For anyone who gets frustrated with DNN designing, I STRONGLY suggest you download firefox, and get the web developer tool addon and the firebug add on. the web developer add on lets you "real-time" edit your Css which is good for getting past small tweaks. Firebug lets you see everything going on with your site, and does an exceptional job at showing how / what Css is being cascaded / overwritten by other CSS.

Between the two tools I have been able to resolve 98% of all my "issues" / frustrations. The rest of the time I come here and someone relplies. :)

I'll second pulling .Head out of the module title, though I suspect the new skinning engine in 5.0 may already be headed that direction.  Many of these CSS styles that are built into DNN code make things difficult to code to standards as well.  Plus, overrridng these in a skin or container CSS file just compounds the amount of CSS that must be processed (PageBlaster helps this).

I also have issues with inconsistent use of the H1, H2, etc. tags.  Modifying the container so that I get a responsible use of the tags in hierarchy, which helps in search engine optimization, is a pain that really isn't needed.  Span as a block level tag isn't well thought out in DNN use and adherence to standards is scattered at best.  Again, I'm expecting a lot of these long-running problems to work out in a new skinning engine in Cambrian.  The current engine, though well maintained, is really dated now.

On the other side, at least there is a default style in the module title that works in many skins without modification.  While I don't like the .Head class, it's a simple way to ensure all DNN installs come with a decent set of base styles and provide a method for an inexperienced end user to change the look/style through the management interface.

Jeff