Bloomreach Content acceleration

Your journey with Bloomreach Content will most likely start with a clean environment. The Alokai team will populate it with data models parallel to your frontend setup.

Content types

Creating a Content Type is the first step required to work with components in Bloomreach Content. It is a scaffolding for Documents which you will be creating to populate your frontend Blocks with dynamic data (e.g. to add values for fields such as title, subtitle and description in your Banner component).

Content Types are divided into two groups: Document Types and Field Group Types. Every Block component in your frontend setup has its corresponding Document Type in Bloomreach Content. Going further, these Document Types might contain one ore more Field Group Types. For example, the Accordion Block component in your frontend setup has a parallel Accordion Document Type in Bloomreach Content which contains the Accordion Item Field Group Type.

Folders

Folders are required to organize Documents created from Content Types. In the initial Alokai setup, every Content Type has a dedicated Folder in the Documents section of the Content Application. These folders are nested within the en root folder.

Components

Components are the final building blocks in your Bloomreach Content setup. They are selectable within the Experience Manager and allow you to pick or create Documents. Every Block component in your frontend setup has its corresponding Component in Bloomreach Content.

Layouts

Layouts define the structure of your dynamic CMS pages. The iniitial Alokai setup ships with an abstract base layout extended by the dynamic page layout. First, they allow you to add static components which will be rendered once during the initial page load and persisted across all pages which use the layout (e.g Footer and MegaMenu). Second, they allow you to define containers (i.e. placeholders) for one or more managed components which can be added and configured in the Experience manager.

Menus

Menus allow you to build components which feature navigation menus (such as Footer and MegaMenu). They must be associated with a static Base Menu component instance added on the layout level. It allows editing them from within the Experience Manager. The initial Alokai setup ships with Menus for both Footer and MegaMenu.