DotNetNuke skinning has only a few basic requirements. If you can design and program in HTML and follow the few simple rules enforced by the skinning engine, you can build beautiful designs for your DotNetNuke site. A few things to keep in mind when working with a DotNetNuke Skin package are:
Skins can be set at the site level and overridden at the page level, with the exception of Admin skins.
Containers can be set at the site level, overridden at the page level, and then at the module level, with the exception of Admin containers.
Each skin or container must have one Content Pane named ContentPane.
Tokens are extended using XML files also referred to as manifest files.
Skins and containers are installed using the DotNetNuke web interface and sometimes the capability to install them is only available only to SuperUsers.
Many examples of both free and commercial skins are available for you to use as references when creating your skins and containers. There are quite a few examples on the www.dotnetnuke.com web site and in the solution, as well as a multitude of resource sites in the DotNetNuke directory. Download some of these examples and, coupled with the knowledge contained in this chapter, you will create high-quality skins of your own in no time. If you can imagine it, then you can build it with the DotNetNuke skinning engine.