On this page
Content

Generated Markdown and frontmatter

The shape of the Markdown file Acrosite generates for a content item — the frontmatter keys, the SEO keys, Custom Field values, and the body — previewed before publishing.

ReferenceFor Developers and EditorsUpdated November 12, 2026

When a content item publishes, Acrosite generates a Markdown file with frontmatter — a block of structured metadata at the top — followed by the body. The editor can preview this exact shape before anything is published, so you always know what your site will receive.

Preview the output

In the editor, open the rail's Readiness tab and expand Generated Markdown / MDX Source under Generated Output. Acrosite shows the file it would generate from the current draft: the frontmatter, then the body. This preview updates as you edit, so you can confirm the output before review or publishing.

The frontmatter shape

A typical Post generates frontmatter like this:

yaml
---
title: "Welcome to our site"
slug: "welcome"
excerpt: "A short summary that orients the reader."
status: "published"
publishedAt: "2026-06-01T09:00:00.000Z"
updatedAt: "2026-06-01T09:00:00.000Z"
contentType: "posts"
seoTitle: "Welcome"
metaDescription: "A short, accurate summary of the page."
noindex: false
featuredImage: "/images/posts/welcome.webp"
section: "guides"
topics:
  - "news"
---

The keys you will see, in this order:

  • title and slug — from the content details.
  • excerpt — the optional short summary.
  • status — always "published": Acrosite writes the file only when the item is published.
  • publishedAt and updatedAt — when the item was published and last updated. The editor preview shows a note in their place, because they are filled in at publishing time.
  • contentType — the content type's key, such as posts or pages.
  • seoTitle, metaDescription, canonicalUrl and noindex — the SEO fields. Empty ones are left out; noindex is always true or false.
  • featuredImage — a Post's featured image, as its public path or URL.
  • Your Custom Field values — each at the top level under its Field Key (section and topics above). Empty values are left out.

The body and images

Below the frontmatter, the body is written as Markdown. Headings appear as #, ##, and ###; the Block Editor's blocks output standard Markdown, and MDX blocks are kept as trusted source text. A body image appears as a standard Markdown image with optional alt text and title, and a caption is written beneath it:

Markdown
Your body text in Markdown.

![Alt text](/images/posts/my-image.webp "Optional title")

_An optional caption._

Why the preview matters

Because the output is generated, you can design your site templates against a known, stable shape. Custom Field values sit at the top level under each field's key, the SEO values have their own keys, and images reference clean /images/... paths. See Where media lands in your repository for image paths and Acrosite-managed content paths for the folder layout.

Next steps

Frequently asked questions

Yes. The Generated Output panel on the editor's Readiness tab previews the generated Markdown and frontmatter from your current draft, so you can confirm the shape before review or publishing.
Each value is written at the top level of the frontmatter under the field's key. Single values (like Number or Select) appear directly; Multi-select values appear as a list.
The Block Editor outputs standard Markdown, and MDX is supported for content the blocks do not cover. MDX blocks are preserved exactly as written.