XP8 CMS - Schemas, Content and Modeling
Contents
Introduction
Enonic’s CMS stack combines the Enonic XP platform, Content Studio for authoring, and Guillotine for headless delivery. XP provides content storage and the declarative schema system. Schemas define the content models exposed through the API and Content Studio, with server-side validation, indexing and querying capabilities. Additional apps are available through Enonic Market.
Deploy custom Schemas for your content models, Extensions that augment Content Studio, and Functions for to augment the API or run custom server-side logic.
| Enonic Market offers free applications for SEO, analytics and integrations as well as subscription apps like Content Studio+ and the AI Content Operator. |
This documentation covers the CMS surface only. See also:
-
Enonic Development Kit for schema deployment, functions, extensions and more.
-
XP platform docs for core platform features and architecture
CMS stack and versions
The products in the CMS stack are released and versioned independently. The 8.x version of this documentation refers to Enonic XP. Content Studio and Guillotine have their own version numbers and compatibility requirements.
| Product | Role | Version context |
|---|---|---|
|
Enonic XP |
Content storage, schemas, indexing, and the Image and Attachment APIs. |
This reference covers XP 8. The Guillotine 9 examples require XP 8.1.0 or later. |
|
Content Studio |
The editorial interface for managing and publishing content. |
A separately installed app. The companion Developer 101 tutorial uses Content Studio 6.1. |
|
Guillotine |
The GraphQL API for headless content delivery. |
The GraphQL examples in this reference use Guillotine 9, a separately installed app. |
The Developer 101 setup lists the exact stack tested for that tutorial. Those tested versions are distinct from each product’s minimum compatibility requirements.
See GraphQL API for endpoint and request details, and Release notes for links to each product’s releases and upgrade information.
Main features
Schema as code: Flexible content modelling.
Hierarchies: Organize content in a tree structure.
Media: Store any file as content.
Image: Real-time processing and delivery.
Versioning: Version control and branching for content.
Workflows: Define custom content lifecycles and approval.
Layering: For multi-language and multi-region use-cases.
Scalable: Scale from small projects to global multi-brand deployments
Customizable: Augment the platform, APIs and tooling through custom development.
Developers may adapt the platform, APIs and tooling extensively via Enonic apps, making it a versatile choice for organizations looking to manage their digital content in a way that is optimized for their needs.
Front-end integration
Enonic CMS can be used with any front-end framework, and publishes React components and a Next.js integration (Next.xp) to handle rendering. See Front-end integration.