FLINT MARKDOWN EXPORT · GUIDES
Markdown export guides
Practical walkthroughs for taking Confluence pages into Git, AI tools, documentation sites and handoffs, with sample files you can download.
Each guide uses fictional pages and the released app’s labels. For every setting and limit in one place, read the Flint Markdown Export guide, or try the interactive demo.
Use cases
Complete workflows for a destination or audience.
Take Confluence pages into Obsidian
Choose pages, review a Markdown export, and check the notes in a vault.
Read the guideMove a Confluence documentation tree into a Git repository
Export a page tree with ID-based paths, review it on a branch, and see exactly what a refresh changes.
Read the guidePrepare selected Confluence pages as context for an AI assistant
Package a project brief for an AI tool and understand which files the destination needs.
Read the guideCreate a portable onboarding handbook or project handoff
Export an onboarding branch with its files and hand over a dated snapshot with a clear scope.
Read the guideTurn exported Confluence Markdown into a documentation website
Build and preview an MkDocs site from a Git documentation export, and test the details that break.
Read the guideHow-tos
Techniques you can reuse across exports.
Break a large Confluence space into manageable exports
Plan branch-sized batches under the 500-page cap and check manifests for overlaps and gaps.
Read the guideKeep images and attachments working after a Markdown export
Compare image-only and attachment exports, keep .assets folders with pages, and read size omissions.
Read the guideChoose the right Markdown export preset
Compare the four presets on the same five pages: filenames, links, panels and metadata.
Read the guideCustomize YAML metadata for documentation and knowledge ingestion
Choose frontmatter fields, add custom team and project fields, and check the result.
Read the guideSave export profiles for repeatable monthly or project exports
Save named output settings, reuse them for monthly exports, and replace or delete them.
Read the guideStart a background export and retrieve it later
Queue a background job, keep its job ID, and come back to download or cancel it within an hour.
Read the guideKeep page links and filenames predictable across repeat exports
See how title, ID and title-plus-ID filenames behave after a rename and a move.
Read the guideSelect exactly the Confluence pages you want to export
Use branch checkboxes, search, Select all matches and Selected only, then verify the page IDs.
Read the guideFind and manage export history as a user or Confluence administrator
Search loaded history, inspect settings and warnings, and understand admin views and retention.
Read the guideChecks and troubleshooting
Make sure an export contains what you expect.
Compare two Confluence exports to see what changed
Load an earlier manifest to count added, changed, moved and missing pages, then list them.
Read the guideUnderstand export warnings and fix missing or changed content
Read each kind of export warning, find it in the files and fix the scope or the source page.
Read the guideCheck a Markdown export before treating it as a dependable snapshot
Reconcile intended pages with the manifest, test links and files, and record the snapshot.
Read the guide