I posted a temporary text about DNN 5 skins and skinning here:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/109/threadid/276990/scope/posts/Default.aspx

Thanks, Timo.  Add my vote to reverting back to case-insensitive comparisons with file names, class names, and content pane names.  I've found that classes are also case sensitive so reference to class="CssClass" will not be styled by the class ".cssclass" in the skin.css unless it's renamed to ".CssClass".  Although, I am a huge fan of structure and orginazation and imho standards can be very helpful, so maybe it will teach us to be more consistent in our coding which would be a good thing, right?

On the other hand, I'm also a huge fan of non-conformist thinking and have authority figure issues, which thankfully doesn't really apply in this case. :)

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

One issue with case sensitivity is that DNN doesn't interface wll in VS/VWD for Intellisense in adding CSS classes or most other options.  I understand why, since the ASCX of the skin doesn't reference the CSS, but a connection with Intellisense can make dealing with case a bit easier.

That said, our standard has become all lower case, never a case issue then.  The skins with DNN 5.0 don't seem to use a standard naming or casing, so that can cause confusion too.

Jeff