FLINT MARKDOWN EXPORT · USE CASE
Create a portable onboarding handbook or project handoff
Give a new team, contractor or partner a portable copy of the pages they need, with the files, the date and the boundaries spelled out.
Finished result
A ZIP with four onboarding pages, a site map image and a safety-briefing PDF beside the page that uses them, plus a short note that states what the snapshot covers and what stays in Confluence.
Example: an operations onboarding branch
The fictional Operations onboarding page (6001) has three children: Your first day (6002), with a site map image and an attached safety briefing; Tools and access (6003); and Who to call (6004). It links to an Expense policy that should remain in Confluence.
Export the branch
- Open Operations onboarding and choose Apps → Export to Markdown, then This page and descendants. Only this branch is collected, not the rest of the space.
- Choose Standard Markdown. Title-based filenames such as
your-first-day.mdare easy for people to browse. - Under Output details, turn on Include other attachments. Images are always included; this setting adds the PDF.
- Choose Review selection. The summary line reads 4 pages · Standard Markdown · Images and other attachments · Frontmatter on. Choose Prepare full preview.
- Inspect the links. The three child-page links became relative links; the expense policy still opens Confluence. Check the summary for warnings; the sample has none.
- Choose Build ZIP from preview → Download ZIP.
What the recipient gets
operations-onboarding/
operations-onboarding.md
operations-onboarding/
your-first-day.md
your-first-day.assets/
safety-briefing.pdf
site-map.svg
tools-and-access.md
who-to-call.md
all-pages.md
manifest.jsonThe PDF is linked from the page that uses it, so it opens from the extracted folder:

The safety briefing is attached:
[safety-briefing.pdf](your-first-day.assets/safety-briefing.pdf)The panel on the root page keeps its Confluence link, because that page was not exported:
> [!NOTE]
> Travel and purchases follow the [expense policy](https://example.atlassian.net/wiki/spaces/OPS/pages/6900/Expense+policy), which stays in Confluence.
Package it as a dated snapshot
The archive name already includes the export date: OPS-operations-onboarding-2026-11-03.zip. Add a short note of your own beside the ZIP so the recipient knows what they have:
- The export time from
manifest.jsonand the source page link. - The pages and files included, and anything deliberately left out.
- That Confluence remains the source of truth, and who to tell about corrections.
The sample note below was written for this guide; Flint does not create it.
Sample files
- OPS-operations-onboarding-2026-11-03.zipThe onboarding export with its image and PDF.
- HANDOFF-NOTE.mdAn illustrative handoff note written by the sending team.
Before you send it
- Check who may read it. The files do not keep Confluence permissions. Mentions become people’s display names, and frontmatter can include authors and editors. Remove unneeded frontmatter fields under Advanced settings, then inspect
manifest.jsonand the page text too: frontmatter choices do not remove names from those files. - Expect it to go stale. The copy does not update. Send a new snapshot when the pages change.
- Keep the folders together. Moving a page file without its
.assetsfolder breaks its images and attachment links. - Check the size limits. Files over 75 MiB, or attachments beyond 300 MiB for the export, are left out with a message. See images and attachments.
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.