Content Designer

Administrators use Content Designer to define content structures. Editors use those structures in Content Manager.

Create the example collection

1. Select New content type.
2. In Details, enter Name Articles, check the ID articles, and select Collection.
3. Choose whether to Require editorial approval.
4. In Fields, select Add field and add:

Label	Field type	Suggested settings
Title	Short text	Required, Localized, Show in list
Body	Rich text	Required, Localized
Hero image	Image	Optional

5. Set Title field to Title, then save.
6. Configure content access and open Articles in Content Manager.

Use Single type instead of Collection for one item, such as a home page. IDs and field keys are integration identifiers; choose them deliberately. Supported keys contain up to 42 lowercase letters, digits, or underscores and start with a letter.

Field configuration

Required controls completeness checks. Localized allows language-specific values. Sortable, Show in list, and alignment affect the editorial listing. Field-specific controls configure choices, relation targets, media selections, or Master Lookup sources.

Only short text, long text, and slug fields can be the Title field. It provides entry titles and enables title search. Clear or replace it before removing or converting that field.

Use Master Lookup for reusable option sets, and CSS Templates for supported content-preview styling.

Workflow policy

Explicitly choose editorial approval for your team. New types default to strict approval when the installation has six or more accounts, and permissive workflow with fewer accounts. Existing types retain their policy until changed.

Policy changes require confirmation and can reset pending unpublished content to draft. Coordinate them with reviewers and scheduled releases. See workflow.

Change an existing structure

Use Edit type. Review destructive-change warnings when removing fields or changing their types. The confirmation can require exact field keys. Take a full deployment backup before destructive design changes; schema exports and generated content-rebuild exports do not replace it.

Export schema and Export selected export content definitions for inspection or reuse. They are not full database/media backups.