While Web pages are nodes in your portal’s sitemap which represent content accessible to portal users, Page Templates represent the actual .aspx pages which provide a means to maintain a consistent look and feel throughout your entire website. Page templates are built using ASP.NET pages, master pages, cascading style sheets (CSS), user controls, and server controls.

When creating a new web page for the site, whether through front-side publishing or through the CRM interface, you must select a page template which will present the page’s content to users of the portal.

Web Page vs. Page Template

The difference between web pages and page templates is perhaps best understood as the difference between an exact URL and an actual .aspx page which acts as a blueprint for displaying content. Each webpage represent a specific URL in your site, which users can navigate to. When a user navigates to a URL, the content associated with that URL is displayed. However, a webpage contains no information on how that content is displayed.  This is determined by the page template, which is the actual .aspx page which generates the HTML that the user sees.  For instruction on actually adding a new page template, see the developer's guide.

Utilizing Page Templates

When you create a new webpage, you must choose a page template from a list of existing templates.

Several Page templates are included with each of the start portals. When using these portals as a base for your own website, these templates will come in handy as a basic means of demonstrating the functionality of the portal. However, a developer will be necessary to significantly change the layout of these pages. In most cases, the “Page” page template will be the page template to use as it is general purpose: a web page using this template will have its content displayed, as well as a list of child pages presented as navigation items.

The other templates are used for specific pages such as the login page, page not found page, site map, and other feature-specific pages that likely won’t be widely reused outside of their intended functionality. Documentation of any useful out-of-the-box templates is integrated into documentation dealing with the features that they related and can be found in the appropriate sections.

Creating a new Page Template

Creating a new Page Template is only necessary when creating a brand new .aspx page to display content on your website, a developer’s task. In fact, for the purposing of simply customizing the layout of your site, a developer can largely just modify existing .aspx pages.

  • Navigate to Portals -> Page Templates
  • Click New

Page Templates

Specify values for the fields provided.

Name Description
Name  Name of the template used for reference.
Website  The associated Website.

The type of the template, which controls how the template will determine what to render.

  • Rewrite: Will use the Rewrite URL field to render a given ASP.NET template.
  • Web Template: Will use the Web Template field to render a given Web Template.
Rewrite URL

Path of the physical ASP.NET .aspx page (or other resource, such as .ashx) which will be rendering the content.

(Only valid if Type is Rewrite URL.)

Web Template

A reference to a Web Template to that will be used to render this template.

(Only valid if Type is Web Template.)

Is Default If 'Yes' then the template will be the default assigned to the dropdown in the client-side editing tools.
Entity Name

The CRM page entity type that this template expects to render. This will be use by the front-side editing system to present only appropriate template choices to content authors.

Usually, this will be Web Page (adx_webpage), but may be another Adxstudio Portals CMS entity, such as Event, Forum, Forum Thread, Blog, or Blog Post.


A description of this template, for the benefit of front-side editing users.