DNN Skins

Click here to change the theme.

Skins are usually contained in a container. They are both extensions. Skins consist of:

  • Dynami Elements
  • Panes
  • Modules
  • Containers

Modules can be placed in panes.

A skin must have at least one pane but can have more than one.

A module can be put in a container in a page.

A skin is one file, either a HTML or ascx file but they are always ascx files after installation. If HTML is used then the package must also have a XML file specifying the custom attributes.

A skin package consists of multiple skins and consists of many files that can include images. Most files are ascx files. An ascx file can be either a skin or a container. There are also XML files. A dnn file is the manifest. XML files are document types. There is also a skin.css file.

A skin consits of an ascx file, a document type file and a JPEG (preview) file.

The default skin type is DarkKnight.

Skins are in the Portals folder in the DNN root. The Portals folder has a "_default" folder and folders with numbers for each of the portals. Under each of those are "Containers" and "Skins" folders. The Skins folder has a folder for each iinstalled skin.

DNN look in the files for tokens (skin objects) that it converts to ASP .Net controls.

A skin must have a ContentPane and can consist of only a ContentPane. All other panes can be named whatever you want.

To install a skin, uplaod the zip file. DNN will unzip then parses HTML files for tokens. Skins can be installed either to the host or site (portal) level. Skins could be copied directly to be installed. Then (go to the page to install to then select) "Host" | "Extensions". Edit the page and click on the "Manage" button then select "Install Extension Wizard". Select "Choose File" and browse to the zip file. You will get a Package Installation Report; click "return".

Then to use a skin as the default for all new ages at the host level, go to "Host" | "Host settings". In the Appearance section are Host Skin, Host Container, Edit Skin and Edit Container. An adminiatrator member can manage skins after that.

Containers are the same as skins in terms of consist of tile types, installation and management except for the number of panes.

CSS Precedence:

  • Default
  • Module
  • Skin
  • SkinFileName
  • Container
  • ContainerFileName
  • portal
  • Inline CSS

Verify the following: Each container contains one module and there is one skin per page.