David> I'm currently writing the styleguide for BHP Billiton's site David> templates, and I am including in it a section on div id's and David> classes, and what they represent.
David> Information in this section includes how the different divs work in David> the context of the page, and in context with other divs, basic David> outlining of how the the divs structure and inheritance works and David> I've made sure our naming conventions for id's and classes can be David> read and understood by people who weren't involved in the project. David If you were interested, and able to share, I'd certainly love to see what you come up with. What to provide as documentation to clients, and how to structure it, is something we're about to start looking at in more detail. Ideally, I'd like to have some sort of template that would lay out the sort of detail you're talking about above, that we could provide as a matter of course to all clients. If it's "commercially sensitive", that's cool and no problem! On another note related to names for div id's and classes, I'm realising the value of having a core stylesheet and then separating out styles for individual pages/templates and having these in seperate stylesheets which can be downloaded only by the pages they are needed on. I realised this once my stylesheet got to over 600 lines and I was taking ages to find the items in it I was working on, and strange things were happening with the cascade as things were being "overwritten"! Is this approach (multiple stylesheets) something others use on larger sites with a lot of styling? Regards Mike Brown ==================================== SIGNIFY :: the logic behind ==================================== ph: +64 4 803-3211 | fax: +64 4 803-3241 mob: +64 0274 885-992 | http://www.signify.co.nz P.O. Box 24-068, Manners St, Wellington Level 8, CMC Building, 89 Courtenay Pl, Wellington ==================================== This communication, including any attachment, is confidential. If you are not the intended recipient, you should delete/destroy this communication; you may not read and must not copy, send on or retain any part of this communication. Please do not disclose to any third party anything about this communication. ***************************************************** The discussion list for http://webstandardsgroup.org/ *****************************************************
