Experience Pages

Introduction

Experience Pages are self-contained pages combining content and page layout, adding the option of a page-driven approach to Bloomreach Experience Manager.

Traditionally, pages in Bloomreach Experience Manager have been content-driven. The sitemap links a URL to a page configuration and a content path, the combination of which can then be rendered as a webpage. The page configuration and the content are strictly separated: they are stored in different locations in the repository and follow separate workflows.

In contrast, Experience Pages store both the page layout configuration and the content in the same place, enabling them to flow through the publication worklfow as a single, self-contained unit. This allows CMS users the flexibility of managing pages independently from the channel configuration.

To enable the use of Experience Pages in a Bloomreach Experience Manager implementation project, someconfiguration by developers is required.

Concepts

Experience Page Folder

AnExperience Page Folder is a content folder in whichExperience Page Documents for one particular channel are stored. It must be configured by a developer.

Experience Page Layout

AnExperience Page Layout is a page layoutconfigured by a developer and stored within the delivery tier configuration section of the repository.Experience Page Layouts are templates for the page configuration embedded in an Experience Page Document.

Experience Page Document

AnExperience Page Document is a document which contains an embedded page configuration that is an instance of anExperience Page Layout.Experience Page Documents are created by CMS users and stored within the content section of the repository inside anExperience Page Folder. AnExperience Page Document has all the features of a regular document including publication workflow,version management, and link integrity checking.