Responsive: Web Design
Responsive: Web Design
WEB DESIGN
with Adobe Photoshop
DAN ROSE
RESPONSIVE
WEB DESIGN
with Adobe Photoshop
DAN ROSE
Responsive Web Design with Adobe Photoshop
Dan Rose
For the latest on Adobe Press books, go to www.adobepress.com. To report errors, please send a note to errata@
peachpit.com.
Notice of Rights
All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic,
mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. For infor-
mation on getting permission for reprints and excerpts, contact [email protected].
Notice of Liability
The information in this book is distributed on an “As Is” basis, without warranty. While every precaution has been
taken in the preparation of the book, neither the author, Adobe Systems Incorporated, nor the publisher shall have
any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indi-
rectly by the instructions contained in this book or by the computer software and hardware products described in it.
Trademarks
Adobe, Photoshop, Fireworks, Dreamweaver, InDesign, Illustrator, Creative Cloud, Generator, Typekit, and Flash are
either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
All other trademarks are the property of their respective owners.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
Where those designations appear in this book, and Peachpit was aware of a trademark claim, the designations appear
as requested by the owner of the trademark. All other product names and services identified throughout this book are
used in editorial fashion only and for the benefit of such companies with no intention of infringement of the trade-
mark. No such use, or the use of any trade name, is intended to convey endorsement or other affiliation with this book.
ISBN-13: 978-0-134-03563-5
ISBN-10: 0-134-03563-1
9 8 7 6 5 4 3 2 1
Acknowledgments
This book was guided by the resourcefulness of Victor Gavenda, the eagle eye of
Stephen Nathans-Kelly (and the Adobe Press team), and the sage wisdom of Dennis
Kardys. My gratitude to Dan Mall for trailblazing the Photoshop-for-RWD path. My
love and dedication to Amanda for her support and encouragement, to Holly and
Norah for play and snuggle breaks, and to Jesus, with whom all things are indeed
possible.
This page intentionally left blank
Contents
Designer/Developer Bonding . . . . . . . . . . . . . . . . . . . . . . . . . 47
Moodboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Methods of Moodboarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Finding and Storing Inspiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Visual Inventories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
The Pursuit of Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Conversations, Not Deliverables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Experimenting with Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6 Establishing Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Suitable Mock-up Replacements. . . . . . . . . . . . . . . . . . . . . . . 79
On Sketching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Style Tiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Style Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Component Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Prototyping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Roughing It in Low-Fidelity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
High-Fidelity and Beyond! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Downloading Assets via Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Extracting Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Generating CSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Artwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Subtle Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Random User Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Social Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Pictura . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Transform Each . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
DevRocket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Bjango Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
WebZap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Composer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Layout Wrapper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
RotateMe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
x CONTENTS
Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
0to255 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Adobe Color (formerly Kuler) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Adobe Color CC for iOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Coolorus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
iOS Hat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
OtherIcons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Glifo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
FlatIcon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
TinyPNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
ImageOptim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Prototyping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Framer, Composite, and Stand In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
InVision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
GuideGuide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Renamy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Ink 192
psdiff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Name Files Appropriately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
CONTENTS xi
Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
Name Layers and Be Accurate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
Use Groups and Globalize Where Possible . . . . . . . . . . . . . . . . . . . . . . . .204
Delete Unnecessary Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
Be Nondestructive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206
Use Blend Modes with Care . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
Be Aware of Resolution and Density . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Standardize Font Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
Don’t Stretch Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
Control Your Text Boxes and Separate Them . . . . . . . . . . . . . . . . . . . . . .209
Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
Use Overlays Appropriately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Nail Tileable Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Be Deliberate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
QA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Proofread . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Account for All Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Be Familiar with Browser Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . 212
On Adoption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Strategies for Getting Buy-in Internally. . . . . . . . . . . . . . . . . . . . . . . . . . .220
Strategies for External Getting Buy-In . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
What Happens When Things Go Wrong . . . . . . . . . . . . . . . . . . . . . . . . . .226
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229
4
A PLEA FOR PHOTOSHOP–
BROWSER HARMONY
In Chapter 3, I presented the case for a browser-based approach to web design. In
this chapter, I’ll take the browser approach down a peg, but I don’t want to diminish
its importance in a responsive workflow. The browser is still the centerpiece of what
we’re doing. But we need to work Photoshop back in to the fold—and not just because
we’re Photoshop fanboys and fangirls. If it didn’t make sense to include Photoshop,
I wouldn’t waste your time advocating its importance in the responsive web design
(RWD) workflow.
The good news is that Photoshop, more so than any other tool I can think of, fills an
important role missing in a browser-only design process.
CDs offered a smaller, portable format that could fit significantly more music than
records. They were even more durable, depending on how you stored them. It’s no
shock that CDs were became more popular than vinyl. When the iPod ushered in the
digital music revolution of the mid-2000s and began to marginalize disc media, you
would assume it made vinyl go away altogether, right?
Wrong. An incredibly strange thing happened: In 2006, people started buying more
records. Today, vinyl growth is steady, and while it’s by no means equal to digital in
sales and mainstream consumer use, it remains relevant. Amazingly, market analysts
have assigned no single concrete reason for vinyl’s uptick in popularity (see Figure 4.1).
Figure 4.1 Vinyl has withstood some major innovations in music media, staying relevant even to the
current day. Can Photoshop do the same in the face of new apps such as Sketch and workflow
alternatives such as designing in the browser?
So, who or what gets the credit for sustaining the life of the vinyl record? Two main
audiences: audiophiles, who prefer vinyl’s sound quality and treasure their massive
record collections, and disc jockeys (DJs). DJs have mastered the art of combining the
digital and the analog, so to speak. Digital tracks play off a computer while the DJ spins
a record on a turntable for scratching, looping, and adding a host of physical effects.
Curious, I sought after some rationale from a friend of mine who is a popular Boston-
area DJ. Why does he prefer to use vinyl in his work? It’s the same thing we Photo-
shop users enjoy but sometimes have trouble putting words to: direct manipulation.
4 A PLEA FOR PHOTOSHOP–BROWSER HARMONY 51
Figure 4.2 The Free Transform tool, the Move tool, and a host of others offer an ease of use that enables the
exploration we desperately need—and won’t readily find in a coding-only design environment.
Designing in the browser can’t compete with the benefits of direct manipulation. Don’t
underestimate the value of drawing a shape in Photoshop and seeing every step in its
implementation. Your brain is processing all the sizes, colors, and positions, looking
for the one that feels right.
Sure, there are some disadvantages to the freedom direct manipulation provides. It
engenders the “silo” effect, where we designers go solo and play in Photoshop for
extended periods of time, discouraging collaboration. Direct manipulation is neither
systematic nor object-oriented, meaning the process by which we transform type and
shape often doesn’t adhere to a pattern or set of preset constraints.
But exploring in Photoshop sure does help get the creative juices flowing.
52 RESPONSIVE WEB DESIGN WITH ADOBE PHOTOSHOP
Objectively, there’s nothing wrong with this approach, and certainly it communicates
that these are five areas you can visit. When I showed the client, they were quite under-
whelmed. The feedback I received was that the section didn’t have adequate emphasis
relative to the importance of the content.
My reaction was to fill the containing divs with the button color (see Figure 4.4 on
the next page). Bigger = more important, right?
54 RESPONSIVE WEB DESIGN WITH ADOBE PHOTOSHOP
Figure 4.4 Bigger buttons. Don’t laugh—you would have done the same thing.
Again, the clients were underwhelmed. They expected to have buttons and appreciated
the increased size, but they thought it was a missed opportunity to tell more of the
story behind the content. It’s a high school, and these portals are all part of the journey.
It wasn’t until I toyed around with that section in Photoshop that I started to layer some
new elements in, like screened photos and sideways text. The point isn’t that those tech-
niques are exclusive to Photoshop (because they’re not: adding a simple background
image and “transform: rotate” in an HTML & CSS editor is just as easy), but the idea
came more naturally in Photoshop.
Sarah Parmenter had a similar assessment of designing in the browser.
While I won’t advocate for having your entire design predetermined before HTML &
CSS, the example shown in Figure 4.5 is a case where taking one small section or com-
ponent into Photoshop makes a world of difference.
As unpopular as the idea may be, I think it’s easier to take the path of least resistance
in the browser than in Photoshop; working in an HTML & CSS editor makes you more
inclined to think in terms of boxes, containers, and the styles you usually employ than
ones you don’t. Heavy layering, offsetting only a single element and not others, and
breaking convention usually mean tweaking more than just a few HTML tags and CSS
properties. Sometimes, that amount of trial isn’t worth the inevitable error. Suffice it
56 RESPONSIVE WEB DESIGN WITH ADOBE PHOTOSHOP
to say, for whatever reason, I’m more inclined to play it safe in the design techniques
I use in code than in Photoshop.
Is it possible that lack of courage in our code-exclusive designs is the reason that all
RWD sites look so similar?
“Have you ever noticed how many websites look the same?
How many are just a bunch of rectangles? How many seem
to copy from one another? Where’s the uniqueness and
creativity?
”
—STEVEN BRADLEY (The Web is a Rectangle, www.vanseodesign.com/
web-design/rectangular-web/)
“Isitefeeldesign.
like responsive design has sucked the soul out of web-
Everything is boxes and grids. Where has the
creativity gone?
”
—NOAH STOKES (http://esbueno.noahstokes.com/post/44088237921/
where-has-all-the-soul-gone)
“Iprojects
wonder if #RWD looks the way it does because so many
aren’t being run by designers but by front-end dev
teams.
” —MARK BOULTON (https://twitter.com/markboulton/status/
445943150247702528)
The question of “Why do all RWD sites look the same?” is a pertinent one when you
consider that diversity in the pre-RWD era was fairly extraordinary. One could even
argue that Flash-based sites were the most distinctive of the lot. Today, it’s common-
place to pick out the sites designed in the browser from ones designed in Photoshop et
al. This notion is where we get such statements like “It looks like a Bootstrap/Founda-
tion site” and “It’s like they just slapped their logo on a responsive WordPress theme.”
4 A PLEA FOR PHOTOSHOP–BROWSER HARMONY 57
Figure 4.6 Examples of similarities in responsive site design. Common components include “boxy” layouts, white
background headers, and hero images with white text overlaid.
Figure 4.7 Examples of similarities in sites designed on the Bootstrap framework. Unadjusted button styles are a
clear giveaway.
Figure 4.8 Examples of similarities in sites designed as WordPress themes. Similar content layout is a hallmark
of blogs.
To some extent, there will undoubtedly be shared styles and components from site to
site, no matter how original we think we’re being (Figures 4.6-4.8). That’s OK. I’d much
rather have a Web that works than one that succeeds in diversity for diversity’s sake.
Remember, the originality we established using Photoshop didn’t always translate to
58 RESPONSIVE WEB DESIGN WITH ADOBE PHOTOSHOP
the browser in a way that was user-friendly, either. Karen McGrane made this witty
retort to the complaint of RWD sameness as it applies to print:
“But why do all the magazines have the binding on the left?
And columnar layouts, so tired. Where’s the innovation?
”
—KAREN MCGRANE (https://twitter.com/karenmcgrane/status/
515162632551411712)
I’m not sure we can fault responsive design for a lack of uniqueness in sites, but cer-
tainly its introduction has added to the number of design considerations we need to
make. By extension, new considerations may not always be tested across all screen
sizes, so we rely on what “works” and what’s familiar. We’re still getting our feet wet
designing responsively; creativity will come.
That doesn’t mean we need to stifle uniqueness or “soul” in the name of being respon-
sively correct. We need to think creatively about being creative.
I contend that Photoshop can greatly assist in our efforts to infuse our designs with the
unconventional and unique. Where designing in the browser may introduce friction
in the creative process, Photoshop can help us focus on the best approach regardless
of the amount of code needed to execute it.
browser to keep our designs flexible, while curtailing the amount of time and effort we
exhaust trying to come up with truly unique ideas.
If a responsive workflow is your goal, I recommend adopting the following philoso-
phy: Photoshop can’t be the workhorse we’ve made it in years past. Instead, Photoshop
takes a backseat to in-browser design, but we still use it to ideate when necessary. To
what extent do we keep Photoshop involved?
In his article “Responsive Web Design in the Browser Part 1: Kill Photoshop,” Josh
Long makes the following statement:
“IfPhotoshop
you want to be a better designer, I’d start by killing
”
—JOSH LONG (http://blog.teamtreehouse.com/responsive-web-design-in-
the-browser-part-1-kill-photoshop)
While some of this sentiment seems in line with what we’ve explored, I object to
the notion that discarding any tool makes you a better designer. Becoming a better
designer has more to do with knowing the limits of the tools you use and knowing
when to use them for the greatest gain.
The browser can bear the majority of many layout and style decisions, which is great
because it’s ultimately where our design will live. We’d be shooting ourselves in the foot
if we tried to make every decision before writing a line of HTML or CSS. That puts the
onus on adopting a workflow that allows the flexibility needed to refine design solu-
tions after being in the browser (I’ll talk more about how to sell this kind of process
internally and externally in Chapter 12).
In most instances, you’d be hard-pressed to find a use for your default Mega Buster
arm cannon, so the quintessential strategy for beating each boss was to use another’s
weapon. Ice Man’s Ice Slasher was critically effective against Fire Man, for example.
Choosing the right weapon at the right time was, essentially, a glorified game of Rock-
Paper-Scissors. Mastering when to use each weapon made the game infinitely easier
(see Figure 4.9).
Figure 4.9 Just as Megaman leveraged timing to beat his enemies, can we do the same with Photoshop?
Specifically, I mean the enemies called “boxy,” “bland,” and “uninspiring.”
Collecting weapons and knowing when to use them is not so different from the prob-
lem we face in web design. By using the right tool, at the right time, for the right pur-
pose, we extract more out of said tool than normal. Knowing when to use Photoshop
is the only thing that can logically keep it in our workflows. Using it too often, too
early, or for the wrong purpose produces frustration, wasted time, and potentially
wasted money.
4 A PLEA FOR PHOTOSHOP–BROWSER HARMONY 61
Inspiration
If our plan is to present multiple design concepts to clients, where does RWD fit in? It
seems like a daunting task to show contrasting design directions through Photoshop
mock-ups at a few different sizes, so what’s a more effective way to move the project
forward?
The secret may be getting everyone on track toward a shared ideal far before anything
is done in Photoshop. You’ll explore a few ways to hedge what would otherwise be dis-
carded work by using inspiration from around the Web to drive your directions. Equally
important, you’ll discover techniques for extracting more useful feedback from your
clients.
Art Direction
The conundrum of page comps in a responsive world hasn’t been ignored. While some
of the industry has turned to producing tools to make comps more quickly, a strong
contingent of designers have devised better design documents altogether. You’ll take
a look at this landscape in Chapter 6, including one I find to be the best suited for a
responsive process: element collages.
Building Blocks
You may have created style guides in the past or be familiar with their longstanding
print implementation. I’ll define what style guides mean for the Web and, more impor-
tantly, as part of a responsive process.
Similarly, component (or pattern) libraries extend what’s introduced in a style guide
into functional collections of elements.
While it behooves us to develop both of these elements in code, there’s plenty of oppor-
tunity to spice them up in Photoshop, long before we run into any funky page designs.
Repair
It’s incredibly optimistic—naïve, even—to expect all the disparate elements of a
responsive site design to come together seamlessly. When it’s time to build pages from
components, we usually find ourselves scrambling to make everything look like the
coherent page it should be.
Let’s determine to expect the wonkiness of putting components together and combat
the seamless spots with Photoshop. You’ll take a look at some common examples of
where page design can fall short and feel disjointed in the absence of a system and
pivot swiftly into an environment to try some stitch-work.
All of this preparation will lead to the union of Photoshop and the browser and to a
better responsive workflow.
Index
B CC Libraries
backgrounds creating buttons for, 125
fixed positioning of, 23 features/functions of, 124–126
gradient, 35 CC Market, as art resource, 170
Bearded design shop, 100 CCM (Christian Care Ministry), 92–93, 95
the big inclusion, 67 Chapman, Shaun, 180
the big reveal, 25–26, 67 character styles, in Photoshop, 88
bird’s-eye view, for cohesive style, 142 Chrometaphore’s Ink plug-in, 192–193
Bjango Actions, 175–176 Clandestine Photoshop (Rose), 222
blend modes Clarke, Andy, 150
careful use of, 207 Clearleft, 96, 97–98
with CSS, 35 client presentations
bloat, 128 the big reveal, 25–26
Bootstrap framework sites, 56–58 design process involvement, 66–67
Bowles, Cennyd, 145 educating on design, 45–46
Brackets, 40 element collages in, 101–102
breadcrumb navigation, in component on in-browser design, 43
libraries, 121 offering contrasting options, 64–66, 74
breakpoint(s) pursuing efficiency in, 75–77
difficulty of three, 18–22 selling new workflow ideas, 224–226
focus on single, 4 with traditional Photoshop, 26–27
browser(s) visual inventories for, 74
compatibility, awareness of, 212–213 Cloud.typography, 24
design variations in, 44 Coda, 40
Photoshop as complement to, 135–136 Code School, 5
resizing, 37–38 Codeacademy, 5
style guide created in, 114 coding skills, 4–6
style prototypes for, 84–87 cohesive page design
web design in. see in-browser design big picture perspective for, 140–142
buttons bird’s-eye view in, 142
calls-to-action, 119 lack of, 140
for CC Libraries, 125 skeuomorphism and, 142–143
in style guides, 111 collages, element. see element collages
Buxton, Bill, 65 collaging format, for moodboards, 68, 69
color plug-ins/tools
0to255 tool, 179–180
C Adobe Color, 180
Callahan, Ben, 222 Adobe Color CC, 181–182
calls-to-action buttons, 119 Coolorus, 182
canvas size, for element collages, 91–92 color(s)
Cascading Style Sheets. see CSS (Cascading cohesive design and, 142–143
Style Sheets) comparisons, in element collages, 99–100
CC (Creative Cloud) extraction of, 162–163
accessing character styles in, 88 manipulating with SVG mages, 155
Adobe Color CC, 181–182 in style guide, 109–110
benefits of, 9 comments, in component libraries, 123
for Extract online service, 160–165 communication
reducing costs with, 30 client, 17–18, 225. see also client
presentations
INDEX 231
M P
Macaw design app, 33–34, 180 Page Layers
Mall, Dan, 17, 72, 90, 92, 98, 222 benefits of working with, 138–140, 218
INDEX 235
PSD, asset storage relative to, 202 Save for Web option, for asset extraction,
psdiff tool, for PSD previewing in GitHub, 29–30, 151–152
193–194 Save function, in asset extraction, 149–150
Scalable Vector Graphic (SVG) images, 155
R scope creep, 100–101
Raindrop cataloging tool, 71 screen resolution, image etiquette and, 207
Random User Generator, 171 screenshots
raster graphics, with Page Layers, 135 New Guides/Smart Guides for, 139
recent feeds, in component libraries, 123 old methods for modifying, 137–138
RedPen tool, 27 Page Layers for modifying, 138–140
Renamy plug-in, 192 search filters, 70
repair work, 61–62 selling workflow ideas internally
Responsible Responsive Design (Jehl), 9 attend conferences, 223–224
responsive design sameness, 140 establish supporters first, 222–223
Responsive Design Workflow (Hay), 22 give presentations, 220–221, 222
responsive patterns, 8–9 set realistic expectations, 221–222, 223
responsive web design. see RWD (responsive selling workflow ideas to clients
web design) affirm direction, 225–226
Responsive Web Design in the Browser Part 1: increase communication/involvement, 225
Kill Photoshop (Treehouse blog), 2 reset expectations, 224–225
Responsive Web Design (Marcotte), 8 Sheeran, Norm, 176
responsive wonkiness ShortcutFoo app, 194–195
fixing, 145–146 sidebar callouts, 120–121
identifying, 143–145 sign-up modules, 119
reverse-engineering style tiles, 83 Site Inspire design gallery site, 71
RotateMe script, 178 sizing images
rounded rectangles, with CSS, 35 with Adobe Generator, 156
RWD (responsive web design) previewing size for, 159
in browser. see in-browser design Sketch tool, 3, 30
contrasting options for, 64–66, 74 sketching, 80
core tenets of, 8 Sketching User Experiences (Buxton), 65
including stakeholders in, 66–67 Sketching User Experiences: The Workbook
lack of cohesive style, 140–143 (Greenberg et al.), 80
Linked Smart Objects for, 136–137 skeuomorphism, cohesive design and,
new workflow for. see adopting new 142–143
workflow slicing, 30
Page Layers for, 133–135 Smart Guides, 139
performance of, 9 Smart Objects
with Photoshop, 7 converting layers to, 206
Photoshop etiquette in, 200 editing, 136
Photoshop vs., 2–3 Social Kit plug-in, 172
potential difficulties in, 132–133 Sparkbox, 84
repurposing tools for, 228 spelling errors, proofreading for, 211–212
responsive patterns in, 8–9 stakeholders, in design process, 66–67
responsive wonkiness and, 143–146 Stand In app, for interactive prototypes,
188–189
state changes, in Photoshop comps, 22
S style, establishing
Sanchez, Edward, 195–196 component inventories for, 87–89
INDEX 237
element collages for. see element collages TinyPNG plug-in, for compressing PNGs,
sketching, 80 186–187
style prototypes for, 84–87 toolbars, Photoshop, 13
style tiles for, 81–83 tools
style guides artwork. see artwork plug-ins/tools
color in, 109–110 asset integration/generation, 183–187
created in browser, 114 color, 179–182
defining, 108–109 for in-browser design, 33–34
icons in, 112–113 merits of comparable, 9–10
link styles/buttons in, 111 organizational, 191–194
for Photoshop-browser harmony, 61 prototyping, 188–190
tables/image dimensions in, 112 repurposing existing, 228
typography in, 110–111 Transform Each script, 173–174
style prototypes transparency
advantages of, 216 with CSS, 35
design elements of, 85 in design process, 66–67
flexibility of, 86–87 Treehouse, 5
function of, 84 Twitter Bootstrap site, 128
style tiles type etiquette
description/advantages of, 82 control/separate text boxes, 209
exploration through, 216 no stretching, 208
as mock-up alternative, 81 proofreading, 211–212
reverse-engineering, 83 standardize font access, 207–208
Styles tab, 163 typography, in style guide, 110–111
Sublime Text, 40
Subtle Patterns plug-in, 169 U
SVG (Scalable Vector Graphic) images, 155 UI Parade online catalog, 176
swatches, of design color options, 110 UI (user interface), Extract Assets as,
157–160
T Unmatched Style design gallery site, 71
tabbed panels, in component libraries,
121–122 V
tables, in style guides, 112 Verizon Wireless, 150
Terrett, Ben, 4 versatility, of style tiles, 82
Test phase, of ShortcutFoo app, 195 vetting direction
text blocks, in component libraries, 117 importance of, 216
text boxes, controlling/separating, 209 including stakeholders in, 66–67
text editor, for in-browser design, 35–36 moodboards in, 67–72
TextEdit, 40 offering contrasting options, 64–66, 74
The Win Without Pitching Manifesto (Enns), pursuing efficiency in, 75–77
77 through conversations, 77
This Is Responsive (Frost), 9 visual inventories for, 72–75
three-breakpoint trap, 18–20 video, in responsive web design, 8
three-direction approach, to design options, vinyl records, 49–50
64–65 visual inventories
“throw it over the wall” workflow, 16, 17 for design process, 72–75
thumbnails, use of Overlays and, 210 efficiency of, 75–77
time savings, with Page Layers, 139–140 visual metaphors, in element collages, 92–93
238 INDEX