A big request to all DNN core module and project developers.

Please, please, please do not code your .ascx to generate markup with inline styles or html attributes.

Please please please, include more css classes on elements at the highest level in the markup to enable module html elements to be selected by css on a per-module basis.

In order to select a specific html element within a module interface, you currently have to either develop a special container, or change the .ascx markup to add a distinguishing class. This really shouldn't be necessary.

DNN has a great skinning engine. Its a pity its potential is limited by poor implementation of module user interfaces.

Paul, you are right that too many developers use inline styles or HTML attributes, they should not IMO.

A lot of this is from legacy versions of the modules (ASP.NET 1 did not "stimulate" developers to create clean HTML)

That's also the problem with some of the Admin modules, some of them need a good cleanup.

If you find any specific issues in a module, please log them: support.dotnetnuke.com

That's the best way to get something fixed.

It's good that more and more modules use templates which makes our lives a lot easier....

Your last issue has been resolved in DNN 5.0 on the Core level (module independent):

Discussed here:
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/163/threadid/254020/scope/posts/Default.aspx

Implementation here:
http://support.dotnetnuke.com/issue/ViewIssue.aspx?ID=8678&PROJID=2