Navigate to: CMS > Page Template

1. Download one of the out-of-box Page Templates to use as a starting point.

2. Make adjustments based on custom requirements, using widgets where applicable.

   1. If making adjustments the following will need to be addressed

      1. The Widget Syntax will need to be updated if re-used per instructions - Working With Widgets
         <z-widget>@Html.WidgetPartial( "Widget Name" , "Widget Display Name" , "Widget Key" , "Portal Mapping Type" , "Portal Id" )</z-widget>

      2. Widget Key - The purpose of a widget is to reuse a control on multiple pages. In order to use the same widget on different pages, we need a differentiating key which is the widget key. If we want to render the above widget, an offer banner, on a different page then we need to use a different unique widget key. (Numeric Value)

3. Rename the custom template if one of the out-of-box Page Templates to use as a starting point

4. Upload the static HTML page to the Page Template section of the CMS. 

   1. Setting up the admin view within the Znode theme - Setting up the admin view within the Znode theme 

      1. An Administrator has two options for setting up the admin view within the Znode theme. 

         1. Administrators can manually copy the views found in the webstore and put them into the admin view. 

         2. Administrators can create a symbolic link between the two. The second option is the most efficient approach, this will take care of all the files that need to be copied.

      2. Copy the same views found in the webstore and put them in the admin.  (Continuously)

      3. Navigate to the current path of your local Znode install and copy the Themes folder found in

         1. IeC:\dev\znode\ZnodeMultifront\Projects\Znode.Engine.WebStore\Views

      4. Paste the Themes folder into the Admin folder 

         1. Ie C:\dev\znode\ZnodeMultifront\Projects\Znode.Engine.Admin

      5. So Znode.Engine.Admin contains the newly copied Themes folder.

Information on context for the user/developer to test the template

1. The user/developer has the ability to add the route of their choice by setting the SEO Friendly URL.
2. If the user/developer does not want to do this, then the page will use a route auto-generated.
3. The preview URL setup will allow the user/developer to preview inside the CMS