TFT

Markdown Front Matter Metadata Editor

Edit the YAML or TOML front matter in your Markdown files easily. Update titles, dates, tags, and custom fields for static site generators.

Markdown Front Matter Editor

Edit YAML front matter for Markdown files

:

How it works

This tool lets you edit the front matter metadata in Markdown files. Front matter is the YAML or TOML block at the top of a Markdown file that contains metadata like title, date, tags, and custom fields.

Static site generators like Jekyll, Hugo, and Gatsby use front matter to configure how pages are generated. This editor provides a user-friendly interface for modifying that metadata without manually editing the raw YAML or TOML syntax.

Common front matter fields:

  • title - Page or post title
  • date - Publication date
  • tags and categories - Content classification
  • description - Meta description for SEO
  • layout - Template to use for rendering
  • draft - Whether the content is a draft

Paste your Markdown with front matter, edit fields in the visual editor, and the tool updates the YAML or TOML while preserving your content. No more worrying about indentation errors or syntax mistakes.

When you'd actually use this

Updating blog post metadata in bulk

A blogger maintains posts in Markdown for their Jekyll site. They use this editor to update tags, categories, and descriptions across multiple posts without risking YAML syntax errors in each file.

Adding SEO metadata to existing content

Someone realizes their Hugo site lacks meta descriptions. They open each Markdown file in this editor and add description fields to front matter, improving SEO without touching the raw YAML.

Converting between YAML and TOML

A developer switches from Jekyll (YAML) to Hugo (TOML preferred). They paste YAML front matter into this tool and export as TOML, avoiding manual conversion of their entire content library.

Managing custom fields for content types

A team uses custom front matter fields for content workflows (author, review status, target audience). This editor makes it easy to add and update custom fields consistently across files.

Fixing broken front matter syntax

Someone's static site build fails due to YAML indentation errors. They paste the broken front matter into this editor, which validates and fixes the syntax automatically before exporting.

Preparing content for migration

A content team migrates from one CMS to a static site generator. They use this editor to add the front matter structure their new platform requires to existing Markdown content.

What to know before using it

Front matter must be at the file's start.Static site generators expect front matter as the very first thing in the file, delimited by --- for YAML or +++ for TOML. Content after the closing delimiter is treated as Markdown body.

Field names are case-sensitive.title and Title are different fields. Use the exact field names your static site generator expects. Common conventions use lowercase for standard fields.

Dates have specific formats.YAML and TOML handle dates differently. YAML often uses ISO 8601 format (2024-01-15T10:30:00Z). TOML has native datetime types. The editor handles format conversion between them.

Arrays can be written multiple ways.Tags can be a flow array ([tag1, tag2]) or block array (each on its own line with -). Both are valid. Choose based on readability and your project's style.

Pro tip: Keep front matter minimal. Only include fields your site actually uses. Extra fields clutter your files and can cause unexpected behavior in some generators.

Common questions

What's the difference between YAML and TOML?

YAML uses indentation and --- delimiters. TOML uses +++ delimiters and has a more explicit syntax. Hugo prefers TOML; Jekyll uses YAML. Both accomplish the same thing.

Can I add custom fields not listed?

Yes. You can add any custom field your static site generator supports. Common custom fields include author, thumbnail, series, or workflow status. The editor handles arbitrary key-value pairs.

Does this validate my front matter?

The editor parses your front matter, which catches syntax errors. Invalid YAML or TOML won't parse correctly. If the editor loads your fields, the syntax is valid.

What happens to my Markdown content?

Your content is preserved exactly as-is. The editor only modifies the front matter block. Everything after the closing delimiter passes through unchanged.

Can I remove fields from front matter?

Yes. Delete fields in the editor and they'll be removed from the output. This is useful for cleaning up unused fields or migrating between platforms with different requirements.

How do I handle multi-line values?

For descriptions or long text, use block strings in YAML (with | or >) or multi-line strings in TOML. The editor provides text areas that handle multi-line content properly.

Does this work with nested front matter?

Yes. Both YAML and TOML support nested structures. The editor displays nested fields in a hierarchical view, making it easier to manage complex metadata configurations.

Can I use this without a static site generator?

Absolutely. Front matter is just metadata. You can use it for any purpose: content management, documentation systems, or custom workflows that need structured data attached to Markdown files.