Pages within DotNetNuke provide a location, and URL, for the content organization of a website. When you create a page in DNN you can apply a Skin
which will control the layout and placement of Panes
in which you can place Modules
.Page Best Practices
- Never rename a page, always create a new page with the new Name and use the Permanent Redirect option from the old to new page.
- When first creating a page make it only available to certain roles that will edit the content, once it is ready for public view enable the All Users role
Editing a Page
The permissions section is different here depending on the Permissions Provider
set in the web.config. In default CE (Community Edition) installs, each row in the data grid represents a role (or user) and the two permission types available (columns) are "View Page" and "Edit Page".
This section determines how the page will behave when viewed (or clicked in the navigation menu). If SSL is enabled, at the portal level, page editors have the option of securing the page (via https) by checking the "Secure" checkbox here. The "Site Map Priority" is used in combination with the Sitemap Provider
to determine how the priority is set for the page in the rendered SEO site map. The start and end dates are used to determine when the page is active and available for viewing.
The "Link Url" field determines what will happen when a user clicks the page in the navigation menu. You have the following options:
- This behaves as a normal DotNetNuke page.
- This is used to link to an external resource (ie. an outside website).
- This will allow you to choose from a list of existing pages in the current site.
- This will link to a file contained within the site. Please note, the file must exist in the DotNetNuke file system (ie. accessible via the File Manager).
The final options is "Permanently Redirect" which, when checked, tells any indexing bots following the link that the resource previously assigned has permanently moved to a new location (this renders a 301 response code).