csuguy - 11:15 pm on Aug 15, 2008 (gmt 0)

csuguy - I believe what you are referring to as 'structure' most other people would call 'layout'. As applied to HTML, structure usually refers to the use of semantically meaningful elements like headings, paragraphs, lists and the like. Part of the goal of CSS is to leave HTML structure to HTML, and confine the bulk of control of visual appearance (i.e. including layout) to CSS. You could always use a separate style and structure CSS file, but personally I would find that adding an extra layer of complication, rather than ease of use, except for the most complicated of CSS-based designs. It's the same reason that an ID of "footer" is much better than an ID of "bottom" - you are likely to want to change the layout without changing the underlying HTML structure.

You're right - layout would have been the better word to use. Structure just came to mind first :D. I'll make sure to use that from now on.

However, I do believe that - unless its a super simple design w/ little css - creating a separate file for layout is worth the effort. True - for the initial design it is easier to stick it all into one location. Hence many people, when initially designing, make all of their css embeded and when it is completed they move it out into a separate file.

And the reason it is moved into a separate file is for maintainability and for easier to read code. However, often one aspect of maintainability is forgotten here - the person/people who may join you in/take over maintenance of the website. While it maybe easier for you to leave it all in one file, it is much easier for people coming along later to maintain the website if the design is already nicely divided into separate files.