DotNetNuke uses a skin, or template if you prefer, to define the web pages. A skin may be used throughout the whole site, or specifiedon a per page basis.
A skin is a mix of HTML and graphics, even Flash, for example http://www.ultramagic.co.uk/. Note that by default flash (.swf) files are not a permitted at upload time. You will need to ask your portal administrator (host) to change the configurations on your portal to enable flash files to be uploaded.
Skins are easy to install, they are usually made available as a zip file, comprising the various components which make up the skin, an HTML file, possibly CSS and XML files, and a number of image files. DotNetNuke also has a number of special objects, for example [MENU] or [CURRENTDATE].
Similar to skins are containers. Each module which is added to a page may itself be placed in its own mini skin. This defines where the title text for the module appears, allows the module to be minimised and provides an or colour wrapper for the module.
Skins are prepackaged and available on the Internet. Our own site will soon be offering skins for purchase.
Skins admin tab
From the Skins Admin Tab skins and containers which have already een uploaded and made availabel either specifically for your web site, or globally may be viewed. Here we can select to view either containers or skins by their group name, this is typically based upon the supplier name, or the name by which the theme is known.
Selection of skins and containers by preview.
Having selected whether to view skins or containers we are able to see an image representing each, assuming that this was included within the original package.
NAT February 2006 (Revised)