Overview
The Content module is where you model, author, and publish every kind of content in CXF. You define the shape of a content family once with a Content Template, then create Content Instances from it — each one authored as one or more Content Versions across languages and environments, with draft and published states. Files live in the DAM, and Publishing Windows control when versions go live. For how Content fits the rest of the platform, see Core concepts. The module is built around a few connected ideas.Templates and instances
A Content Template is the blueprint for a family of content — it fixes the family’s type, the custom attributes its records carry, and how they behave. A Content Instance is a concrete record created from a template, inheriting its type and attribute schema. Templates come in five types, so the same content engine powers very different objects:| Type | What it’s for |
|---|---|
| Stories | Editorial content — articles, posts, pages. |
| Products | Sellable goods and services that power Commerce. |
| Locations | Physical or virtual places — also used as inventory locations in Commerce. |
| Blocks | Reusable content fragments composed into other content. |
| Taxonomies | Categorization trees, scoped to an object type (see Taxonomies). |
Products and Locations in Commerce are content
instances — a sellable product or a warehouse is just a content instance of the
matching template. Content is the foundation the other modules build on.
Versions: language, environment, status
Content isn’t a single flat record. Each instance is authored as Content Versions, where a version is one rendition identified by language × environment × status (draft or
published). That’s how the same instance can hold an English and a Spanish
version, a production and a development environment, and an in-progress draft alongside what’s
live — all at once. An instance’s content fields (its attribute values) live on
its versions.
Assets
The DAM (Digital Asset Management) is the library where files live — images, video, documents, and external links — organized in folders, with responsive variations and alternative sources. Content references assets through its media attributes.Scheduling
Instead of publishing by hand, you can schedule a version to go live and come down automatically. A Publishing Window is a named, reusable time range you point a version’s schedule at — it publishes at the window’s start and unpublishes at its end.In this module
Content Templates
The blueprint that defines a content family’s type, attributes, and behaviour.
Content Instances
The records created from a template — stories, products, locations, and more.
Content Versions
Language × environment × status renditions, with draft and published states.
DAM
The asset library — files, folders, variations, and links.
Publishing Windows
Reusable time ranges that schedule when content goes live.