This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Does your book provide any suggestions on naming conventions and organization of the .css document(s)? I find that I struggle to remember the class names and to create good names because I haven't come across suggestions for good naming conventions.
Chapter 1 discusses the pros and cons of using separate .css files. On the positive side, multiple external .css files make it very easy to modify an entire web site, parts of a web site, or even a single page of a web site. On the other hand, each .css file you add to a web page delays the downloading of the page by 0.1 to 0.5 seconds per file � even if the file has been cached by the browser (a browser still has to ask the server if a cached file has been modified and needs to be downloaded again).
By the way, if you are a developer, you'll love this book because it is all about the best practices for coding XHTML and CSS. I wrote this book because I'm a developer and couldn't find any good CSS books for developers � they were all for designers. I have included a wealth of information on coding XHTML and CSS. The book also has a wealth of information on design patterns that you can quickly use in your code to create cross-browser compliant solutions.