>> CSS requires a change in thought process, a re-envisioning of a >> website >> from a different perspective. > > Exactly, at least for those who learned to create web pages without > the benefits of CSS.
This is the interesting part, because I'm a professional web designer, and until about two months ago, I had never designed an html table in my life, other than some small forms that arguably shouldn't have been tables to begin with, since my primary work doesn't require them that often. So when I see a website coded in tables, my brain really starts to hurt. Part of it is a generational gap between younger web designers and older. I never knew that table based designs were ever ok. The books always talk about table based layouts as if the Civil War were still raging, and the victory of the good North (CSS) was almost complete over the evil South (table-based layouts). But another part of why tables hurt my brain is the lack of semantic structure. I can look at, analyze, and improve the code of a <div> and CSS based layout any day. What is there to guess about this structure? It's easy, it makes sense, and is really easy to modify. <div id="header"></div> <ul id="nav"></ul> <div id="content"></div> <div id="sidebar"></div> <div id="footer"></div> But when I look at the structure of even a simple table based layout, I have to blink my eyes a few times to even guess at what I'm looking at. In fact, my coworker, although primarily a visual designer, had to take over our email design project, since he was the only one with any experience using tables for layout, and the only one who could figure out how to make it all work. ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
