Quote:
Seven years after the first American Web site launched, Jeffrey Zeldman and a group of fellow Web developers decided that Microsoft and Netscape were fragmenting the Web into proprietary fiefdoms, with the side effect of forcing developers to code duplicate versions of their sites for a metastasizing population of incompatible browsers.
-- A Web gadfly makes his mark
|
I bet -- were I to do all table-based layouts -- the opinion of the only thing you can do might be different. Were this a code discussion, any number of designers would feel quite free to hold forth on why I'm either behind the times, or worse. The same goes for blink tags in a usability forum.
WPW itself took the step of having a content discussion forum.
There's really no reason not to adopt content-driven websites as thoroughly as standards. Where reasonable arguments are put forth against tables, something similar can be said about pointless content and purposeless designs and redesigns. ALA did this with the "redesign versus realign" article referenced here.
Content driven design gives the designer just as many advantages and opportunities for differentiation as standards based design. And, like standards, it is something we should have been doing anyway.
What Zeldman did was show standards aren't
limiting, they free up your time for innovation. What CSS Zen garden did for CSS was destroy the myth CSS couldn't do anything. They didn't go nearly far enough, but these examples show the way. The point is to see the differences and advantages of content-driven design.