Uniform Content (Headless CMS)

Every Uniform project includes a fully featured headless CMS — there is nothing extra to purchase or provision. Content teams can start creating and managing structured content immediately, while developers consume it through APIs and SDKs in any frontend framework.

Unlike standalone CMS products, Uniform's headless CMS is deeply integrated with the rest of the DXP platform. Content lives alongside compositions, personalization, A/B testing, and visual editing in a single workspace, so teams can move from content modeling to live experiences without switching tools.

Structured content modeling#

At the core of Uniform's CMS is a flexible content modeling system built on content types and entries.

Content types are the blueprints that define the structure of your content. Each content type is composed of fields — such as text inputs, date pickers, rich text editors, asset selectors, and more — that specify what information an entry should contain.

Entries are the actual pieces of content created from those blueprints. An article, a product, an event, or a FAQ item — each is an entry authored against a content type. Entries are design-agnostic: the same entry can be displayed by different components in different contexts, keeping content cleanly separated from presentation.

For content that needs repeatable, structured data within a single entry — such as product variants, feature lists, or opening hours — blocks let you define reusable sets of fields that repeat inside a parent entry without cluttering your project with separate entries.

When entries need to reference other entries, reference fields allow you to build relationships across content types, enabling complex content structures like linked categories, related articles, or author profiles.

Federated content with Uniform Mesh#

Most enterprises don't store all their content in one place. Product data lives in a PIM, images in a DAM, pricing in a commerce platform, and editorial content across one or more CMS instances.

Uniform solves this with Uniform Mesh — a no-code integration framework that connects external systems to Uniform through a single, unified layer. Rather than building and maintaining point-to-point integrations, teams connect their existing systems to Uniform Mesh and pull external data directly into entries and compositions.

Ready-to-use integrations are available for leading content, commerce, and DAM platforms, and custom integrations can be built for any other system.

Unified content model with entry patterns#

Entry patterns take federated content a step further by enabling a unified content model across your entire enterprise — regardless of how many source systems are involved.

An entry pattern defines how data from an external system maps into a Uniform content type. Because the mapping is encapsulated in the pattern, content editors don't need to know which system the data comes from — all entries look and behave the same way regardless of their origin.

This approach enables powerful scenarios:

• Compose entries from multiple sources — Combine product data from a PIM, images from a DAM, and pricing from a commerce platform into a single, unified product entry.
• Aggregate content across systems — Unify articles from multiple CMS instances into one content set backed by a single content type.
• Incrementally migrate from a legacy CMS — Create entry patterns as a facade over legacy content, then gradually migrate entries to Uniform without disrupting live experiences.
• Mix local and remote content — Some entries are authored directly in Uniform while others are sourced from external systems, all within the same content type and managed as equals.

Content authoring and management#

Uniform provides a rich set of tools for content teams to author, organize, and manage content at scale:

• Entry editor — A full-featured editing interface with side rail, nested entry editing, and contextual tools.
• Entry previews — Preview entries in the context of live compositions before publishing.
• Search, filter, and bulk operations — Find, organize, and manage entries at scale.
• Workflows — Define review and approval processes for content.
• Releases and scheduling — Coordinate cross-entry content launches with scheduled publishing.
• Localization — Manage content across multiple locales within a single entry.

Ready to dive in?#