Key Concepts
Content Structure
Define expected content structure through a layout component and specify which components can be used via an allow list.
Status Management
Support draft and published status with iterative development and version history.
Version Control
Independent versioning from packages with complete version history and rollback support.
Package Binding
Reference specific package versions to ensure component stability across content.
The ContentType Object
Example ContentType
Component Allow List
ThecomponentIdsAllowList field supports two formats:
Simple Component IDs
Grouped Components
Group related components with optional display names:Group IDs must be unique within the content type. Component IDs can appear in multiple groups. Both formats can be mixed in the same array.
Schema Generation
ContentTypes automatically generate a comprehensive JSON Schema that:- Includes complete component definitions using the
oneOfpattern - Provides full property schemas for each allowed component
- Enables LLM understanding with complete structural information
- Fetches the layout component schema
- Fetches schemas for all allowed components
- Generates a
oneOfarray for component options - Uses the schema to validate content on creation and update
Description Best Practices
The description field follows a structured markdown format optimized for semantic search:Aim for 400-600 characters.