Hello, I'm new to DNN and we are evaluating it as a platform for some portal software we are developing.  Could someone please confirm or deny the following synopsis of DNN skinning?

DNN supports almost any skin one could desire for high-performance web sites.  There are hundreds of skins for sale at http://www.snowcovered.com and elsewhere for under $50.00.  There are dozens of firms that will fix-bid DNN skin development.  The market for DNN skins and development services exists because DNN is very popular but there is no fool-proof tool for building DNN skins.

Inside DNN, skins are implemented as ASP.NET user controls that include embedded references to CSS classes, web graphics files and predefined user controls that represent content, e.g. a users login name or the customers logo.  People who develop DNN skins usually use VS.NET 2005 or VS Web Developer 2005 Express Edition that can be downloaded for free at http://msdn2.microsoft.com/en-us/express/aa975050.aspx .  It is also possible to use non-Microsoft tools such as DreamWeaver.  Regardless, the user needs a basic understanding of HTML and CSS syntax to build DNN skins with an HTML editor.  This wide-open approach gives a skilled developer the freedom to create a stunning look and feel.  But, the unskilled skin developer has plenty of opportunities to fail.  After they create the skin HTML, CSS stylesheet and graphics, they must bundle them all into a zip file arranged into the proper subfolders.  They then use a DNN facility to upload the zip file.  If the skin is defined in HTML, the DNN skin engine will automatically translate it into an ASP.NET user control.   If the zip file and its contents are valid, the user sees a lengthy message telling them that the skin was successfully uploaded or not.  Skin import error messages are difficult to interpret for the uninitiated.  If the skin is successfully uploaded, the user must update the appropriate portal settings or portal page settings to apply the new skin.  

The entire authoring process for DNN page skins must be repeated to define skins for DNN modules called containers.  Container skins may be applied to any module.  

If you need to change some portion of an existing skin, you either take the risky approach of editing the appropriate skin user control in place using VS.NET OR you unbind the skin from all the portals that use it, remove it, import the updated version and then rebind it to the appropriate portals.  One cannot remove a skin that is currently in use.