Creating your first pages and blocks in EPiServer

In my previous post about EPiServer I explained how to start a new EPiServer project. In this tutorial I will show you how to create page and block templates that can be used in EPiServer to create content. For now we keep it very basic.

Creating a page template

Go to the Model/Pages directory and right-click on this folder and choose New Item. Under C# select EPiServer and from that list choose Page Type. Name your new page type StartPage.cs.

visual studio create new page type

Add new Page Type

After that a file is created with some default content. We are going to create a simple blog website in this tutorial. The startpage will contain the blogs that the editor can create using EPiServer. Later we will also add the possibility to add comments to your blog and more.

For now our new startpage needs at least a header and a place to add blogs. So we need to add the properties to our model to hold this information:

Lets have a quick look at what we are doing here. First of all notice the attribute ContentType that we add before the definition of the class StartPage. This attribute tells EPiServer that this is content template. The DisplayName is the name shown in the EPiServer CMS when creating a new page and the Description is also shown there. The GUID is important for EPiServer. This ID is autogenerated and unique for every type (page,block etc). Its used by EPiServer to notice for example when you change the name of a class from StartPage to BlogPage for example. Without this GUID EPiServer cannot know that you changed the new. For EPiServer it would then mean that you deleted StartPage type and created a new BlogPage type. With the help of the GUID it can now recognize that you renamed your type instead of creating a new one.

Next notice that our StartPage inherits from PageData. This makes it a Page Type. Later we will make our pages inherit from a base class SitePageData or something similar so that we can add general properties required by all pages like meta title and meta description etc. PageData is an internal class of the EPiServer Core Library.

As you can see I created two properties. Both properties are virtual. That is important because otherwise EPiServer will give an error that you declared non-virtual properties.

More information about all possible property types can be found here:

Notice the [CultureSpecific] attribute. All strings have this attribute by default! What it means is that this property has a unique value per language. So in this example if we would create our startpage in Dutch we can add different blogs to our contentarea then on the English version.

More information about attributes used by EPiServer can be found here:

The GroupName tells EPiServer in which tab it should display the properties in the CMS. Here a enum is used but a string is also valid.

EPiServer CMS Tabs

EPiServer CMS Tabs

Now we have our model we also need a controller and a view. These can be easily created:

  1. Create a controller by right-click on Controllers and add New Item – Page Controller (MVC), and give it the name StartPageController
  2. Add a view by right-click on Views and create a folder named StartPage and then right-click on this folder, choose View, and name it Index.cshtml and make sure its empty.

Page controller

This is how probably your StartPageController.cs file looks like now. For now this is fine and leave it like it is.

Page view

This file is still empty. We need to add some html to show at least a very basic startpage. For now lets make the content look like this:

If you are new to Razor but you are familiar with Web Forms then this website could help you:

Check this page for an introduction to Razor:

Before we build our project and create our first content page lets take a quick look at the used Html helpers. Notice the use of @Html.PropertyFor. This is an Html helper and is EPiServer specific. Its a combination of the default Razor html helpers DisplayFor and EditorFor. What is does is in Editor mode is generates an editor to edit the property and in display mode it just displays the content.

More information about all possible Html Helpers supported by ASP Razor look here:

Further notice the model part:

This tells Razor to use the StartPage model. If you check our StartPage Controller you see that we also pass a StartPage model to our view. So this should work.

Ok now lets build it and then you can create your first page.

Creating a block template

Next lets create a block template. A block is very similar to a page with the only difference that a block cannot be accessed directly from the URL. Blocks are used when some content needs to be re-used on different pages. Blocks are created in the same way as creating a page type.

First right-click on the Models/Blocks and select New Item -> Block Type. Give the block the name AdvertisementBlock.cs.

Create a BlockController on a similar way. Also create a block view like you created a page view. So first create a folder Views/AdvertisementBlock and create a file Index.cshtml in this folder.

Block type (Model)

Block controller

Block view

Now you should be able to create a simple advertisement block in EPiServer. Nothing fancy yet but for now it will do.



  1. Just wanted to say thanks for taking the time to write these blog posts. Start a new job with a company using EPiServer and this is proving very valuable training 🙂



Leave a Comment.