I would submit that this is not the fault of the commercial skin vendors. It is the fault of DNN - after you have been in the DNN "community" for awhile you learn that while DNN is an excellent open source project that you will really like - it is a closed community. Want an example?  DNN comes with a core module called Surveys - do you see it in use anywhere on DNN.com?  Have you EVER seen it in use on DNN.com?  Oh, but we can dream - here are a couple of survey's I'd love to see on DNN.com:

1. Should we have skin contests (like we used to do) with the winner being included in the core?
2. Should DNN.com change to a forums module that actually works?
3. Should DNN.com change the way forums are moderated?
4. Should DNN.com add X forum folders?

Can you add to the list??? 

Greg

Kind of - but when you design from a valid xhtml/css/tableless method you think differently to how you think when you (years ago) designed pages using tables. The page will end up looking different - you can spot a css layout from a table layout without looking at the source.

Sure - you can get 2 pages looking the same using either method but the fact is you don't. It's just a different approach that you use when you design using the css approach.

And it's that approach that I think developers need to be aware of - minimal, valid code output and leave it to your css to do the styling.

You don't need tables and all those extra divs..

A seperate div for each corner of a box? That's really nasty coding..

Not wanting to sound too harsh on DNN though - it's a quality bit of kit and I love the way it allows you to drop modules in and the inline editing is awsome. I just wish the front end was a bit better.

How is that? A page is made out of layout, text, color and images. There's nothing visually which indicates if css or tables was used.