3 ms·
I always felt CSS solved the wrong problem. It's too low level -- and it doesn't really help separate content from elements as much as it should. It feels like
by e12e 12y ago
I always felt CSS solved the wrong problem. It's too low level -- and it doesn't really help separate content from elements as much as it should. It feels like the designers looked at what people were already doing with tables (forcing old, DTP-style layout on web pages, ignoring the ability of user-agents to prefer how content should be presented) -- and tried to separate that layout out from the mark-up. So you ended up with two types of mark-up, just as with tables, semantic mark-up (h1, p, em, img, a/href, li) and "layout mark-up" (span, div). To a certain extent CSS was successful in making table-markup semantic again. But pages are still evolving away from being easy to parse for content, just as they were with table-based mark-up.
I still think Adobe's proposal:
http://www.w3.org/TR/css3-regions/ http://www.w3.org/TR/css3-regions/
is a much better way to solve the problem how "how can we let publisher dictate how the pages should look, users be damned, but still keep the html-markup simple and semantic" -- than the traditional CSS model.
All that said, sites like the legendary CSS Zen garden, does illustrate that CSS is a powerful tool, and offers quite a few improvements over plain old html+tables:
http://www.csszengarden.com/ http://www.csszengarden.com/
Still wish they'd gone with something that was more informed by Desktop Publishing Software (along with some proper support for breaking up words, a la:
https://code.google.com/p/hyphenator/ https://code.google.com/p/hyphenator/ ).
- lmm 12y agoThe CSS Zen garden made sense in an age where people hand-wrote their pages. But today any CMS could achieve exactly the same results with plain html + tables - the pages are already rendered on the server (or in Javascript) based on a template + content (probably in markdown or some such).
- e12e 12y agoI disagree. It is much more feasible to have templates and widgets that work across different CMSs and blog platforms, if you can have a common html target to style with css (and enhance with js). And even if you don't think ready-made templates are a good idea (eg: using a layout made for wordpress with ghost, or vice-versa) -- many companies have heterogeneous solutions where the "web site" is actually made up of various independent systems, unified behind a proxy like Traffic Server or Apache with mod-rewrite. Having a sane html template to target, makes it much easier to have a uniform looking (and behaving) site -- and you only have to fix css bugs in one place.