Which front-matter formats are supported?

YAML (--- delimited), TOML (+++ delimited), and JSON ({} delimited) front matter blocks are all editable.

Does it know about static-site generator conventions?

Yes. Built-in schemas for Hugo, Jekyll, Astro, and Eleventy validate required fields and suggest common keys.

Can I switch between form and raw views?

Yes. Edit visually with form inputs or switch to the raw text view if you prefer typing it manually.

Is my front matter stored?

No. The editor is fully client-side — your data never leaves the browser.

YAML · TOML · JSON · Hugo · Jekyll · Astro

Edit front matter visually

Build YAML / TOML / JSON front-matter blocks with a structured editor. Templates for Hugo, Jekyll, and Astro included.

Quick Start

How to build a front-matter block

Pick a format, fill in key/value rows, copy the wrapped block into your post.

01
Pick a format
YAML (---), TOML (+++), or JSON — the delimiters change automatically.
Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.
formatGFMmarkedCommonMarklive
format · markdownyaml · GFM
```
---
…
---
```
loaded · GFMGFM · ready
02
Load a template
Hugo, Jekyll, and Astro presets seed common fields.
Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.
presetsoft-breaksoptionsconfiglive
template · optionshugo · live
```
title: …
draft: false
```
options applied · livelive
03
Edit fields
Numbers and booleans are auto-typed for TOML and JSON.
The preview is scoped under a .mde class so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.
editpreviewscoped CSSrenderstable
typed · renderedauto · ready
```
draft = false
```
rendered · liverendered
04
Copy block
Drop at the top of your Markdown post — delimiters included.
Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.
exportclipboard.md.htmlblob
✓ · exportedready · done
```
✓ Copied front matter
```
shipped · ready to shipsuccess

Pro tips

Author Markdown that renders everywhere

GFM is the safe default

GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.

Soft-break behaviour varies

A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.

Escape inside code fences

Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.

Anchors are slugified

GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.

Tables need a header row

The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.

Front matter is YAML

Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.

Use Cases

When to edit front matter

Static-site posts, Astro pages, docs.

Hugo blog post

Title, date, draft, tags — the canonical Hugo header. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.

GFM-compliant

Jekyll post

Layout, categories, permalink — copy-paste ready. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.

GitHub-perfect

Astro content collections

Typed front matter for Astro content collections. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.

diff-friendly

Docs page meta

Set title, sidebar order, draft status. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.

render-stable

Convert format

Switch a post between YAML/TOML/JSON without retyping fields. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.

cross-platform

Quick scaffolding

Drop into a new file when starting a draft. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.

SEO-friendly

FAQ

Frequently asked questions

Which delimiters?

YAML uses ---, TOML uses +++, JSON uses no delimiter and emits a plain object.

How are types inferred?

Numbers (123, 3.14), booleans (true/false) — anything else stays a string.

Can I have nested keys?

Not visually — paste arrays/objects as raw strings in the value cell.

Which generators support this?

Hugo, Jekyll, Astro, Eleventy, Gatsby, Docusaurus — anything that parses TOML/YAML/JSON front matter.

Is anything sent to a server?

No — the editor runs locally in your browser.

Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

47 in queue·8 shipped this month

Request queued. Thanks!