BlueConfetti

FLINT MARKDOWN EXPORT · HOW-TO

Customize YAML metadata for documentation and knowledge ingestion

Keep the page metadata your documentation or ingestion process uses, add your own fields, and leave the rest out.

Finished result

Every exported page starts with six Confluence fields and three custom fields, the same in every export that uses the settings.

Available fields

FieldValue
title, page_idThe page title and Confluence page ID
source_urlThe page’s Confluence address
space_key, parent_id, breadcrumbWhere the page sits; the breadcrumb lists titles from the export root
labelsThe page’s labels
author, last_updated_byDisplay names of the creator and the latest editor
created, updated, versionWhen the page was created and last updated in Confluence, and its version number
exportedWhen this export ran; the same for every page

updated belongs to the page. exported belongs to the export. The Git documentation preset leaves exported out so repeated exports do not change unedited files.

Example: documentation fields for a platform team

A platform team ingests its handbook into a documentation index. It needs the title, ID, source link, labels, last update and version, plus three fields of its own.

  1. Export the handbook and choose Git documentation.
  2. Keep Add YAML frontmatter on and open Advanced settings.
  3. Under Frontmatter fields, clear space_key, parent_id, breadcrumb, author, last_updated_by and created.
  4. In Custom metadata (one key=value per line), enter the team’s fields:
team=Platform
project=Engineering handbook
review_cycle=quarterly

Prepare the full preview and open any page in Markdown source. Architecture overview starts like this:

---
title: "Architecture overview"
page_id: "1004"
source_url: "https://example.atlassian.net/wiki/spaces/ENG/pages/1004/Architecture+overview"
labels: ["architecture"]
updated: "2026-10-08T15:30:00.000Z"
version: 4
team: "Platform"
project: "Engineering handbook"
review_cycle: "quarterly"
---

# Architecture overview

Values are written as quoted YAML strings, and custom fields follow the page fields. If you clear a field and turn it back on later, it moves to the end of the page fields. Custom values are the same on every page in the export.

Rules for custom fields

Turn frontmatter off

Clear Add YAML frontmatter and each file starts directly with its # Title heading. manifest.json still records every page field, including author and editor names, whichever frontmatter fields you choose. all-pages.md keeps a source line for each page.

Keep the settings

Open Saved profiles, enter a Profile name such as “Platform docs metadata” and choose Save current output settings. Profiles store custom metadata values, so do not put secrets in them. See export profiles.

Sample files

Sample files on this page are fictional. They were produced by the released Flint Markdown Export exporter, using a simulated Confluence site instead of a live one. Interface labels come from the released app; this guide contains no app screenshots.