Rick I completely agree.

This is on my to do list, skinability of modules..

We should try to get this right for the core modules, third party developers is another problem (as you can see with XHTML).

I would like any module to use consistent Css classes, NO inline CSS and as little in modules.css as possible.
I agree  we need clear guidelines.

ATM I don't have any time to work on this (the transition to DNN 5 requires a complete rewrite of the Skinning documentation and there is a skin contest comming), if you feel like contributing some time to start this of it would be really welcome.
(not meant as "put your money....")

Thanks, Timo

Rick, your right time is the problem...

I worked on the DNN 5 skin object attributes tables and it's almost finished (so not the whole doc, only Skin Object attributes)

Will send it to some people for a check this week and release it as a Beta, in the Forum.

I agree DNN5 would have been the right time to change the standard classes, but we decided not to for Downwards compatibility reasons.

For "us" it's not a problem to make some changes to a skin, but for a lot of people it is.

On the other hand some people don't seem to realise we went from DNN 4 to DNN 5 a major change, which means there could be at least some minor changes (apart for the unintended changes like the Case sensitivity).

Nice work Timo,

I've been removing the Dnn Css files in my code behind for the modules. Solves alot of problems when using 3rd party controls like Telerik.

Have to try out your Skin Object this weekend.

Thanks, Burl