Sitemap Configuration

After a request is matched to a mount, Bloomreach Content matches the remaining request path against the sitemap. The sitemap defines the URL structure for a site and consists of a hierarchical tree of hst:sitemapitem nodes. For example:

/hst:sitemap:
  jcr:primaryType: hst:sitemap
  /root:
    jcr:primaryType: hst:sitemapitem
    hst:componentconfigurationid: hst:pages/home
    hst:relativecontentpath: common/home
    /about:
      jcr:primaryType: hst:sitemapitem
      hst:componentconfigurationid: hst:pages/textpage
      hst:relativecontentpath: common/about

A matched sitemap item typically includes the hst:componentconfigurationid property. This property references the HMVC root, which is usually a child node under hst:pages. For more information, see Pages, Components, Abstractpages and Templates.

A sitemap item can also define an optional hst:relativecontentpath property. This property specifies the path relative to the root content node configured by hst:site. For details on how sitemap items are matched, refer to SiteMapItem Matching.

Note:
For default site pipeline processing, which follows the HMVC model, the matched sitemap item must include a hst:componentconfigurationid. If the sitemap item specifies non-default processing using the hst:namedpipeline property, it usually does not include a hst:componentconfigurationid.

A sitemap item can reference multiple component configuration IDs. For details, see Multiple Component configs per SitemapItem.