Content Chunk Component

When adding this component to a shape or piece, you can specify the following:

• Name (required) - A name for the component.
• Identifier - String that will be generated based on the component name when shape/piece is created or updated. You’ll use the identifier to reference the component programmatically.
• Repeatable - Specify whether or not the chunk can be repeated during content creation. You might set up repeatable content for things like recipes or quizzes.
• Localized Structure - This toggle will be enabled if you set the chunk to be repeatable. If set to Yes, the number of chunks and their contents may vary for all languages configured within your tenant, and all components within the chunk will automatically have their localization properties set to Yes as well. If set to No, then the number of chunks and their content will be shared across languages, and different localization properties can be assigned individually to each nested component.
• Component(s)/Piece(s) - At least one component or piece must be added to the chunk. You can click and drag to reorder components/pieces, or use the action button (...) to delete them.

Based on your configurations, the chunk will be labeled with either “Unified Structure” (same number of chunks/content across languages) or “Localized structure” (the number of chunks/content may differ across languages).

Below is an example of a repeatable content chunk for recipe ingredients. The chunk allows each ingredient to be defined with a quantity (numeric), a link to the ingredient product page, and a link to a substitute/alternate ingredient (item relations).

When editing content for an item, you can add, reorder, and remove chunks as needed. Use the action button (...) in the top-right corner of any chunk to access the following options:

• Collapse all chunks
• Add chunk above
• Add chunk below
• Reorder chunks
• Remove chunk

Chunks come with a powerful nesting capability. You can add them to pieces to create sophisticated multi-level structures. Currently, four levels of nesting are supported. The diagram below shows the different combinations that are possible between pieces and structural components.

The components on the fourth level of nesting may only contain non-structural components. A non-structural component is any component that isn't a chunk or choice, such as single line or rich text. A full list of non-structural components can be found here.

The screenshots below show some examples of nested structures for product properties (food, in this case) and flexible marketing content.

Once created, chunks and their content are accessible via the Catalogue API. Refer to our sample query for retrieving chunk component content, and to the API docs at https://api.crystallize.com/your-tenant-identifier/catalogue for more information.