Dimensions

In webCOMAND, dimensions provide a way to identify, manage and query different variations of content, known as "variants".  For example, a Language dimension can be used to identify, manage and query different language translations of content.  A content item with a Language dimension might have three variants: English, French and Spanish.  If the content has a title field, each variant would define the appropriately translated title.

Dimensions can be used to implement:

• Localization - Translations of the same content into multiple languages.
• Segmentation - Create personalized versions of content to be presented to different user segments.
• A/B Testing - Create different versions of content to be presented to different test groups of users to compare engagement and outcomes.
• Formats - Store multiple versions of content for fast retrieval based on the desired format.  For example, certain sizes, cropings and image formats of image data.  Images can also be processed on the fly, but this is useful for storing manual or pre-processed versions as well.
• Personalization - One or more dimensions can be used to manage and present content that caters to specific consumer demographics.

How Dimensions Work

webCOMAND comes with a Dimension Content Type, which has a few fields used to identify and query content variants for a specific dimension.  These include:

• Identifier - The Key used to identify a content variant in queries.
• Title - Optional name used to identify a content variant in the user interface.
• Description - Optional description of the content variant, displayed in the user interface.
• Icon - Optional image to represent the content variant in the user interface.

User Interface

Once a dimension is added to a content type, the Variants Sidebar is available in Form View.

Queries

cPath and cQL queries can retrieve content of the desired variant using the WITH Clause.

SELECT Title FROM WebPage WITH EN

Add a Dimension

Add a new dimension with the following steps.

1. Ensure dimensions are enabled for the repository.  See Dimensions Configuration.
2. Define a content type that extends the Dimension Content Type.  For example, a Language content type that extends Dimension.
3. Add content of the new Content Type to specify the Identifier and optional Title, Description and Icon for each variant.
4. Enable variants of the new dimension for desire content types by adding a new relationship field to each desired content type.for the new content type to the desired content type(s).

Localization

The most common use of dimensions is content localization.  The io_comand_localization package makes it easy to add localization with the following steps.

1. Import the io_comand_language package.
2. Update each content type that contains content you would like to localize (or a common content type they extend).
3. Update any existing queries to request the desired language.
4. Update any existing publication content types you wish to localize.

• < Collaboration
• Authorizations >