How your app and CMS work together
From the first draft to everyday publishing.
Three steps, illustrated with actual product views and fictional example data.
Your idea becomes an application.
Describe what you want to build and choose a design direction. Develop the app with AI and connect it to your content types.
The result is an app you can keep developing. CMS bindings connect its content.
Try the editorial workflow →
App Builder
Describe your application, choose a design direction and develop the result further with AI.
- Three visual directions or your own brief
- Bind a generic content card with two layouts to your content types
- Preview, visual edits and follow-up AI edits
Content Studio
Manage structured content with languages, references and a clear draft/publish workflow.
- Status and publishing per language, fallback language visible
- Autosave with revision conflict detection; discard draft changes
- Comments, scheduled publish/unpublish and releases
Media
Manage images and files centrally and deliver matching variants through the CDN.
- Image focal point for crop-safe previews
- CDN image variants by width, height, quality and format
- Image, file and multi-asset fields in content types
APIs
Deliver content to existing frontends, with separate keys per environment.
- REST delivery, preview and management
- GraphQL per environment, with schema introspection
- Separate keys per access type
Team & governance
Control who can do what in your space, and keep a record of what changed.
- Roles, with custom roles from the Team plan up
- Invitations for organization and space
- Audit log for changes
Import
Bring in an existing Contentful space through a guided assistant, instead of rebuilding content by hand.
- Carry over content types, entries and assets
- Contentful spaces in the global and EU regions
Visual editing requires CMS bindings. The reference editor supports one direct reference level. Data models are configured in the CMS first.