In Experience Manager, content folders, unlike pages, are not site-specific, meaning a content folder’s items may be shared by multiple sites. For organizational reasons, you may want to group a set of content items under the same content folder but have some of those items only trigger for particular sites or site groups. For example, you may want to organize all of your promotional banner content items in the same content folder, keeping them together and easy to locate, but one of those promotional banners would only be triggered when a particular site is the current site. For this site-specific promotional banner, you would specify the site as a trigger when you add the banner’s content item to the content folder in Experience Manager. Note that a content item can have one or more sites or site groups as a trigger.
Enabling the use of sites and site groups as triggers in Experience Manager requires some additional configuration on the part of the Workbench administrator. Specifically, to incorporate sites and site groups in content item triggers, the following happens:
An administrator or business user manually adds a set of user segments to Workbench that correspond to the sites and site groups that have been defined in Site Administration. This allows the sites and site groups to be used in the user segment triggers configured by business users.
Experience Manager business users configure triggering rules for the content items using the manually added user segments.
Every time the Core Platform calls the Assembler, it passes site context information (the current site and its site groups) for the current request and shopper.
The passed information allows the Assembler to return the correct content for the request, based on the configuration set in Experience Manager.
The following sections provide more detail on these general steps.
