---
title: Create a generic page template
---

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

## Apply the same concept to a more general page template

Looking over the page template we've just created, you may find it a bit of a waste to have all these options for Page Builder layouts and appearance available only for service pages.

Since most of what we've made is reusable, it will be straightforward to create a more general-purpose page template that has these Page Builder features, and can be used on any page type.

1. Create a new _\~/Features/Shared/Templates_ folder.
2. Add a new page template properties file called _GeneralPageTemplateProperties.cs_.
3. Include the same properties as _ServicePagePageTemplateProperties.cs_, except for the checkbox. This template will always use Page Builder areas.
   ```csharp title="GeneralPageTemplateProperties.cs"
   using Kentico.PageBuilder.Web.Mvc.PageTemplates;
   using Kentico.Xperience.Admin.Base.FormAnnotations;
   using TrainingGuides.Web.Features.Shared.OptionProviders;
   using TrainingGuides.Web.Features.Shared.OptionProviders.ColumnLayout;
   using TrainingGuides.Web.Features.Shared.OptionProviders.CornerStyle;
   using TrainingGuides.Web.Features.Shared.OptionProviders.ColorScheme;

   namespace TrainingGuides.Web.Features.Shared;

   public class GeneralPageTemplateProperties : IPageTemplateProperties
   {
       [DropDownComponent(
           Label = "Color scheme",
           ExplanationText = "Select the color scheme of the template.",
           DataProviderType = typeof(DropdownEnumOptionProvider<ColorSchemeOption>),
           Order = 10)]
       public string ColorScheme { get; set; } = nameof(ColorSchemeOption.TransparentDark);

       [DropDownComponent(
           Label = "Corner type",
           ExplanationText = "Select the corner type of the template.",
           DataProviderType = typeof(DropdownEnumOptionProvider<CornerStyleOption>),
           Order = 20)]
       public string CornerStyle { get; set; } = nameof(CornerStyleOption.Round);

       [DropDownComponent(
           Label = "Column layout",
           ExplanationText = "Select the layout of the editable areas in the template.",
           DataProviderType = typeof(DropdownEnumOptionProvider<ColumnLayoutOption>),
           Order = 30)]
       public string ColumnLayout { get; set; } = nameof(ColumnLayoutOption.OneColumn);
   }
   ```
4. Add a view called _GeneralPageTemplate.cshtml_, copying the parts from _ServicePagePageTemplate.cshtml_ that are not specifically related to services.
   ```cshtml title="GeneralPageTemplate.cshtml"
   @using Microsoft.AspNetCore.Html
   @using TrainingGuides.Web.Features.Shared
   @using TrainingGuides.Web.Features.Shared.OptionProviders.ColumnLayout
   @using TrainingGuides.Web.Features.Shared.ViewComponents

   @model TemplateViewModel<GeneralPageTemplateProperties>

   @{
           if (!Enum.TryParse(Model.Properties.ColumnLayout, out ColumnLayoutOption columnLayout))
           {
               columnLayout = ColumnLayoutOption.OneColumn;
           }
   }
   <tg-component-style color-scheme="@Model.Properties.ColorScheme" corner-style="@Model.Properties.CornerStyle">
       <vc:page-builder-columns column-layout-option="@columnLayout" editable-area-options="@new EditableAreaOptions()" />
   </tg-component-style>
   ```
5. Register the template in a file called _GeneralPageTemplate.cs_.
6. Do not include the `ContentTypeNames` property.

   > **Info:**&#x20;
   >
   >  Omitting 
   >
   > `ContentTypeNames`
   >
   >  allows the template to be used for any page content type. 

   ```csharp title="GeneralPageTemplate.cs"
   using Kentico.PageBuilder.Web.Mvc.PageTemplates;
   using TrainingGuides.Web.Features.Shared;

   [assembly: RegisterPageTemplate(
       identifier: GeneralPageTemplate.IDENTIFIER,
       name: "General page template",
       propertiesType: typeof(GeneralPageTemplateProperties),
       customViewName: "~/Features/Shared/Templates/GeneralPageTemplate.cshtml",
       IconClass = "xp-square")]

   namespace TrainingGuides.Web.Features.Shared;
   public static class GeneralPageTemplate
   {
       public const string IDENTIFIER = "TrainingGuides.GeneralPageTemplate";
   }
   ```

Now, if you sign in to the administration interface, you should have a general-use page template with properties to determine its color, corner styling, and editable area layout.

🎬 [Video](https://docs.kentico.com/docsassets/modules/create-general-template/VideoTemplatePropertiesGeneralFinal.mp4)

## Wrapping up

If you need a refresher, feel free to take another look at the [beginning of this series](https://docs.kentico.com/modules/page-builder/meet-requirements-with-page-builder.md) to review the mockups of the page functionality we've been working to implement so far.

> **Tip:** **Apply your knowledge**
>
> If you'd like to put your knowledge to the test, try swapping out the `UsePageBuilder` checkbox in `ServicePagePageTemplateProperties` for another enumeration-based dropdown.
>
> Create a third option which keeps the structured service data, while rendering editable areas at the top and bottom of the page.