I’ve been thinking every now and then about how much my work relies on using Photoshop for starting a design. In the past, I was used to a workflow of:
Photoshop design > Revise/Edit > Markup/CSS > Browser bugs > Revise/Edit Photoshop design after more client requests > Change Markup/CSS > Browser bugs > Finished (maybe)
This process is not uncommon in the web and freelance design world. Those last three steps could potentially cycle into what may seem like an infinite revision hell. Revisions that mean returning to Photoshop and perhaps adding something like rounded corners or applying a font change. Both of which, if several layers have been created, can be very time consuming.
What I’ve discovered is that designing in Photoshop is not at all that different than designing with Markup and CSS. You’re still going to use Photoshop for graphic touches and polished png’s, but you’re skipping all the monotonous layer changing and crappy text rendering that doesn’t translate to what the web browsers will look like.
After reading this years’ “24 ways: Make Your Mockup in Markup” article, I am completely convinced ditching Photoshop from the start of the design process is the best (and painless) way to approach modern web design. What I think is the most convincing point made early in the article is a quote by web design guru Jeffrey Zeldman:
Content precedes design. Design in the absence of content is not design, it’s decoration. – Jeffrey Zeldman
If you think about anytime you’ve started a project with little direction from a client and had no content other than the name of the url, what did you end up doing? If you worked the “old” way you probably opened up your sketch pad or Photoshop and started mocking up ideas using dummy content. But what’s going to happen? You’re going to bust out a kickass design that you feel great about, but, we can find from past experience that there exists no “perfect client(s)” who are happy with that first draft mockup. They’ll start asking questions like, “What are these tab rollovers going to look like? How will video posts work? I want to add a cool lightbox window for all image previews, can you mock that up for me? I don’t like your color scheme, do it in lemon chiffon.”
So you revise and fumble with your layers.
Then, the content the client didn’t realize they wanted at the start creeps out. All of a sudden…that first draft you created has turned into a burden of layer changing and pixel pushing. Also, any questions about dynamic content or user interactions are a royal time zapper to mock up as a static .psd. There are always more changes after that first mockup if you haven’t learned your lesson about setting a feature limit, but that’s another topic of discussion.
Really the two points I got out of this article that I find a lot of value in are, this will save you oodles of time, and that by approaching web design in this manner we can help push the newer advancements in xhtml and css forward into the standard that they should be.
In summary, what you have to gain from using the web browser as your design tool:
- Standards compliant markup for clean accessible code from the start
- CSS3 properties for those design touches (rounded corners, border colors, text-shadows, @font-face)
- A client that can see results in their vision and be apart of the design process
- Less time spent making small revisions in a static environment!
If you’re on the fence about this approach here are a few other juicy articles on this topic that help solidify this approach to web design.