Mapping Web Content Templates to Fragments
By default, you can map web content structure fields holding a single value (such as date, numeric, image, number, or text) to fragments. For multi-value fields (such as select from list, radio button, or HTML) you must first render the field using a web content template; then you can map the template to a fragment.
For example, the Web Content with Audience structure on this image contains a Content field of Text type and an audience field of Select from List type:
You can map the single-value content field directly to a fragment, but you need a web content template to map the multi-value audience field. The web content template should use the same structure as the web content article containing the field you want to map. The following image shows this relationship:
If you want to map several structure field values to individual fragments, you must create a separate web content template that renders just one field for each field that uses that structure. If you render all your fields in one template, all their values map to the fragment when you select the template.
Mapping a Web Content Template to a Fragment
-
Create a web content structure that contains the multi-value field you want to map.
-
Create a web content template that uses the same structure with the multi-value field (A).
-
In the web content template, under fields (B), select the variable (C) with the multi-value field in the structure.
-
Create the web content based on the previous web content template.
-
On the fragment-supported page (content page, display page template, etc.) add the fragment.
-
On the sidebar panel, click Selection (
) and choose the element in the fragment you want to map. -
Under the Mapping section, select and map the web content article that contains the value you want to map.
-
Click the Field drop-down menu and select the web content template you created before.
-
Click Publish to save the changes.
A web content article is reindexed when it is edited and saved, but content pages are reindexed only when published (to conserve resources). Therefore, when a web content article mapped to a cached fragment is updated, the update doesn’t appear on the content page until you publish the page again or unmark the fragment as cacheable.