re -> How are you guys structuring your CSS files?

for me, multiple css files for different parts of the page is harder
to manage. I'm pretty old school & keep everything within the 1 css
file (within reason). this also means 1 http request which is good.
exceptions are if you had a massive "admin" section or something you'd
probably create a separate, additional, css file just for those pages.

to make it easier to find stuff in a css file i tend to structure my
css roughly like the html...with tabbed in sub sections

so:

#header {stuff here}
     #logo {...}
     #nav {...}

#content {...}
     #main-column {...}
          .featurebox {...}

     #sidebar .featurebox {...}

i find this helps me when revisiting a file after a while. i also
format my css so they dont wrap for each attribute or whatever...
meaning each rule takes up 1 line. the tabbed formatting really comes
into play there and you can very quickly scan down the doc to find the
section you need... much like you scan a html structure.

an example of mine (albeit not meticulously formatted):
http://www.mollio.org/css/main.css

of course firebug makes finding stuff so much easier these days,
giving you a filename and line number! its almost cheating... ;-)

my 2c

pete ottery


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to