• Introduction
• Account Types
• Prerequisites
  • CDN DNS
• Workspace
• Architecture
• Extensions
• Nodes
• Layouts
  • Masters
  • Templates
  • CMS Form Tag
• Items
  • Child Items
• Draft Items
• Item Actions
• Caching
• Media Management
• Users & Groups
• Security
• Site Settings
  • Languages
  • Global Values
  • Properties
  • Data Definitions
  • User Profile
  • Membership User Profile
  • Membership Settings
  • Response Headers
  • Rewrite Directives
  • Page Redirects
  • Admin Timezone
  • Site Performance
  • Exceptions & Messages
  • MIME Types
• Tokens

Core Modules Documentation

To create a new Template:

1. Click the Cms > Layout > Templates node.
2. Click the "New Template" button.
3. Specify the following information:
   1. Name - Friendly name to refer to the Template
   2. Master - Optional.
   3. Domain & sub domain - The domain and sub domain that this Master will be used for. To learn how to add domains and sub domains, click here. If a Master is used, then the domain and sub domain settings are pulled from the Master.
4. Click "Ok".

If a Template uses a Master, then the new Template will have CMS Content controls for each corresponding CMS Placeholders specified in the Master. Below is an example of a Template using a Master.

<Cms:Content PlaceHolderName="HeadSection">
    <Cms:CssLink Href="/styles/custom.css" Media="screen" />
</Cms:Content>

<Cms:Content PlaceHolderName="PlaceHolder1">
    <h1>Header</h1>
    <div>
        Main Content
    </div>
</Cms:Content>

The CMS Content tags correspond to the CMS PlaceHolder tags in the Master through the PlaceHolderName attribute. The CMS Content tags contain markup specific to the Template and will be injected into the CMS PlaceHolders during rendering. If a Template uses a Master, then all markup and CMS controls must be contained inside CMS Content controls.

Below is a table showing the available CMS controls on a Template. Each control can be inserted using icons in the tool bar above the Template content area.

Control Name	Summary
Content	A control tag who's inner content is injected into the corresponding PlaceHolder tag on a Master.
User Module	Renders a custom user module's item.
Global Value	Renders a global value as defined in Site Settings > Global Values.
jQuery	This is a marker control informing the layout engine to include the jQuery framework script as defined in the Global Value: Javascript Frameworks > jQuery. The placement of this control in the Master does not matter as it will be included as the first script in the first script include control found during rendering.
Script Link	Renders and registers a javascript link during rendering. By registering the link the layout engine will not render any other duplicate script links that might have been registered by another module present on the page.
CSS Link	Renders and registers a CSS link during rendering. By registering the link the layout engine will not render any other duplicate CSS links that might have been registered by another module present on the page.
Includes	Supports two types: "Css" and "Script". This control represents the placeholders of each type that modules and items can inject registered links and content.
Custom View	Renders a custom Razor file. FilePath attribute is required. Learn more about Custom Views.
Region	Defines a user editable/sortable region where other CMS Items and Modules will be rendered.
Value	Defines an input where a CMS user can provide content. The placement of the Value control indicates where the user provided content will be substituted. To learn more about Values and Snippets, click here.
Snippet	Defines a group of Values and Snippets where a CMS user can provide content. The placement of the Value control indicates where the user provided content will be substituted. To learn more about Values and Snippets, click here.
Built-in Modules	In addition to the Master specific controls, most built-in module items can be directly placed inside a Master for rendering. Since the built-in Page module is the top level module in the CMS during rendering, other Page module items cannot be directly placed in the Master. To learn more about the built-in modules, click here.