On mark-up and frameworks …

For years the web was an immature piece of crap, most web developers were atheist towards web standards, and best-practices were updated at a faster pace than even computer hardware. After that came upon us the web in which standards were more and more loved, and just some minor hacking was needed to gain at least a bearable result. All in all, the world is becoming a better place.

In recent events, CSS frameworks keep on popping up more and more, with some notable web designers loving them, others loathing them, and much that are still in between those two ends of the spectrum. So what gives?

CSS frameworks allow for rapid prototyping, proper grid-based designs and typography and – if used properly of course – for clear and usable interfaces. The only problem with this is, that you need way too many DIV elements, way too much classes on these div elements, and the little baby jesus of web standards will start crying, because “thou shalt keep mark-up and styling separate!”.

I’ve been reading up on a lot of articles written about this issue, and have been talking this over with experienced and less experienced web developers and designers, and the end result of this equation; Write a protocol with quick reference, in which a single, organized way of writing mark-up and styling without trapping the designer’s free and creative ways.

Ready? Set. Go.