I've got a brief article that explains how the hierarchy for CSS works it's here - Because of the flexibility for skinning it allows you, to specify elements, right down to container level.  So yes - as you package the skins and containers as long as there is a filename.htm and filename.css it will be read.

You can also put them into a container CSS file but it's a little more complex, so generally for speed and ease I use the filename.ascx and filename.css method which you described.

In short that's what the skinning engine does - it reads those files and knows how to interpret them.

Nina Meiers

Good to see people still wanting to do this :)

You've understood it right and like Nina says, DNN takes care of it when it parses the skins upon upload. Once you've done it like that, then you can take a variety of shortcuts depending on how independent you need the containers to be from the skin. If they are not independent then you can simply place all of the container css into your skin.css and not have it seperate at all. It' saves on a lot of duplicate stuff.

As a tip, when you're creating your skin and containers in your wyysiwyg editor, add a link to join each htm file to its relevant css file: <link rel="stylesheet" type="text/css" href="name-here.css">

This lets you edit and preview the file with styles in place. However, if you forget to remove the link before packing and uploading the file, then your portal will load the css files twice.

Get back here if you have any trouble.

Regards,
Rob