In the previous section we looked at WebMail. In this section we will look at Design of the Site.
Download a PDF version of this lesson (10k) Design of the Site. This lesson is a sample from the manual..
Design of the site is implemented through a skin process in DotNetNuke.
DotNetNuke has three main layers:
- Database and infrastructure layer (provided by WebSuburb)
- Content layer provided by the user
- Design layer - customised with skin modules
We will examine a few aspects of the design
Choosing a skin
- 3rd Party skins - There are hundreds of 3rd party skins available for free download or for purchase. Google DotNetNuke Skins.
- The default skins - DotNetNuke is installed standard with a number of default skins. Samples of these may be viewed on WebSuburb.com.au .
- Customised skins - A graphic designer can create a customised skin for the website. Explanation and examples of the process are on a separate page on this site. Obviously this route requires significantly more effort than the above two options and is significantly more expensive than the first two options.
DotNetNuke Skinning Competition
DotNetNuke organises skinning competitions to demonstrate the capability of the software to accommodate customised designs. Check out
www.dotnetnuke.com/default.aspx?tabid=684
http://www.dotnetnuke.com/Community/SkinningContest/Entries/tabid/1435/Default.aspx
Changing skins
There are two types of skin:
- Page skins can be applied:
- To all the pages in the site (refer to 6.4 below)
- At an individual page level. (refer to page advanced settings 3.4.2)
- Module skin. For modules the skin is referred to as a container i.e. the borders surrounding module content. Modules skins can be applied
- To all modules in the site (refer to 6.4 below)
- To all modules on a page (Refer to Pages advanced settings 3.4.2)
- To an individual module (refer to modules Pages basic settings 3.7.2.1)
Click here to return to