FLINT MARKDOWN EXPORT · HOW-TO
Keep page links and filenames predictable across repeat exports
Pick a filename pattern whose paths survive the changes your pages actually go through.
Finished result
Real paths for four filename patterns before and after one rename and one move, so you can see which pattern keeps which path stable.
The example changes
The five-page handbook was exported twice in Standard Markdown with different Filename pattern values under Advanced settings. Between the exports, Architecture overview (1004) was renamed System architecture, and First week (1003) moved from Onboarding to the handbook root.
| Pattern | Renamed page 1004 | Moved page 1003 |
|---|---|---|
{title} | engineering-handbook/architecture-overview.md → engineering-handbook/system-architecture.md | engineering-handbook/onboarding/first-week.md → engineering-handbook/first-week.md |
{id} | 1001/1004.md (unchanged) | 1001/1002/1003.md → 1001/1003.md |
{title}-{id} | …/architecture-overview-1004.md → …/system-architecture-1004.md | …/onboarding-1002/first-week-1003.md → …/first-week-1003.md |
{date}-{title} | …/2026-10-08-architecture-overview.md → …/2026-11-03-system-architecture.md | …/2026-10-08-onboarding/2026-10-08-first-week.md → …/2026-10-08-first-week.md |
What the table shows:
- Page IDs survive renames. Only
{id}kept the renamed page’s path. - Every pattern follows the hierarchy. A move changes the directory, so the moved page’s path changed in all four patterns.
{date}changes on every edit. It uses the page’s last-updated date, so an edit renames the file. Use it for dated snapshots, not for stable paths.- Title plus ID stays unique and readable, but still changes on rename.
Loading the first manifest under Compare with a previous export reports these as paths changed; see comparing exports.
Links to pages you did not select
Only links between pages in the same export become relative. In a second sample, only the handbook and Architecture overview were selected. The handbook’s link to Onboarding stayed in Confluence:
Everything a new engineer needs, in one place. Start with [Onboarding](https://example.atlassian.net/wiki/spaces/ENG/pages/1002/Onboarding), then read the [Architecture overview](engineering-handbook-1001/architecture-overview-1004.md).To list the links that still point to Confluence, search the extracted files for your site address, for example grep -rn '](https://example.atlassian.net/wiki/' --include='*.md' .. Links inside HTML tables use href= instead.
Filename rules
- The pattern must contain
{title}or{id}, may add{date}and fixed text, and cannot contain/or\. An invalid pattern showsFilename pattern must use {title} or {id}, with no path separators or unknown tokens. - Names become lowercase with hyphens, up to 80 characters, keeping letters from any script.
- Siblings with the same name get the page ID appended, so two pages called Notes become
notes-<id>.md. - The page list shows each page’s filename under its title as you edit the pattern.
- Unselected parent pages remain as directories without their own file.
Choose for your destination
- Git repository or documentation site:
{id}, as in the Git documentation preset. Diffs stay small and renames do not break links. - Obsidian or a folder people browse:
{title}-{id}. Readable and unique. - One-off handoff:
{title}. Easiest to read when nobody depends on the paths later.
Destinations still render links their own way: Obsidian follows wikilinks, and MkDocs turns .md links into page addresses. Test the destination after a change of pattern.
Sample files
- handbook-partial-title-id.zipTwo of five pages selected, title plus ID filenames, with a link that stays in Confluence.
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.