Introduction
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.
Glossary
Commerce Management application (Back Office) | Intershop Studio | Meta Model Class | Model Element (in *.pagelet2 files) | Comments |
|---|---|---|---|---|
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 | c.i.c.pmc.capi.definition.pagelet.ContextObjectRelation | contextObjectRelations |
|
Page Type | Page Entry Point | c.i.c.pmc.capi.definition.pagelet.PageEntryPointDefinition | pageEntryPointDefinitions |
|
Include Type | Component Entry Point | c.i.c.pmc.capi.definition.pagelet.ComponentEntryPointDefinition | componentEntryPointDefinitions |
|
Page Variant Type | Pagelet (pagelets with their page flag set to true) | c.i.c.pmc.capi.definition.pagelet.PageletDefinition | pagelets |
|
Component Type | Pagelet (pagelet with their page flag set to false) | c.i.c.pmc.capi.definition.pagelet.PageletDefinition | pagelets |
|
Slot Type | Slot | c.i.c.pmc.capi.definition.pagelet.SlotDefinition | slots |
|
Page Template Type | Pagelet (pagelets with their page flag set to true) | c.i.c.pmc.capi.definition.pagelet.PageletDefinition | pagelet | 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) | c.i.c.pmc.capi.definition.pagelet.PageletDefinition | pagelets |
|
Configuration Parameter | Configuration Parameter | c.i.c.pmc.capi.definition.pagelet.ConfigurationParameterDefinition | configurationParameterDefinitions |
|
There is no equivalent in the back office; configuration parameters are implicitly visible by configuration parameters derived from them. | Configuration Parameter Type | c.i.c.pmc.capi.definition.pagelet.ConfigurationParameterType | configurationParameterTypes |
|
| Call Parameter Interfaces |
|
|
|
References
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.
Pagelets
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.