If you've been designing CSS like I have for years, you can utilize TVs for your content resource to determine how you would like it to be presented.
- I've been utilizing the @import statement (usually in combination with link rel element) for modular CSS for quite some time.
- My CSS is split into 5 files, all ordered according to their priority based on their function.
- One of the CSS files is document specific. So I load the CSS in the following way: HTML Overrides, Layout Styles (2 column, headers, etc.), Content Styles, Page Specific Styles (an article vs. a blog), and finally "functional CSS" (CSS that mimics application functionality).
- I don't utilize browser-specific CSS hacks. I've simply chosen not to support IE 5.X or IE 6.X.
As a result, if my page is of template, Article, I may choose a different "Page Specific" file or layout structure from any other page very easily. I've utilized this with TV's to determine which classes, or even Resource Specific CSS. Doing so allows my users to have some control over the way their own content is presented without it undermining the consistency of the site's presentation. Furthermore, I still maintain control over when custom CSS may be applied (within the site).
P.S. Thank you for this tutorial! It was exactly what I wanted my whole life and never knew it.