• Documentation
  InstallationUsing the Kentico interfaceDeveloping websitesConfiguring KenticoManaging usersSecuring websitesDeploying websitesManaging website contentMultilingual websitesMacro expressionsExternal utilitiesIntegrating 3rd party systemsCustom developmentE-commerce featuresOn-line marketing featuresIntranet featuresCommunity featuresRunning Kentico on Microsoft AzureUsing Amazon web services with KenticoCertified extensionsReferencesRelease notes - Kentico 9
• Tutorial
  Getting started with KenticoUsing the Kentico interfaceSite development overviewCreating a new websiteAdding styles to the websiteWorking with the Pages applicationCreating the master pageCreating website pagesCreating page templatesNext steps
• API Examples
  Content managementOn-line marketingE-commerceSocial and CommunityDevelopmentConfiguration

• The CMSPagePlaceholder control creates an area on the page that behaves like a portal engine page template. You can place multiple CMSPagePlaceholder controls onto a single page.
• The content of the <LayoutTemplate> element defines the layout of the area. You can specify a table structure or a CSS-based layout applies through HTML elements (<div>, <span>, etc.).
• The layout may contain multiple CMSWebPartZone controls, which represent fully functional portal engine zones. You can configure every zone to serve as either a standard web part zone or any type of widget zone. Users can manage these zones when editing pages based on the page template on the Design tab of the Pages application. When web part or widget content is added to a zone, information about it is stored in the database along with the respective page template object, not in the actual code of the ASPX page.

When registering ASPX page templates with portal engine functionality in the Page templates application, you need to set the Template type to ASPX + Portal page. This enables the Design tab when editing pages based on the template in the Pages application.

Example

The following example demonstrates how to create an ASPX page template with zones that users can design via the portal engine:

1. Build a new page template according to the example on the Creating ASPX page templates page.

   • When writing the template's ASPX code, place the following inside the <asp:Content> element:

     XML

     Copy

     <cms:CMSPagePlaceholder ID="plcZones" runat="server">
         <LayoutTemplate>
             <table style="width:100%">
                 <tr>
                   <td style="width: 50%">
                     <cms:CMSWebPartZone ID="zoneLeft" runat="server" />
                   </td>
                   <td style="width: 50%">
                     <cms:CMSWebPartZone ID="zoneRight" runat="server" />
                   </td>
                 </tr>
             </table>
         </LayoutTemplate>
     </cms:CMSPagePlaceholder>

     This code defines two editable web part zones in a basic two column table layout.

   • When registering the template in the Page templates application, set the Template type to ASPX + Portal page.

2. Open the Pages application and add a Page (Menu item) page to the content tree using the new page template.

3. Switch to the Design tab of the new page. You can see two web part zones on the page.

4. Expand the menu () of the zoneLeft zone and click Configure.

5. Switch the Widget zone type property from None to Customization by page editor.

6. Click Save & Close.

   • The zone now serves as a widget zone for page editors.

7. Add a web part to zoneRight, for example Editable text.

8. Open the Page tab.

   • Here you can manage the editor widget zone on the left and enter content into the editable text region displayed by the web part on the right.

9. Open the menu of the editor zone () and click Add new widget to place some widgets onto the page.

10. Save the page.

The example demonstrates how to use web parts or widgets to build the design of pages based on ASPX page templates. This approach combines the standard architecture and development process of ASPX templates with the flexibility and user‑friendliness of the portal engine.