Entry editor

The entry editor is where you author and manage your entries. This interface provides all the tools you need to create rich, structured content and manage relationships between entries.

Editor interface overview#

Entry editor interface showing the main components and layout

The entry editor interface is organized into several key areas, each serving specific functions for content creation and management:

Editor header#

The editor header contains essential entry information, navigation, and controls for previewing, saving, and publishing your entry:

• Back button: Returns you to the entries list view.

• Entry name: Displays the entry's name as it appears throughout the Uniform UI. This name is automatically derived from the field marked as "display name" in the content type definition. The entry name cannot be edited directly.

• Entry slug: Shows the entry's URL-friendly identifier. The slug is automatically generated from the entry name when first created, but you can customize it. After saving, the slug remains fixed unless manually updated.

• Locale and edition selector: A combined menu showing the current locale and edition. The menu displays available locales on the left side and editions on the right side. If you're using editions, locales enabled on other editions appear in submenus, allowing you to switch to a specific edition and locale in one step. If only one edition exists (the default), the editions section is hidden to reduce clutter.

• Publish status & workflow state: Shows the current publish status of the entry. If the content type has a workflow assigned, the current workflow state of the entry will be shown in a popover.

• Preview button: Opens a preview of your entry in a nested composition editor, allowing you to visualize how your content will appear when rendered in a composition.

• Save dropdown: Provides options to manage your entry's state:

  • Save: Clicking the button saves the changes to the current entry as a draft without publishing.
  • Workflow transitions: When workflows are enabled for the entry's content type, additional options appear to move the entry through different workflow stages.
  • Publish: Makes the entry available for use in compositions and APIs.
  • Unpublish: Removes the entry from public availability.

• Entry menu: Click the button to access the entry management menu, where you can access the entry's definition (content type or entry pattern), duplicate, or delete the entry. Delete moves the entry to Trash.

Side rail#

The side rail provides quick access to entry-related tools and information without leaving the editor. Located on the left side of the interface, it offers detailed views of your entry's structure, resources, and metadata that can be accessed in panels when you click on the corresponding icon.

The side rail contains five elements:

Element	Icon
Structure	The structure icon in the side rail
Data resources	The data resources icon in the side rail
Source	The source icon in the side rail
History	The history icon in the side rail
Locales	The locales icon in the side rail
Releases	The releases icon in the side rail
Properties	The properties icon in the side rail

Structure#

The Structure panel provides a hierarchical view of your entry's content organization. It displays:

• Field groups: Expandable sections that contain related fields
• Individual fields: Specific content elements within each group
• Navigation: Click any item to jump directly to that section in the fields panel
• Content outline: Visual representation of your entry's architecture

This panel is particularly useful for large, complex entries where you need to quickly navigate between different sections.

The structure panel of an blog post entry.

Data Resources#

The Data Resources panel allows you to attach data resources to your entry to enrich the entry with data from external sources. Commonly this is used for defining pattern data resources for entry patterns.

An example view of the data resource element.

Unpublished content mode switch allows selecting content that, depending on data source configuration, hasn't been published yet, or that hasn't passed through normal workflow stages to become live, or belongs to a different environment.

Source#

The Source panel shows you the references of your entry as JSON data. You can see entry data:

• As it will be saved as JSON.
• As it would be returned for use in a consuming application, with data resources applied.

An example view of the source element.

History#

Here you can see drafts and published versions of your entry. Each row shows who made the change and when, and offers two actions on the right:

• View loads the entry as read-only with the references as they were at that point in time. From there you can restore the version, which creates a new version with the associated references, or go back to the current version.
• Compare opens a diff modal. A searchable menu lets you pick what to compare the version against: your unsaved changes, the latest draft, the latest published version, or any other past version.

The list shows a few more details:

• Each version carries an id code, such as nqbrkkk, to help refer to a specific version across screens or in a conversation with a teammate.
• Changes made within the same day are grouped. Use the chevron to expand or collapse the group and see the individual versions underneath.
• The live published version is marked with a Latest Published badge.
• Timestamps are relative, and hovering one shows the exact time.

By default, data is saved for the last 30 days. However, for projects on the Enterprise plan, data can be accessed for up to 365 days.

This is useful when there are multiple people collaborating on a single entry, or previous version data needs to be reviewed. You should note that this isn't a full audit feature. Uniform does track the references that are saved as JSON. It doesn't save the data coming from external sources. If you're reviewing a pattern, only the references will be saved.

An example view of the history element.

Locales#

The locales panel allows you to manage the locales and editions of your entry.

Releases#

The Releases panel lets you manage the current entry's inclusion in releases without leaving the editor. It lists every open or locked release in the project, alongside the Base state, so you can see where a copy of the entry exists and jump between releases while you work.

An example view of the release panel.

From the Releases panel you can:

• Browse and sort releases by release date or by name.
• Filter releases to show either all releases or only the releases that contain a copy (or a deletion) of the current entry.
• Search releases by keyword.
• See which releases include the current entry. A calendar indicator is shown next to each release that already contains a copy of the entry, and a tooltip clarifies whether the entry is new, copied, or deleted in that release.
• Activate a release by clicking its name in the list. The release switcher in the main navigation updates accordingly, and the active chip highlights the currently active release.
• Copy the entry into another release from the menu next to a release. The copy uses the version of the entry from the currently active release. If the entry already exists in the target release, you'll be asked to confirm before its release content is overwritten.
• Open the release details page to edit the release's schedule, name, and other settings from the same menu.

Properties#

Within the properties section you will see some basic information about your entry, including the:

• Entry slug
• Entry ID
• Created, modified, modified by, content type, and last published dates. Clicking on the content type will open it for editing.

An example view of properties element.

Property panel#

The main content area where you edit the fields of your entry.

Fields that are organized in groups will show as expandable sections.

Content collaboration#

Entries use the same collaboration behavior as compositions: a presence indicator for other people editing the same entry, version conflict handling when someone saves while you are editing, and live content updates that refresh the editor when the entry changes in the background, including changes made by AI or by an automation. See content collaboration for the details.