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
| Field | Value |
|---|---|
title, page_id | The page title and Confluence page ID |
source_url | The page’s Confluence address |
space_key, parent_id, breadcrumb | Where the page sits; the breadcrumb lists titles from the export root |
labels | The page’s labels |
author, last_updated_by | Display names of the creator and the latest editor |
created, updated, version | When the page was created and last updated in Confluence, and its version number |
exported | When 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.
- Export the handbook and choose Git documentation.
- Keep Add YAML frontmatter on and open Advanced settings.
- Under Frontmatter fields, clear
space_key,parent_id,breadcrumb,author,last_updated_byandcreated. - In Custom metadata (one key=value per line), enter the team’s fields:
team=Platform
project=Engineering handbook
review_cycle=quarterlyPrepare 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 overviewValues 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
- Up to 20 fields. Keys start with a letter and use letters, digits, underscores or hyphens, up to 64 characters.
- Built-in field names such as
titlecannot be reused. - Values are text up to 1,000 characters.
- A line without
=or a repeated key stops preparation with a message such asCustom metadata must use key=value, one field per line.orDuplicate custom metadata key: team. Return to selection to correct it.
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
- ENG-1001-custom-metadata-2026-11-02.zipFive pages with trimmed fields and three custom fields.
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.