Registration is coming soon. Acrosite is not open for sign-up yet.Contact us
On this page
Content Editor

The content editor

A tour of the Acrosite content editor: content details, the body editor, the metadata rail with Save State and Publish Readiness, Custom Fields, SEO, and the output preview.

OverviewFor Editors and AuthorsUpdated October 1, 2026

The Acrosite content editor is where you write and prepare a Post, Page, or Custom Content Type item. It keeps the writing surface front and centre, with a metadata rail that tracks save state, publishing readiness, the featured image, and version history. This overview tours the editor so the rest of the editor docs make sense.

Open the editor

Open a content item from any content list (the Edit action on a row), or start a new one with Add Content. The editor opens on the item as a draft. A meta row at the top shows the project, the content type, the current status, and the save mode.

Content details

The first section, Content Details, holds the basics that orient the item everywhere it appears:

  • Title — the item's name.
  • Slug — its URL-friendly identifier (see Slugs and output filenames).
  • Excerpt *(optional)* — a short summary used in listings and as an SEO fallback.

The body

The Body section is where you write. Choose Block Editor for a structured writing canvas, or Source to work directly in Markdown and MDX. See Write with the Block Editor and Source mode for Markdown and MDX.

Structured content and SEO

Below the body, Custom Fields appear as structured inputs for the item's content type — see Fill in Custom Fields. The SEO Details section collects the SEO fields, and Advanced Output Details previews the generated Markdown and frontmatter.

The metadata rail

On the right, the rail keeps key controls in view:

  • Save State — the save mode and the last saved time, with Save Draft and Cancel. The editor uses manual saving; there is no autosave, so save your work as you go. ⌘S (or Ctrl+S) saves the draft, and if you try to leave with unsaved changes — a link, the browser's Back or Forward, or a reload — Acrosite or your browser asks first: Stay, or Leave Without Saving. If a save fails, your changes stay in the editor and stay protected until you save them.
  • Featured Image — set an optional featured image.
  • Publish Readiness — checks for the title, slug, body, SEO, and required Custom Fields, so you can see what still needs attention before review or publishing.
  • Version History — recent manual Save Draft snapshots. Restoring a version updates the editor until you save, so you can review an earlier draft safely.

Next steps

Frequently asked questions

No. The editor uses manual saving — use Save Draft (or ⌘S / Ctrl+S) to store your changes, and the rail shows when the draft was last saved. If you try to leave with unsaved changes, Acrosite asks before you go.
Version History lists recent Save Draft snapshots of the item. Restoring one loads it back into the editor, but nothing is committed until you save, so you can compare or roll back without risk.
It confirms the title, slug, body, SEO title, meta description, and any required Custom Fields are in good shape. Drafts can stay incomplete; the checks simply show what to finish before review or publishing.