Configuration Container Page templates

create pages that serve as container nodes for various configuration pages

  • Configuration Page template
  • Lead Configuration Page template
  • Errors Configuration Page template

Configuration containers are designated templates to create container nodes for specificly assigned other pages. Containers templates are: Configuration Page, Lead Configuration Page, Errors Configuration Page.

on this page:
Configuration Page , Opens In New Window Lead Configuration Page , Opens In New Window
Errors Configuration Page , Opens In New Window

Introduction

In a GEM site, various configuration pages can be set up. These pages are stored under the path country/entity/site/language/configuration, e.g. RO/BCR/www.bcr.ro/ro/configuration. For some of theses configuration pages, a container page must be created where designated templates can be set up. The most common container is the /configuration page itself. Additionally, containers are necessary for Error Pages (404/500) and Modal Content Pages.

Glossary:

Configuration Page

The Configuration Page is used to create the /configuration node that serves as container node for all configuration templates. It is created as child of the language node of every site: content/sites/country/entity/site/language/configuration, e.g. ../RO/BCR/www.bcr.ro/ro/configuration.

Attention:

Be aware that the node must not be renamed or moved. When start editing a new site, it is usually already set up for the editors, ready to use.

The following templates can be set up below the /configuration node, or more precisely the Configuration Page:

Editorial hint:

Create "folder nodes" for other configuration pages

As child of a Configuration Page, all configuration templates are available to be set up. Therefore, it can also be used to create a kind of a folder for other configuration pages. This can be useful to keep the /configuration node tidy. If for example multiple Snippet Content Pages are created, a Configuration Page can be used to create such a folder or archive under which all Snippet Content Pages are created (e.g. /configuration/snippet-archive/snippet1).

Lead Configuration Page

The sole purpose of the Lead Configuration Page is to serve as a container node for Modal Content Pages. This means that every Modal Content Page (template used to create forms) can only be created as a child of a Lead Configuration Page.

Editorial hint:

Create "folder nodes" for multistep forms or a collection of Modal Pages

The Lead Configuration Page can also be used to create a kind of a folder for a collection of Modal Pages. This can be useful to keep the .../leads node tidy and it gives e.g. to multistep forms a logical structure (all steps are stored in one container). To do so, simply create a Lead Configuration Page under the Lead Configuration Page that is used as .../leads container.

Attention:

Be aware that the Name of the .../leads node must not be changed. The Title can be customized as desired.

Please see the Modal Content help page for more information.

Errors Configuration Page

The sole purpose of the Errors Configuration Page is to serve as a container node for the designated Error 404 and 500 pages. This means, that as a child of .../configuration, the .../error-pages node is set up and below that, the pages for .../404 & .../500, e.g. .../configuration/error-pages/error-404.

Please see the Error Pages - 404 / 500 help page for more information 

Related topics