editor.json: the owner's editing screen

This file designs the content editing screen in the dashboard. It does not change the layout of the public website and does not declare new content fields.

Start with the fields in definition.json, then decide how an owner should find them:

editor.json

{
  "contractVersion": 1,
  "groups": [
    {
      "id": "homepage",
      "label": "Home page",
      "sections": [
        {
          "id": "opening",
          "label": "Opening section",
          "fields": [
            "hero"
          ]
        },
        {
          "id": "offer",
          "label": "What we offer",
          "fields": [
            "showServices",
            "services"
          ]
        }
      ]
    },
    {
      "id": "shared",
      "label": "Shared content",
      "sections": [
        {
          "id": "details",
          "label": "Business details",
          "fields": [
            "business"
          ]
        }
      ]
    }
  ],
  "collections": [
    {
      "path": "services",
      "view": "gallery",
      "labelField": "title",
      "descriptionField": "summary",
      "imageField": "image"
    }
  ]
}

Read the hierarchy

groups contains high-level navigation groups, such as Home page and Shared content. Each group contains sections. A section has a label and an ordered list of existing top-level field IDs.

In this example, the owner sees:

1. Home page → Opening section: the hero group, including headline, introduction and image.
2. Home page → What we offer: the show-services checkbox, then the repeatable services collection.
3. Shared content → Business details: the business name and phone number.

The order of the arrays is the order of the editor. Group/section IDs identify editor organization; they do not become content keys.

Fields are references

"fields": ["hero"] places the entire hero schema group in a section. "fields": ["hero.title"] is not supported here. A top-level field can appear only once across configured sections.

Unassigned top-level fields are still available: groups and lists receive automatic sections, and remaining simple fields appear in an automatic General section. Omitting a field is not a way to hide it.

The file must exist, but its content may be null to use automatic organization. A configured object needs contractVersion: 1. Labels are plain strings displayed as written; they are not translation maps.

Collections improve list summaries

collections configures how list items are presented. path points to the list; labelField, descriptionField and imageField point to fields inside one item. They help the owner recognize a card without changing its data.

For the complete walkthrough and design decisions, continue to design the content editor.