Lee I have not looked at the tutorials, since I've simply been busy holding my own with trying to answer these forums, and the death of a staff member has changed focus for a shor time.

I've been working with Armand on several other projects for quite some time. It's been a big job, and we were not getting together to finalise things until after Easter due to the circumstances this last couple of weeks, and I know that there have been some very high end developments behind the scenes that simply aren't able to be posted live yet due to the fact they're not fully researched/finalised.

I will make an effort after Easter as that's my earliest time frame.

And I would also like to say thanks for posting this information on here. Your thoughtful post was comprehensive and well covered.

My only comments about those tutorials is that there was a post by a newcomer which I felt was displaying confusing delivery of information on telling people to change the source code. 

Your tutorials are for a fee? Or are these covered in your general registration? I am not sure about all this.  Armand and I have developed some skins which are tableless, xhtml compliant, light and fast, but require more tweaking and we'd like to put some more aesthetics into them, because commerically they're just too simple to be taken seriously I'm afraid, but we are working on some options too.

I expect we'll have delivery of things around May - no earlier.

Nina Meiers

Hello,

         Just my .02 cents real quick from a different perspective.  I've got to agree with Lee, DNN needs to validate weather it's using tables or CSS styles.  There are good arguments on both sides for using CSS over tables and I believe there are good reasons to use one or the other depending on what you are trying to do.  I've always been a guy that believed in using the right tool for a job and not using a tool just because it's the latest and greatest.  So weather to go completely table free CSS or not isn't really the big issue in my mind.  Having valid code as the end result is more important.

         From a user perspective and following DNN since the first released version I've noticed some things. Shawn, (it seems to me) started out aiming DNN more toward the intranet and internal sites where the IT department has control over the users browser of choice and valid html wasn't as much a concern. Starting with the later version of DNN 2 and really kicking into high gear from 3.0.13 there has been a much higher interest from the community toward using DNN on the internet, outward facing where there is no control over the browser.  But there hasn't yet been as big a change in the target of the core.  This seems to be changing a little bit but the levels of the project team leaders.

         To get valid code wouldn't take much.  Running my sites through the validator doesn't show a lot of horrible things.  Just lots of unclosed tags double tags and for some reason an unquoted attribute that is quoted. (not sure about that one.)  I've not read any of the tutorials yet but did at one time go through all of the core code cleaning up some simple stuff that almost fixed all of the validation errors.  The one I couldn't get rid of was the unquoted attribute since I couldn't figure out how to fix something that didn't have anything wrong with it.

         I offered the changes I made and even posted them here in one of the fourms and was basically told to go away we don't want your stuff, your not one of us.   So I just kind of got the idea that maybe it was only important to me and maybe a few others. :)

          Anyway now that DNN is getting more and more popular and facing the internet more maybe it's time to consider being more valid.

Cheers,