Publishing

CMS

Define content collections, fields, records, and singleton content for APIs, Sites, and external editing.

CMS

The CMS stores structured content in workspace-defined collections. Use it for content that should feed Sites, the public API, or external in-page editing.

Open the feature

  • Open CMS from the sidebar.
  • If the entry is missing, an admin can enable the CMS module and sidebar item.
  • API exposure is configured separately in System Settings → API.

Collections

  • A collection has a name, slug, singular and plural labels, description, mode, optional parent collection, display field, icon, and sorting settings.
  • Collection mode stores many records, such as posts, people, or projects.
  • Singleton mode stores one shared record, such as site settings or contact information. Opening a singleton starts creating or editing that one record directly.
  • Parent collections let you organize the CMS list into a tree. The table view shows nested collections with indentation, and the grid view shows parent/child grouping.
  • Hidden collections are excluded from the CMS collection view until you use the hidden-collections toggle. Hiding a collection does not change relation fields or API behavior.
  • Collection icons are visual markers in CMS list views only.
  • Reordering collections is available when the list is sorted by sort order, hidden collections are shown, and search or filters are clear.

Fields

  • Add fields from a collection's Manage Fields action.
  • Supported field types are short text, long text, rich text, Markdown, number, boolean, date, color, image, images, file, files, tags, select, JSON, relation, and relations.
  • Relation fields require a target collection. The display field controls how linked records are labeled in tables, cards, and relation pickers.
  • Select fields require at least one option.
  • Media fields can allow upload-only selection, item-folder selection, or item plus collection-folder selection. File fields can also restrict accepted MIME types and maximum file size.
  • Field types are locked after creation, but supported conversions are available from the field action menu. Field slug changes migrate stored record values to the new key, so external sites and API consumers must update to the new field key.
  • When you add a field to a collection that active API keys already read, Einblick can offer to add that field to those keys.

Records

  • Collection records have draft, published, or archived status.
  • The record list supports table and grid views, search, status filters, and field-based filters for supported field types.
  • Published Sites and default API filters read published records unless an API key or page configuration intentionally narrows or changes that behavior.
  • Manual record order is kept through the sort column and drag handles unless sorting is disabled for the collection.
  • Deleting a record removes the CMS entry permanently.