Rodney,

From a CSS point of view the skin.css file contains the common code shared between all skins in a pack, and the skinname.css files are specific to each of the skins their associted with (ie a skin called yellow would use the skin.css and the yellow.css file).

I'm not too sure about a common.ascx file though like they use in Wordpress where you define the layout for the header, footer and so on which gets included in a main template file.

Hope this helps from a css point of view though,

Rick.

---

---

PSDtoDNN - You supply the artwork... we'll build the skins!™
Website | Twitter | YouTube | Skype

Rodney,

Maybe because I am I developer I look as your issue a bit differently.  Have you considered having a common skin definition that is read by a code generator that then generates the 10 different versions?

Code Generators typically generate VB and C#, but are not limited to the specific languages.  You should be able to create the skin files (aspx, xml, htm, css) using the code generator.  There are many code generators out there so you use one of them or create something yourself.   For example MyGeneration ( must be good they use DNN for their site <grin>)

This method keeps the "control" in your hands and does not require DNN support.

Just a thought
Paul.