BlueConfetti

FLINT MARKDOWN EXPORT · USE CASE

Prepare selected Confluence pages as context for an AI assistant

Package a small set of project pages as Markdown an assistant can read, and know exactly what you are handing over.

Finished result

A four-page project brief exported as Markdown, with plain-text panels, a combined all-pages.md of 2,436 bytes and one recorded warning. You will know which parts the combined file carries on its own and which still depend on the adjacent files.

Flint Markdown Export does not send content to an AI provider, and it has no built-in AI integration. It prepares files in your browser, or in Atlassian-hosted functions for a background export. Choosing a destination, and following your organization’s rules for what may be shared with it, is a separate step that you control.

Example: a project brief

The fictional Harbor Lights brief (page 2001) has three child pages: Scope and goals (2002) with a flow diagram, Decision log (2003) with a dated table, and Open questions (2004) with a task list, a Jira issue key and a Jira issue list. The brief also links to a Visitor policy page that is not part of the export.

Export the brief

  1. Open the brief and choose Apps → Export to Markdown, then This page and descendants. Keep the four pages selected.
  2. Choose AI context. It uses relative Markdown links, filenames with titles and page IDs, and plain-text panels.
  3. Decide what metadata travels with each page. Open Advanced settings and clear any Frontmatter fields the destination does not need. Clearing author and last_updated_by keeps those names out of page frontmatter, but they remain in manifest.json and any @mentions in the text stay as names.
  4. Choose Review selection → Prepare full preview. In Preview file, pick all-pages.md and switch between Rendered and Markdown source. Open Open questions to see its conversion warning.
  5. Choose Build ZIP from preview → Download ZIP.

What the export contains

harbor-lights-project-brief-2001/
  harbor-lights-project-brief-2001.md
  harbor-lights-project-brief-2001/
    scope-and-goals-2002.md
    scope-and-goals-2002.assets/check-in-flow.svg
    decision-log-2003.md
    open-questions-2004.md
  all-pages.md
  manifest.json

One warning is recorded for Open questions: Jira issue list not exported (JQL: project = HL AND statusCategory != Done). The issue key HL-12 on the same page becomes an ordinary link to Jira; the live issue list becomes an HTML comment marker. If the assistant needs those issues, add a summary to the page or provide the list separately.

The combined file

all-pages.md joins the selected pages in tree order. Each page starts with a comment, its title and a source line, but the YAML frontmatter appears only in the individual files:

<!-- page 2001: harbor-lights-project-brief-2001.md -->

# Harbor Lights project brief

Source: https://example.atlassian.net/wiki/spaces/PRJ/pages/2001/Harbor+Lights+project+brief · Updated: 2026-10-08
...
Figures in this brief are planning estimates, not approved budget.

Background reading: the [visitor policy](https://example.atlassian.net/wiki/spaces/PRJ/pages/2900/Visitor+policy) and the [Scope and goals](harbor-lights-project-brief-2001/scope-and-goals-2002.md) page.

Three details in that excerpt matter for an assistant:

Trimmed frontmatter

With title, page_id, source_url, labels and updated kept, the brief’s file starts like this:

---
title: "Harbor Lights project brief"
page_id: "2001"
source_url: "https://example.atlassian.net/wiki/spaces/PRJ/pages/2001/Harbor+Lights+project+brief"
labels: ["project-brief", "harbor-lights"]
updated: "2026-10-08T15:30:00.000Z"
---

Match the files to the destination

Check the destination’s own documentation for the file types, number of files and sizes it accepts, and whether it reads folders, ZIP archives or images. Then choose:

Sample files

Limits that affect this task

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.