The IE hack recommendation is great advice. I won't use conditional comments, it's much easier to maintain a few IE hacks in the main stylesheet. I've never be

The IE hack recommendation is great advice. I won't use conditional comments, it's much easier to maintain a few IE hacks in the main stylesheet. I've never been in favor of breaking up a stylesheet very much. I'm writing a "CSS framework" right now that will only involve one extra CSS file, simple to use and easy to read. I'd much rather have a few marks in the file and fold code as needed than fumble with 10 tabs to make a few changes. And where does layout depart from pure styling? This is a question that confuses me when dealing with broken-up CSS. Border-width is layout, yes, but it's definitely also a visual element and doesn't feel like layout. I think that this is the best way to format code, and almost all coders are familiar with it. Better to use a coding standard, I think. .single .selector { /* indent four spaces */ } .multiple .selector1, .multiple .selector2 { /* indent four spaces */ } /** * Block comments */ .single .selector { single: property; } Over-documentation means your class names and HTML semantics are incomplete. Most CSS code is very, very easy to figure out (you can pick a page apart with a glance at Firebug if it's tableless), and you either need to strip it out or unnecessarily increases load times.