Creating & Editing Content
This guide walks you through the Entry Form—the place where editors add or update records inside a collection.
Opening the Form
- Click Create New on the Content List.
- OR click an existing row to open it in edit mode.
- For single record collections you are taken directly to this form when selecting the collection.
Form Anatomy
| Section | Details |
|---|---|
| Title bar | Shows collection name, locale, and status badge. |
| Locale Switcher | Appears when your project has multiple locales. Switching reloads the entry in that language. |
| Status Menu | Draft / Published toggle, Duplicate, Move to Trash, Delete Permanently. |
| Save Button | Split-button offering Save & Stay, Save & Close, Save & New. |
Working with Fields
The Entry Form renders every field defined in the collection.
| Field type | Editor widget |
|---|---|
| Text / Long Text | Input / Textarea. Repeatable fields add Add Line & Trash buttons. |
| Rich Text | Lexical editor with headings, lists, links, media embed. |
| Slug | Auto-generates from a source field; can be read-only if you tick Readonly. |
| E-mail / Number / Color | Native validation (HTML5/email, numeric, colour picker). |
| Enumeration | Single or multi-select. |
| Boolean | Toggle switch. |
| Date / Time | Beautiful date-picker with optional time picker or range mode. |
| Media | Opens Asset Library modal; shows thumbnails of selected files. Single or multiple based on field options. |
| Relation | Picker modal; choose entries from another collection with search & filter. |
| JSON | Raw JSON textarea with validation. |
Repeatable fields
When Repeatable Field is on, values are stored as an array of objects with a value key. UI shows ➕ Add Line and ⨉ delete controls.
Validation & Error Handling
Validation runs client-side (basic checks) and server-side.
If a rule fails:
- Error message appears below the offending field
- Toast shows “Failed to save content. Please check the form for errors.”.
Saving Entries
| Action | Result |
|---|---|
| Save & Stay | Saves, keeps editor open. |
| Save & Close | Saves then returns to Content List. |
| Save & New | Saves then resets form for a new entry. |
Status is set simultaneously—choose Draft or Published in the split button.
Entry Status & Lifecycle
- Draft – private; only visible to authorised users.
- Published – live in API responses.
- Trashed – moved to Trash; hidden from normal list, can be restored.
- Deleted Permanently – removed from DB, can’t be undone.
Unpublishing an entry sets status back to Draft.
Duplicating Entries
When editing, choose Duplicate in the status menu. A copy is created with:
- Same field values
- Status = Draft
Trash & Deletion
- Move to Trash – soft delete; entry can be restored from the content list with filtering status to Trashed.
- Delete Permanently – bypasses trash; asks for confirmation.
Locale Management
If your project has multiple locales:
- Use the Locale dropdown in the toolbar to switch language.
- Entries are stored per locale.
Translations
When your project has multiple locales, you can link entries as translations of each other:
- Open the Translations Panel: Click the Translations button (located under the Locale selector in edit mode)
- Link a Translation:
- For locales without translations, click Select to choose an existing entry
- The selected entry will be linked as a translation
- Navigate to Translations: Click the entry number link (e.g., "Entry #123") to open the linked translation
- Unlink Translations: Click Unlink to remove the translation connection
Linked translations share a translation group, allowing you to:
- Build language switchers in your frontend
- Maintain content relationships across languages
- Use the API to fetch translations (see API Translations)
Translations are independent entries, each has its own content, status, and can be edited separately. Linking them only creates a relationship for navigation and API queries.