Get Started: Content Modelling
Document Type Changes
Document types are defined in the Document Type Editor. Users with Site Developer privileges can access the document type editor in the Content app: select Document types from the Documents drop-down.
In the document type editor, you can create new document types, adjust existing ones, or manage “compound types”, i.e. composite structures of fields for grouping and reuse in multiple document types.
When working with the document type editor, be careful about existing content. Changing the content type definitions will affect the output of the Delivery API, which is consumed by the front-end. Existing document fields could go missing, and the front-end may no longer be able to render a proper experience.
To ensure that document type changes can be tested before applying them to live site content, they must be associated with a developer project (in the Projects app) and go through the project review lifecycle. Only a single active developer project can include document type changes at one time, to avoid conflicting changes.
To enable document type changes within a development project, check the Includes document type changes checkbox when creating a new project or in the Project info tab of an existing development project:
Document type changes can be tested by creating new documents based on the affected document types in the context of the developer project. The content editor and site preview will adjust based on the document type model that is appropriate for the selected project.
Note that currently, once a new document type is merged to the live site configuration as part of a developer project, it can no longer be deleted.