Skip to content

Content Editing ​

The Content Panel is the right-side panel in the project workspace. It provides structured views for browsing and editing content entries, with specialized interfaces for each model kind.

Content Panel Navigation ​

The content panel has several view modes:

ViewTriggerPurpose
OverviewClick project name in sidebarShows all models with entry counts
CollectionClick a collection modelLists entries as expandable rows with search, filters and sorting
SingletonClick a singleton modelShows the single entry's fields, with an Edit content button
DocumentClick a document modelShows documents with Markdown preview
DictionaryClick a dictionary modelShows the key-value editor
VocabularyClick Vocabulary in sidebarShows project-wide vocabulary terms
BranchClick a branch in sidebarShows the review panel for that pending change

What You See Depends on Your Role ​

Write controls are shown only to roles that may use them, so a control you can see is one the server will accept:

RoleWhat the content panel offers
Viewer, ReviewerRead-only. No edit, delete, add or status controls. Reviewers approve, reject and request changes from the review panel
EditorEdit entries, dictionary keys and vocabulary terms, add entries
Admin, OwnerEverything an editor can do, plus the status picker, Add model, Delete model, the Title field setting, and editing the Form and Comments settings

A member limited to specific models can edit only those models. See Team Management for roles.

Browsing Entries ​

Collection View ​

When you select a collection model, the content panel shows a list of all entries. Each entry displays field values in a compact row format.

Collection view: a model's entries listed with status badges in the content panel

Features:

  • Search: Finds entries across the whole model, not only the rows already on screen
  • Filter and sort: The Filter button offers filters derived from the model (including status), with Clear filters. Sort by title (A-Z or Z-A), recently updated, or any sortable field
  • Locale switcher: Switch between locales for i18n-enabled models
  • Counts: The footer shows how many entries are visible out of how many match; Show more loads the next page
  • Expand a row: Click an entry to see all its fields and when it was last updated
  • Edit entry: The pencil icon on a row opens the editor modal
  • Delete entry: The trash icon sends the delete request to the AI chat, and the agent performs it

Singleton View ​

Singleton models display their single entry directly in the panel. Fields are shown read-only; click Edit content to open the editor modal with all fields.

Document View ​

Document models show entries with their Markdown content. Each document is identified by its slug and displays a preview of the body content. As in the collection view, the pencil icon opens the editor modal and the trash icon sends the delete request to the AI chat.

Dictionary View ​

Dictionary models show a flat list of key-value pairs for the selected locale. Use the filter box to find keys or values.

ActionHow it works
Edit a valueThe Edit value icon on a row opens the editor modal for that key. Edit content in the toolbar opens every key in the filtered list together (there is a cap on how many; narrow the filter first if the list is long)
Add a keyType a key and a value in the row at the bottom and click Add key. A key that already exists is refused ("Edit its value instead")
Rename a keyThe Rename key icon turns the key into an input. The key is renamed in every locale that holds it, in one commit, and the rename is refused if the new key already exists in any locale. A site that still reads the old key loses that text until its code uses the new one
Delete a keyThe Delete key icon opens a confirmation where you type the key to confirm. The key is removed from every locale that holds it

On a project with several locales, the default locale is the reference: while you edit another locale, the modal shows the default-locale value under each input, and a Missing in {locale} filter lists keys the default locale has and the current one lacks. If an edit drops a {placeholder} that the old value or the default-locale value contained, the modal warns you; the value still saves.

Rename and delete are held for review on review projects, like any delete: the change waits on its branch under Pending Changes until it is approved. In the review panel, a removed key that reappears under a new name is labeled "possibly renamed from".

The Editor Modal ​

The editor modal provides a full-featured editing experience for individual entries. It opens when you click an entry in any content view.

The editor modal for a blog post — a relation field (author), a relations field (categories), an image field that takes a media path or URL (cover_image), and a text field (excerpt), with a Save changes button

The modal edits all of an entry's fields at once. Click Save changes to save everything you changed in one commit. A field in a model with several locales that is shared across locales (for example a media or relation field) is saved to every locale, and the toast tells you which.

Creating New Entries ​

For collection and document models, the Add entry button in the content panel header sends a request to the AI chat, and the agent creates the entry with default values. You can also describe the entry yourself in the chat.

For singletons, the entry always exists — you edit the existing one.

Field Editing ​

Each field type has a specialized editor:

  • String/Text: Input field or textarea
  • Markdown/Richtext: Editor with formatting toolbar and live preview
  • Image/Video/File: A text input for a media path (media/original/...) or an external URL. Copy the path of an asset from the Media Library
  • Date/Datetime: Date and date-time inputs
  • Boolean: Toggle switch
  • Select: Dropdown with predefined options
  • Relation: Entry picker showing entries from the target model
  • Array: Repeatable item list with add/remove controls
  • Object: Nested field group
  • Color: Color picker with hex input

Saving Changes ​

When you save content, Studio:

  1. Validates the data against the model schema
  2. Creates a cr/* feature branch and commits the change to it
  3. On an auto-merge project, merges it into the contentrain branch and advances main, then shows "Saved to branch: ..."
  4. On a project with the review workflow, holds the branch when the approval policy asks for review, and shows "Saved to branch ... it needs review before it goes live". The branch appears under Pending Changes

TIP

Every content save creates a Git commit. You can always see exactly what changed in the review panel or in your Git history.

Content Status Workflow ​

Content entries in collections support a status workflow:

Content entries with status badges (draft, published) and the publish/unpublish toggle on row hover

StatusDescription
draftEntry is being worked on, not ready for publication
publishedEntry is live and visible to consumers
archivedEntry is retired and not served

Changing Status ​

You can change an entry's status through:

  • The status badge on a collection row, a document, or a dictionary: click it and pick Draft, Published or Archived. The badge is a menu only for owners and admins; other roles see a plain badge
  • The AI chat ("Set the blog post 'Hello World' to published")

A published entry can also carry a schedule. The badge then reads scheduled (not live yet) or expired (no longer served); hover it for the date. See Scheduled Publishing.

WARNING

A status change is a Git commit like any other. On a review project, moving an entry to published or archived is treated as a higher-risk change and is held for approval under the default policy. The CDN only serves entries with published status.

Multi-Locale Editing ​

For models with i18n: true, the content panel includes a locale switcher:

  1. Select a model in the sidebar
  2. Use the locale dropdown to switch between available locales
  3. Edit content in the selected locale
  4. Each locale has its own content file in the repository

Copying Content Between Locales ​

To bootstrap a translation, you can ask the AI agent:

"Copy the English blog posts content to Turkish"

The agent uses the copy_locale tool to copy all entries from one locale to another without overwriting existing translations.

Vocabulary Editor ​

The vocabulary is a project-wide set of terms shared across all locales. Access it from the sidebar under Vocabulary.

The Vocabulary editor: shared term keys mapped to translations, with an add-term row

Features:

  • Add terms: Type a key and a translation for the selected locale and click the plus button. Switch the locale and add the same key again to add that language's translation
  • Bulk add: Click Bulk add and paste one term per line, a key then a tab or space then the translation. All terms are saved into the selected locale in one change
  • Delete terms: Remove terms that are no longer needed

The term list shows the translation for the selected locale; the locale codes under a term show which languages have a value.

Vocabulary terms are stored in .contentrain/vocabulary.json and are separate from dictionary models.

On a review project, a vocabulary edit is held for review like any other content change. The panel tells you the edit is waiting on its branch, the branch is listed under Pending Changes, and the review panel shows each added, updated or removed term under Project settings.

Content Panel Context ​

Items in the content panel can be pinned to the chat context. This helps the AI agent understand what you are working on:

  1. Hover over a model, entry, or field in the content panel
  2. Click the pin icon to add it to the context bar
  3. The pinned item appears as a chip above the chat input
  4. Send a message — the agent sees the pinned context

You can also drag and drop items from the content panel to the chat context bar.

See AI Chat for more details on the context system.

Editing via AI Chat ​

All content operations can be performed through the AI chat instead of the UI:

"Create a new blog post titled 'Welcome' with author 'a1b2c3d4e5f6'"
"Update the site settings tagline to 'Build faster with AI'"
"Delete the FAQ entry with ID 'x9y8z7w6v5u4'"
"Add a new key 'nav.blog' with value 'Blog' to the UI Strings dictionary"

The agent handles schema validation, branch creation, and Git commits automatically.

Next Steps ​

Released under the AGPL-3.0 License. Privacy