I last night sat through most of the 'make your skin XHTML compliant' videos and found it informative on many levels.

However one ommission for me from the set of videos / supporting documentation was information on why XHTML compliancy is a good idea and why it is worth the effort. Now I could hazard a guess why it is a good idea (greater uniformity across different platforms / browsers / user agents devices, better interoperatbility with apps using XML, etc) but is it something for everyone / every site? I did find this page which attempts to motiavte XHTML compliancy but it was not very compelling (I do however note that it dates from 2004).

I think the 19th DNN Creative tutorial would benefit greatly from some info clarifying why XHTML complaincy is a good thing (and maybe identifying when - or for whom - it should not be a priority). 

Let me phrase it another way - to my knowledge the user experience for my DNN site is more-or-less unifrom across all major browsers and platforms. Why do I need XHTML complaincy?

(Aside: if this 'context setting' info is already there somewhere then apologies for missing it, but do please point me towards it).

eoghano

Hello,

Good questions, checkout this article: XHTML and best practice coding for skins and modules in DotNetNuke
there are also links to several resources at the end of the article.

Also have a look at: Semantic Code and Header Tags in DotNetNuke Skins

Basically it all leads to creating an accessible website with the added benefits of better performance and potential search engine results.