Before a content administrator can configure dynamic content items within an application, you must create content folders to contain those items. Content items within the same folder are evaluated against each other at runtime to determine which item (or items) should be returned to populate a defined section of the current page.

In Experience Manager, content folders define the top-level organizational structure of an application, in which the content administrator can browse for content. If a query satisfies the trigger criteria for multiple content items within a folder, items with higher priority take precedence over those with lower priority. A single application request may trigger content items from multiple folders

Content folders have the following properties:

Oracle recommends that you create at least one content folder for pages and one for each slot on the page that can contain either shared or variable content. This provides a logical organization of content within Experience Manager. It enables content to be triggered independently of the pages that contain them and also enables content in one slot to be triggered independently of content in another slot.

Content folders determine which content items are evaluated and returned when populating a dynamic section of an application page.

Suppose you have a site where a typical structure for a search and navigation page looks like the following:

Based on this template, the content administrator wants to configure a page for a specific trigger (for example, Category > Cameras > Digital Cameras) using contextual, shared, and variable content as in this picture:

The configuration for the page (as specified in Experience Manager) looks like this:

The configuration for Guided Navigation (including which dimensions to display and which dimension values to boost or bury within those dimensions) and for the Results List (including default sort options and record boost and bury) are specified as part of the page configuration. The other slots on the page contain only placeholders. The actual Header, Footer, Banner, and Spotlight content items that display when someone visits the site are defined in their respective content folders.

The mechanism for populating these slots is the same regardless of whether the content that should display in each slot is shared or variable content. The only difference between the two kinds of content is in the trigger criteria on the content items within those collections: variable content, such as the Spotlight, has triggers that are more specific than the page trigger. Reusable content, such as the generic header and footer, has triggers that are more general than or orthogonal to the page trigger.

When the content administrator has created all the content needed to populate this page (and a few other pages), the application may include the following content items in the following folders:

The content folders are configured as follows:

Each page or content item within these folders has an associated trigger and priority (relative to the other items in the same folder) specified by the content administrator in Experience Manager.

When a site visitor refines on Category > Cameras > Digital Cameras and Brand > Sony, the following content triggers:

In this example, content is returned from five content folders. Priority between items is specified within each folder. It does not make sense to prioritize the Sony cameras banner against the April spotlight cartridge, for example, because they are not competing against each other to be displayed on the page. In general, content items with more specific trigger criteria should have a higher priority than those with more general criteria, especially if they are used in a dynamic slot with an evaluation limit of 1.

Oracle recommends that you create separate content folders for each area on the page, even if they have the same content type. For example, if you want to have two banners on the page, each populated via dynamic slots, they should reference two different folders, or else the same banner (the one with the highest priority for the current navigation state) is returned for both sections of the page.

Oracle also recommends that you do not mix reusable and variable content within the same folder. For example, if a slot (such as the Spotlight slot) can be populated with either reusable or variable content, create two different folders, Reusable Spotlights and Variable Spotlights. The content administrator can configure a particular page to populate the Spotlight slot from either folder as applicable. In order to populate the same slot with a mixture of reusable and variable content, the content administrator can insert two (or more) placeholders in the Spotlight slot, each referencing the corresponding folder for each type of content.

The final result for the site visitor who is looking at Sony cameras looks something like the following:

Copyright © Legal Notices