rema wrote
In my opinion the proper way to do it is to have the skin 100% controlled with CSS and that is the only file you have to change to alter the skin.
That's nice when you can. I often have to tweek a skin to make it compatible between browsers which can often call for an added div wrapper or the breaking up of a div in the orginal layout into a table, or perhaps to include a section into a span to allow a more specific class to be used, again to make it work cross browser. But I probably have more of those issues to deal with as I make sure my skins use a standards complaint doctype, as I do not want to work in "quirks mode" as the default doctype in DNN and your skins use. Over the years, I have had way too many problems working with "quirks mode" to ever allow my sites to fail standard complaint doctype and drop into quirks mode, too many issues living on the quirks mode edge.
As for css, I heavily rely upon it, but as I mentioned there are times when some additional code is required once testing on multiple browsers begin. When you have a good base template though, most skins can follow that same template and be fine, but if you move outside the box a bit on a skin, you can be right back into the muck with cross browser issues, not to mention those times when you think you might just want to add a little something-somthing to an area.
BTW, your site is quite beautiful!