Jeff, I agree that we inherit to much styles (and default.css should be cleaned up)

The problem here is that this would be a breaking change for existing installations.

So this is a very difficult subject...

I do have a skinobject that removes any stylesheet from the page, you want, I just wonder if that helps for "beginners".

I don't agree with you on module.css.

Some modules need CSS and it's better to have it externallty then inline.

It's more about what some module developers put in there IMO.

One of the big challenges in an environment like DotNetNuke is that a page is comprised of many different pieces, all written by different developers, designers and admins.  The DNN core obviously cannot write a single stylesheet that serves every module and skin, and skinners have no way to know the requirements of the individual modules.

What might be interesting is to see if we couldn't generate a "master" portal.css that combines all the styles from the active skin and all actively used modules.  If generated, this file could be used instead of the individual default, skin, container, module, portal css files.  There are certainly some issues here in terms of maintenance and how to deal with newly installed modules.

Our current skinning engine is definitely targeted at the typical business user who has little design/CSS experience.  We need things to "just work" as much as we can.  Our challenge now is to provide hooks that allows an administrator take control and remove the "training wheels", recognizing that some administrators may remove the training wheels without fully understanding the implications (we still need dad running along behind the bike for a couple blocks).