Document Tree
Document Properties
Last Modified
Added to KB
Public Access
Doc Type
  • ICM 7.10
  • ICM 11
  • ICM 12
Concept - CMS - Overview


On this page, you can find an overview with links to all sub-concepts of the CMS concept. A much more detailed introduction gives an idea of the CMS structure and basic concepts.


Commerce Management application (Back Office)

Intershop Studio

Meta Model Class

Model Element (in *.pagelet2 files)


Context Object Relations are only indirectly visible when one creates product or category pages/includes. Their display name goes in front of the display name of the respective page/include types, i.e. the page/include types extending the content object relation. A direct runtime equivalent of content object relations does not exist.

Content Object Relation




Page Type

Page Entry Point




Include Type

Component Entry Point




Page Variant Type

Pagelet (pagelets with their page flag set to true)




Component Type

Pagelet (pagelet with their page flag set to false)




Slot Type





Page Template Type

Pagelet (pagelets with their page flag set to true)



There is no distinction between page and component templates at the content model layer; it is determined at PO layer by a flag 'template' at PageletPO

Component Template Type

Pagelet (pagelet with their page flag set to false)




Configuration Parameter

Configuration Parameter




There is no equivalent in the back office; configuration parameters are implicitly visible by configuration parameters derived from them.

Configuration Parameter Type





Call Parameter Interfaces





For questions and typical problems related to the CMS concept please refer to the Cookbook - CMS (7.8 - 7.9).

Configuration Parameters

A configuration parameter represents a leaf in the content composition tree. For more details refer to the sub-concept Configuration Parameters.

Call Parameters

A lot of content instances cannot be executed independently. The content model that the instance is based on determines the parameters this parameter set contains. It does so by providing further elements called Call Parameter Definitions. The sub-concept of call parameters is described here: Concept - CMS - Call Parameters.


The structure and properties of pagelets, i.e., page variations and components, are described here: Concept - CMS - Pagelets.

Content Entry Points

Content entry points are described in the sub-concept Concept - CMS - Content Entry Points.
To achieve the composition of pagelets a data structure must be present to connect a content entry point (on one side) with a pagelet (on the other side).

View Contexts

View contexts are meant to associate arbitrary business objects with content in the form of pages or includes to supply them with individual visual representations in the storefront. For more information see here: Concept - CMS - View Context.

Content Templating

The main idea behind content templating is to have a means to define new content by re-using already existing content. In this way, the content manager does not have to deal with complex content structures. For more information see: Concept - CMS - Content Templating.

Content Completeness Check

The basic idea behind completeness checks of CMS objects is to deliver a control tool to measure possible pain points. For more information see Concept - CMS - Completeness Checks.

Content Sharing

This concept provides an overview of content sharing as it has evolved with the introduction of application awareness of the CMS framework. Business users gain an understanding about the general content sharing principles whereas developers additionally get an overview of how content sharing is applied technically and how they can detect and handle content sharing using an API for it.

For more information see Concept - CMS - Content Sharing.

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.
The Intershop Knowledge Portal uses only technically necessary cookies. We do not track visitors or have visitors tracked by 3rd parties. Please find further information on privacy in the Intershop Privacy Policy and Legal Notice.
Knowledge Base
Product Releases
Log on to continue
This Knowledge Base document is reserved for registered customers.
Log on with your Intershop Entra ID to continue.
Write an email to if you experience login issues,
or if you want to register as customer.