Manage Site-Specific Data - BloomReach Experience - Open Source CMS

Manage Site-Specific Data

As of version 13, repository data specific to a site web application (such as the site's HST configuration and web files) is defined and packaged in the site web application. This includes both config and content definitions.

For the Configuration Management mechanism to detect and process these definitions, the site web application must declare itself to be an "HCM Site". It does so by including the hcm-site.yaml file in the site web application, as described for projects in Multi Site Mode. When Configuration Management detects such site web applications, it scans it for HCM modules, and processes them after having processed the repository data definitions of the CMS/platform web application.

In terms of the repository structure, the data pertaining to a specific web application must be easily distinguishable from the data pertaining to the CMS/platform or the data of other site web applications. Therefore, each site web application has its own HST configuration root node/tree, and its own web file bundle name.

If your project runs in Single Site Mode, all repository data definitions must be packaged in the CMS/platform web application, and the hcm-site.yaml file must not be used.
Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?