This content is archived. See latest version here

Last updated: Feb 23 2015

The content model is based on inheritance from model classes for content types, and provides flexibility to create customized content types in website implementations.

Content in EPiServer are pages, blocks, media files, and folders in CMS. It also is catalog content in EPiServer Commerce. The content type defines a set of properties that an item, for instance a page, consists of.

You can create a content type by adding a model class to your solution. You also can add and customize modify a content type using the administrative interface. 

During site initialization, EPiServer scans the assemblies in the bin folder and adds classes with the EPiServer.DataAbstraction.ContentType attribute by the synchronization engine. A content type is constructed by merging the settings from the model class with any settings that were defined in the administration view.

Settings defined in the user interface take precedence over settings from your model. (In the admin view, you can restore the content type to the state described by the model class.) You can see model types that were created in the admin view. For example, the URL segment follows the name of a folder, which means that the URL segment changes when the folder name is changed.

EPiServer content types

Related topics

Do you have feedback on this documentation? Send an email to For development-related questions and discussions, refer to our Forums on