---
title: Adding portal engine functionality to ASPX templates
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

When developing or maintaining a website using ASPX page templates, one of the drawbacks is that you need to manually modify the code of pages whenever you wish to change the design. You can add flexibility to ASPX templates by defining areas that are editable directly through the browser in the **Pages** application, just like when using the Portal engine development model. To learn more about portal engine features, please read the version of this tutorial dedicated to the portal engine.

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

## Writing the ASPX code

1. Open your web project in Visual Studio (using the **WebSite.sln** or **WebApp.sln** file).
2. Right‑click the **CMSTemplates\CorporateSite** folder in the Solution Explorer and select **Add -> Add New Item**.
3. Create a new **Web form** named: _TwoZones.aspx_
   - Check the **Select master page** box.
4. Click **Add**. The **Select a Master Page** dialog opens.
5. Choose the **Root.master** page from the **CMSTemplates/CorporateSite** folder and click **OK**.
6. Open the **Source** view of the new ASPX page and place the following inside the **\<asp:Content>** element:

   ```xml

   <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>

   ```

   > **Info:** The **CMSPagePlaceholder** control creates an area on the page that behaves in a way similar to a portal engine page template.
   >
   > The **\<LayoutTemplate>** element defines the layout of the area. This example uses a basic two column table structure, but setting a CSS‑based layout applied through HTML elements (for example \<div>, \<span>) is also a valid option.
   >
   > The table contains two **CMSWebPartZone** controls, which represent fully functional portal engine zones. 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, the system stores the information in the database along with the respective page template object, not in the actual code of the ASPX page. Communication with the database is ensured by the **CMSPortalManager** control, which is located on the Root.master page.
7. Switch to the code behind file (**TwoZones.aspx.cs**) and add a reference to the **CMS.UIControls** namespace:

   ```csharp

   using CMS.UIControls;

   ```
8. Modify the class definition to inherit from the **TemplatePage** class:

   ```csharp

   public partial class CMSTemplates_CorporateSite_TwoZones : TemplatePage

   ```
9. Save the web form's files.

You can now use the web form as a page template in Kentico.

## Registering the ASPX page as a page template

1. Log in to the Kentico administration interface and open the **Page templates** application.
2. Select the **Corporate Site/Examples** folder.
3. Click **New template** and type _**Two zone template**_ into the **Template display name** field.
4. Click **Save**. The system creates the template and displays its **General** tab.
5. Select the _**ASPX + Portal page**_ option for the **Template type** property. This is necessary in order for the **Design** tab to be available when editing pages using the template in the **Pages** application.

   ![Registering an ASPX page template with portal engine functionality](https://docs.kentico.com/docsassets/k8tutorial/adding-portal-engine-functionality-to-aspx-templates/ASPX_Template_Mixed.png "Registering an ASPX page template with portal engine functionality")
6. Enter the following path into the **File name** field: _**\~/CMSTemplates/CorporateSite/TwoZones.aspx**_
7. **Save** the changes.
8. Switch to the **Sites** tab and use the **Add sites** button to assign the page template to the site that you are using (Corporate Site).

## Using ASPX + Portal engine templates

We will modify the **About Us** page created in the previous example to use the new page template.

1. Open the **Pages** application.
2. Select the **About Us** page and switch to the **Properties -> Template** tab.
3. Click **Select** and choose the _**Corporate Site/Examples/Two zone template**_ page template from the catalog.
4. Click **Save** to confirm the page template change.
5. Refresh your browser window and switch to the **Design** tab, which is now available for the **About Us** page. You can see two empty zones on the page as defined in the ASPX code of the template. To define the content of standard zones, add web parts.
6. Drag the **Editable text** web part from the toolbar into **zoneRight**
7. Double-click the web part header in the zone and set the following properties:
   - **Design -> Editable region title**: Right text
   - **Design -> Editable region height**: 400
8. Click **OK**.

This web part provides a text area on the page that users can edit on the **Page** tab of the **Pages** application, just like the editable regions in the previous example. The template allows you to build the design of the page using a browser‑based interface. Each web part zone may contain any number of web parts.

You may also configure zones to use various types of widgets, which are objects similar to web parts, but allow page customization by different kinds of website users, not just the administrators or designers.

1. Expand the menu () of **zoneLeft** and select **Configure**.

   ![Configuring a portal engine zone](https://docs.kentico.com/docsassets/k8tutorial/adding-portal-engine-functionality-to-aspx-templates/ASPX_Mixed_Zone_Menu.png "Configuring a portal engine zone")
2. Switch the **Widget zone type** property from _**None**_ to _**Customization by page editor**_.
3. Click **Save & Close**. The zone now serves as a widget zone for page editors.
4. Switch to the **Page** tab
5. Type some content into the editable text region displayed by the web part on the right and click **Save**.
6. Open the menu of the editor widget zone (click ) and click **Add new widget**. Select the **Newsletters -> Newsletter subscription** widget from the catalog and set the following values for its properties:
   - **Newsletter name**: Corporate Newsletter
   - **Allow user subscribers**: disabled (unchecked)
   - **Widget container**: Corporate site - Light gradient box
   - **Widget container title**: Newsletter subscription
7. Click **OK** to add the widget and then **Save** the page.

The widget provides a form which users can use to subscribe to the site's newsletter.

![Editing widgets and editable region content of a page based on a mixed template](https://docs.kentico.com/docsassets/k8tutorial/adding-portal-engine-functionality-to-aspx-templates/ASPX_Mixed_Result.png "Editing widgets and editable region content of a page based on a mixed template")

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.