Sites and Channels Configuration

In Bloomreach Content, only mounts that reference an hst:configuration containing an hst:channel node appear in the Experience manager overview. You can configure the hst:channel node directly under the hst:configuration node or within the hst:workspace subnode of the hst:configuration.

If you configure the hst:channel directly under hst:configuration, channel settings are read-only in the Experience manager.
If you configure the hst:channel under hst:workspace, channel settings are editable in the Experience manager.

For example, if your project is named example, the following configuration results in read-only channel settings:

/hst:hst:
  /hst:configurations:
    /example:
      /hst:channel:
        /hst:channelinfo:

To make channel settings editable, configure the channel under hst:workspace:

/hst:hst:
  /hst:configurations:
    /example:
      /hst:workspace:
        /hst:channel:
          /hst:channelinfo:

Site Node Configuration

Under /hst:hst/hst:sites, define hst:site nodes. Each hst:site node connects:

The absolute content location for the mount, specified by the hst:content property.
The hst:configuration for the mount, which includes the sitemap and, optionally, the HMVC configuration.

For details on how a mount references an hst:site, see the hosts configuration documentation. A mount uses the hst:mountpoint property to point to an hst:site. The hst:site node specifies the content location with hst:content and references its configuration either:

By the hst:configurationpath property, or
By naming convention (preferred): the hst:site node name matches a node under /hst:hst/hst:configurations.

Example: Local and Production Environments

The following configuration example demonstrates a setup for a single channel with both local development and production environments:

/hst:hst:
  /hst:configurations:
    /example:
      /...:
      /hst:workspace:
        /...:
        /hst:channel:
  /hst:hosts:
    /dev-env:
      /localhost:
        /hst:root:
          hst:mountpoint: /hst:hst/hst:sites/example
    /prod-env:
      /com:
        /example:
          /www:
            /hst:root:
              hst:mountpoint: /hst:hst/hst:sites/example
  /hst:sites:
     /example:
       hst:content: /content/documents/example
/content:
  /documents:
    /example:
      /common:
      /news:
      /...:

In this configuration:

Both http://localhost and http://www.example.com resolve to the / mount (hst:root).
The hst:root mount points to /hst:hst/hst:sites/example.
The hst:site node at /hst:hst/hst:sites/example specifies that content is located under /content/documents/example.
Because the hst:site node does not define an explicit hst:configurationpath, it uses the naming convention to determine its sitemap configuration and HMVC configuration: /hst:hst/hst:configurations/example.