Delivery Framework Concepts

Bloomreach Experience Manager's delivery framework (HST) uses a number of concepts to enable flexible multi-channel delivery of content.

Delivery Configuration

A delivery configuration is a collection of configuration items required to deliver a site. Configuration items include but are not limited to: sitemap, page models, components, etc.

Site

A site binds a delivery configuration to a content root in the repository. Different sites can use the same delivery configuration with different content roots, for example in case of translated sites.

Channel

A channel is a site that can be managed through the Experience manager.

Page Model

A page model is a configuration of components into a hierarchy.

Component

A component is a single unit in the hierarchy that makes up a page model. It typically has a single purpose such as retrieving one or more content items, executing a search query, or delegating to child components in the page hierarchy. Optionally, a component can have a rendering template for Java-based server-side rendering.

Catalog

The catalog contains components that can be added to a container by CMS user in the Experience manager.

Container

A container is a placeholder in a page model for one or more catalog component instances added and configured by CMS users in the Experience manager.

Container Item

A container item is a term used for a catalog component instance living inside a container.

Template

A template is used for Java-based server-side rendering of a component, typically using Freemarker. Not required when using the Delivery API.

Sitemap

The sitemap defines a site's URL space as a hierarchy of sitemap items.

Sitemap Item

A sitemap item binds a URL or URL range to a page model and, optionally, to a content path relative to the content root defined for the site.

Site Menu

A site menu is a hierarchical navigation structure, binding menu items to URLs defined in the sitemap.