Experience Pages

Info: Experience Pages are available starting with brXM 14.3.0.

Overview

Experience Pages combine both content and page layout into a single, self-contained page. This approach introduces page-driven management to Bloomreach Content.

In earlier versions, Bloomreach Content used a content-driven model. The sitemap mapped URLs to separate page configurations and content paths. Page configuration and content were stored in different repository locations and managed through separate workflows.

Experience Pages differ by storing both the page layout configuration and the content together. This design allows the entire page to move through the publication workflow as a single unit. CMS users can manage these pages independently from the channel configuration.

To use Experience Pages in your implementation, you must configure the system.

Hint: For step-by-step instructions, see the Configure Experience Pages tutorial.

Key Concepts

Experience Page Folder

An Experience Page Folder is a content folder that stores Experience Page Documents for a specific channel. Developers must configure these folders.

Experience Page Layout

An Experience Page Layout is a page layout defined and configured by a developer. It is stored in the delivery tier configuration section of the repository. Experience Page Layouts act as templates for the page configuration embedded in an Experience Page Document.

Experience Page Document

An Experience Page Document is a document that includes an embedded page configuration based on an Experience Page Layout. CMS users create Experience Page Documents and store them in the content section of the repository, inside an Experience Page Folder. Experience Page Documents support the standard document features, including the publication workflow, version management, and link integrity checking.