The following terminology is used throughout the Enhanced Content documentation. These terms build upon one another and are listed in order below accordingly.
|
Term |
Definition |
|---|---|
|
Module |
A pre-formatted layout block consisting of text, images, or a combination of the two, that can be used by itself or in conjunction with other blocks to build content and create a layout in a Template for a Dynamic Record, or to be used to create a layout in a Static Record. |
|
Enhanced Content |
The overarching concept of an experience beyond basic product data management. Example: The combinations of several modules in the desired output published to a user interface, for example, Amazon. |
|
Content Editor |
The combination of one or more of the available modules. The Content Editor designs the experience delivered for those viewing the Enhanced Content on a Product Page. |
|
Dynamic Records |
Dynamic Records are created from templates. These contain the specific experience as designed for each of the associated products. |
|
Static Records |
The encapsulation of information that consists of all needed data to support enhanced content on a product for the platform it is being published to. If more than one product is associated with a Static Records, the information will all look the same; no distinctions can be made. |
|
Templates |
Templates are from which Dynamic Records are created. Templates are created so A+ content applicable to multiple products can be crafted with one content-generation action. A template contains the layout of modules, which are ordered in defined ways to create an experience. Additionally, this is where content data can be associated with content areas, to ensure a fast and efficient way of creating content at scale. |
|
Product Experience Management (PAM) |
The overall task that needs to be achieved through the offering. |