Editorial

To fill in an entry's fields, choose Editorial → Structured Editor in the sidebar and pick the entry from the menu at the top, which lists each entry with its type. The editor shows the fields of the entry's content type, with a * after required ones, and then the entry's Body, built from paragraph and heading blocks.

Choose Save when you're done. Content checks every value against its field's rules first. If any fail, it shows how many fields need attention and puts the message under each field, and nothing is saved. Otherwise it saves the fields and the body together, takes a new version and confirms with "saved as version" and the version number.

The figures across the top count the type's Fields, how many are Filled, and the Issues found on the last save. If no content type matches the entry's type, the editor shows "No schema for type" and the type name: create a matching type in Content architecture.

Saving needs the Edit an entry or page permission, and saving an entry that's Published or Scheduled also needs Publish an entry or page.

An entry goes through review by its status. A writer sets the entry to In review in its Visibility tab, and someone with the Publish an entry or page permission approves it in the Review Queue, which publishes it, or rejects it back to Draft.

A version is a saved copy of an entry's title, slug, body and other details at one moment. Content takes a version each time you save in the Structured Editor, each time you publish from the Publishing Queue, and when it publishes a Scheduled entry on its date. Versions taken at publish time are marked published. Version History shows them, and Compare and Rollback compares two of them and can restore the older one.

Changing an entry anywhere else, such as in the entry editor or with Bulk Editing, doesn't take a version.

The Structured Editor gives each field an input that matches its data type:

• Text: a one-line box.
• Number: a number box.
• Boolean: a menu of True and False.
• Date: a date picker.
• Enum: a menu of the field's options.
• Media: a menu of the project's assets.
• Reference: a box for the linked entry's id or slug.
• Rich text and JSON: a larger text box. A JSON field keeps its last valid value while you type, and shows "Not valid JSON yet; the last valid value is kept." until the text is valid.

Localized fields say "Localized · varies per locale." under the input. Switching to another entry in the menu at the top discards changes you haven't saved.

Editorial → Visual Editor shows a published entry the way readers see it: the cover image, the excerpt, the body and the author. Pick the entry from the menu at the top, which lists published entries only, and pick a width with the three device buttons: Desktop (full width), Tablet (768 pixels) or Mobile (390 pixels).

The preview doesn't change anything. To edit what it shows, open the entry from Content → All Content. If nothing is published yet, the screen shows "Nothing published yet".

To start a discussion about an entry, choose Editorial → Comments & Mentions, then New thread. Pick the Entry, optionally name the field it's about in Field key, write the Comment and choose Start thread. The entry and the comment are required.

Threads are listed with the most recent activity first. Each one shows its entry, its field key, whether it's Open or Resolved, and every reply with its date and time. Reply opens a box under the thread: type the reply, then press Enter or choose Post. Resolve closes the thread, and Reopen opens it again.

Switch between All, Open and Resolved threads, and search entry titles, field keys and comment text. The figures across the top count Threads, Open threads and Replies. Comments can't be edited or deleted. Posting needs the Edit an entry or page permission.

An assignment names who owns an entry through review, and by when. To create one, choose Editorial → Assignments, then New assignment:

• Entry and Assignee are required. The assignee is free text, such as a name or an email address.
• Due date is optional.
• Status: Open (the default), In progress or Done.
• Priority: Low, Normal (the default), High or Urgent.

Choose Create assignment. Each row shows the entry, the assignee and the due date, which turns red once it has passed on an assignment that isn't Done. The figures across the top count Assignments, Open ones (anything not Done), Overdue ones and High priority ones (open and High or Urgent).

Filter by status, and search assignees and entry titles. Each row's ⋯ menu has Edit, Mark done and Delete, which removes the assignment straight away, without asking. Assignments need the Edit an entry or page permission.

Editorial → Review Queue lists every entry that's In review, most recently updated first. Each row shows the entry's slug, type, author and last update, with two buttons:

• Approve publishes the entry straight away. It needs the Publish an entry or page permission, which the Owner, Admin and Editor roles have.
• Reject sends the entry back to Draft.

Neither asks you to confirm first. The figures across the top show how many entries are Awaiting review, the Oldest wait (the last update date of the longest-waiting entry) and how many Types are in the queue. Filter by type, and search titles, slugs and authors. When nothing is waiting, the queue shows "Queue is clear".

Editorial → Approval Workflows records the steps of your team's review process, such as Legal review, in order. To add a step, choose New state. Only the Label is required, and the Key fills in from it. Position sets its place in the order, and new states go last. Terminal is No to start (the flow continues); pick Yes for a state that ends the flow. Choose Create state.

The Flow card shows the states in position order. In the list, each state is a Gate or Terminal, and its ⋯ menu has Edit and Delete, which removes it straight away, without asking.

Workflow states describe your process; they don't change entries. An entry's status stays one of Draft, In review, Scheduled, Published or Archived, set in its Visibility tab or by the Review Queue. Changing states needs the Edit an entry or page permission.

Editorial → Version History lists an entry's versions, newest first. Pick the entry from the menu at the top. Each row shows the version number, a published tag if it was taken at publish time, when it was taken, and its title and number of fields. Click a version to see everything it saved.

The figures across the top show the number of Versions, the Latest one and how many are Published snapshots. Version History only reads; to restore a version, use Editorial → Compare & Rollback.

To compare two versions of an entry, choose Editorial → Compare & Rollback and pick the entry from the menu at the top. Content starts with the second-newest version on the left, as the baseline, and the newest on the right; change either one with the version menus. The table lists every difference with its path, whether it was Added, Removed or Changed, and the value in each version. An entry needs at least two versions to compare.

To restore the baseline, choose the restore button at the top, which names the baseline version (like Restore v3), then Restore in the dialog. It overwrites the entry's title, slug, excerpt, body and field values with the baseline's, and the entry's current state isn't saved as a version first. Restoring needs the Edit an entry or page permission, and Publish an entry or page too when the entry is Published or Scheduled.

Editorial → Bulk Editing sets the status or type of many entries in one go:

1. Select entries with the checkbox on each row, or click the row. Select all in view selects every entry that matches the filters and search.
2. Under Batch action, pick a new status, a new type, or both. Keep status and Keep type leave that part as it is.
3. Choose Apply, which shows how many entries are selected.

Selections are kept when you change the filters, and Clear empties them. If some updates fail, Content says how many and reloads the list. Setting entries to Published or Scheduled, or changing entries that already are, needs the Publish an entry or page permission.

The AI Assistant writes editorial suggestions, such as a summary, a clearer introduction or a better title. To ask, choose Editorial → AI Assistant, optionally pick an entry in Entry context (the menu lists the 100 most recently updated entries), type up to 4,000 characters in Request and choose Ask assistant. With an entry picked, the assistant reads its title, excerpt and body.

Suggestions don't change or publish anything. Your requests and responses are saved and private to you, and the table shows your last 20. Each person can ask up to five times a minute in a project; after that, Content says "Wait a minute before asking again." Asking needs the Edit an entry or page permission.

If the screen shows "Generation provider unavailable", the assistant hasn't been set up on the server, and only your saved history is available.