Sorry, I'm new to DNN and not familiar how things work around here.

Hadn't realized that there is no formal release process where the documentation team gets access to the new code (during beta or RC times) so that new features can get a preliminary documentation that can be included with the actual release.

I agree, if all these features were conceived, coded and added on 12/23, then it's impossible to have them documented by 12/24.  ;-)

I see a lot of potential in DNN and I think it's amazing what has been accomplished. That's why I feel it's important that the delivery process be improved so that all these great features reach the intended users. Once I'm ready to get into module development, I intend to contribute to "give back" and show my appreciation.

I agree with some of the comments that the DNN 5 skinning documentation should have been ready.

It isn't and I'm sorry about that.
It took me a lot of time to get the new skin to play nice with "all" browsers (read IE6) and I have a lot of commercial custom skinning work ATM.
Also please remember that the changes discussed here are core changes, (a skin is now an extension), this means the idea to spend 5 minutes after programming would not apply in this case (if at all).

I'm working on a blog with an overview of changes for DNN 5 skinning, I'll post that ASAP.
 

wacktronic,

Try the VBscript I mention in a early post... it creates a minimum manifest that will allow you to load old skins and containers.  also see this post

Paul.