Plan a content model
Plan Data Types, Components, fields, keys, and safe model changes.
Use Content model to define how editors author content and how delivery clients receive it. Each Content type, Asset type, and Component owns one ordered Field Set.
Choose the owner
| Owner | Use it for | Lifecycle |
|---|---|---|
| Content type | Independently authored entries | Draft, Published, Changed, and Archived |
| Asset type | Independently managed files and metadata | Its own content lifecycle |
| Component | Reusable embedded structure | Belongs to its containing entry, asset, or Component |
Choose stable type and field keys: they shape generated delivery contracts. One suitable ShortText or Slug field can provide editor titles. Test the model with a non-production entry or asset before clients depend on it.
Access
To inspect the model, a member needs backend.read and model.read with matching Backend scope; model.read may also be limited to selected Data Types. Creating uses model.create. Updating or deleting uses model.update or model.delete with scope matching the affected owner.