I have been creating several sets of skins for a client and I have seen two different methods for naming the CSS file for either the skins and/or containers. I'm wondering if there is an advantage or limitations to one or the other.
1. Create a general container.css or skin.css that applies to all container/skin files in the set (i.e. if you have Home.ascx and Detail01.ascx).
2. Create a CSS file for each ascx (or html) file with the same basename as that file. (i.e. Home.ascx, Home.css, Detail01.ascx, Detail.css)
For me, the second method means a greater repetition of code and creates more work when a color or font or something else needs to be updated. But I have noticed some strange behavior when there is more than one skin set used on a site, or a container from a different skin set is used on a page with a different skin set to it (i.e. container from YourSkins is put on a page with MySkins applied as the page's skin).
Has anyone seen any problems with multiple generic skin.css files being pulled into the same portal, even though they have different paths? (i.e. Skins\YourSkins\skin.css and Skins\MySkins\skin.css) or even (Containers\YourSkins\container.css, Skins\MySkins\skin.css)