Wolf’s Little Store

October 13, 2008

Slicing skill list

I don’t believe you can design successfully for the web if you don’t know HTML and CSS. After perfecting his mockup, a web designer needs to be able to take that design and build a website out of it. If never get your hands dirty in the code, you’re not a webdesigner, period.

I’m not saying you need to be able to build an entire website - that takes a team of skilled people with different proficiencies. And by website I mean a CMS-driven dynamic website, not your single HTML file you uploaded to myfirstwebsite.com.

Designing a website, writing the markup and writing the styleheets are the foundations of the skillset of a webdesigner. You could call it the webdesigner’s holy trinity: perfecting these three takes years, and anything else you know can be considered a bonus.

When you start out with HTML and CSS you run into a thousand cross-browser issues and trying to make the mockup real often becomes a frustrating experience. Almost daily I hear fellow webdesigners curse at one browser or the other. The only way to really learn how to deal with bugs is to spend some time reading up on why and when they occur, and how you can build around them or solve them. I know I spent quite a few hours with a few bugs and hacks.

I compiled a list of common bugs and things you should know how to do to get from mockup to website in no time. This is a reference list so this post will probably get updated in the future.

Currently, this list is browserbug-focused and doesn’t deal with certain skills like saving images for the web, like writing clean and structured markup and stylesheets. Some things are not easily listed - common sense for example. Nonetheless, enjoy.

The list

6 responses

Leave a Reply

Write in English, stay on-topic and polite.