BlueConfetti

FLINT MARKDOWN EXPORT · HOW-TO

Choose the right Markdown export preset

See how the same pages come out in each preset, then pick the one that matches where the files are going.

Finished result

A side-by-side view of real output from the four presets for the same five fictional pages, and a short rule for choosing between them.

These examples come from the four downloads offered by the interactive demo, with all five handbook pages selected and other attachments off. Apart from export timestamps, they match the output of the released exporter.

Filenames

PageStandard MarkdownObsidian vault and AI contextGit documentation
Engineering Handbookengineering-handbook.mdengineering-handbook-1001.md1001.md
Onboardingengineering-handbook/onboarding.mdengineering-handbook-1001/onboarding-1002.md1001/1002.md
First weekengineering-handbook/onboarding/first-week.mdengineering-handbook-1001/onboarding-1002/first-week-1003.md1001/1002/1003.md

Title filenames are easiest to read but change when a page is renamed. Page IDs never change. Title plus ID is both readable and unique.

Links between pages

The handbook’s first paragraph links to two other pages. Standard Markdown and AI context use relative Markdown links (with their own filenames); Git documentation does the same with page IDs; Obsidian vault uses wikilinks:

Standard:  Start with [Onboarding](engineering-handbook/onboarding.md), then read the …
Obsidian:  Start with [[engineering-handbook-1001/onboarding-1002|Onboarding]], then read the …
Git:       Start with [Onboarding](1001/1002.md), then read the …
AI:        Start with [Onboarding](engineering-handbook-1001/onboarding-1002.md), then read the …

Inside HTML tables, Obsidian output adds navigation attributes so the link works in a vault: class="internal-link" data-href="engineering-handbook-1001/onboarding-1002#Before day one".

Panels

The handbook has an info panel. Each preset writes it differently:

Standard and Obsidian (callout):
> [!NOTE]
> This handbook is the source of truth. If something here is wrong, fix it.

Git documentation (blockquote):
> **Info:**
> This handbook is the source of truth. If something here is wrong, fix it.

AI context (plain text):
This handbook is the source of truth. If something here is wrong, fix it.

Callouts use the > [!NOTE] form that Obsidian recognizes; other Markdown tools may show it as an ordinary quote. Blockquotes work almost everywhere. Plain text removes the panel’s emphasis entirely.

Frontmatter

All four presets add YAML frontmatter with the same page fields. The difference is the export time: Git documentation leaves out exported, so unchanged pages stay byte-for-byte identical between exports. The other presets end their frontmatter with a line such as exported: "2026-10-11T16:00:00Z".

Which preset to choose

DestinationPresetWhy
An Obsidian vaultObsidian vaultWikilinks and unique note names
A Git repository or documentation siteGit documentationStable page-ID paths and clean diffs
An AI tool or other text pipelineAI contextReadable unique names and no panel syntax
Another Markdown editor, or not sure yetStandard MarkdownReadable names and common Markdown

A preset is a starting point. Advanced settings changes page links, panels, filename pattern and frontmatter fields. When you have changed them, the heading shows Customized settings, and choosing a preset again replaces those settings; custom metadata text is kept.

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.