Originally Posted by
delia
Thanks for that idea, Steve.
Y'all have answered the question partially - and these are necessary discussions about mod CSS.
But I'm actually talking about taking that default stylesheet and splitting it up so that only non-page specific stuff remains. Going forward - especially with responsive templates and adding more jquery based CSS, that default stylesheet is going to grow. I'm looking to prepare for that eventuality in future versions.
I guess the real question is, if stylesheet.css is split up for page specific reasons, will that make it easier to change the CSS on the site? It's hard to imagine how a newbie will see this - it was way too long ago for me to remember what it was like .
Seems to me that if the stylesheets are named per page, that would make it more obvious where specific CSS resides. But since CSS does depend on the order in which the CSS files are read, would that make it harder to troubleshoot problems? 99% of the time the page specific stylesheet comes (alphabetically) before the stylesheet.com so that CSS can override the main stylesheet.css while on that page. I can easily foresee problems there - but should I worry about this?
Which returns me to the mod CSS. If we do this, then mods would have to all hold the default CSS and changes, negating the idea of new CSS files for mods.
Yes, mc12345678, standards. Let's keep talking everyone!
Bookmarks