On 8/9/05, Christian Heilmann <[EMAIL PROTECTED]> wrote: > I will introduce it as a best practice for my developers here, you can > do the same at your place, if more and more companies can see the > benefit of it, we may be able to collate an overall standard and make > it much easier for developers to maintain other people's code. It will > be a guideline, and some metrics could show that it is effective, > which is something we'd have to measure, too. Guidelines are cool, > cause you can follow them but you don't really need to.
I'd definitely be keen on getting in on that. I myself have yet to settle on a standard structure for my CSS, but with every new site I get a little closer to finding one. I imagine it's that way with most of us, so a place to share experience sounds like a good idea. I usually tend to chunk my rules by where they're manifesting on the page (all the rules for the header go together, all the rules for the footer go together, etc, I call em "page sectors" but that's just me) from the top down (header, body, sidebar, footer, etc). It works well until the stylesheet starts getting complex. For example, if I'm using body classes to distinguish sections of a site, should I chunk all the rules for that site section together, or break it into page sectors and have each sector sub-chunked by section? I've also tried breaking them out into separate style sheets (both by sector and by section, e.g. header.css and portfolio.css) but I'm not happy with the way that scatters things. Then you get into site skins and hack management and so forth... yep, a CSS architecture repository and reference library sounds like a good idea. Wiki anyone? -- Craig, www.focalcurve.com ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
