BlueConfetti

FLINT MARKDOWN EXPORT · CHECK

Compare two Confluence exports to see what changed

Check what changed between two snapshots of the same pages before you replace the older copy.

Finished result

Flint reports Compared with previous export: 1 added, 2 changed, 1 paths changed, 1 missing. A short jq command then names each page and explains every count.

How the comparison works

Every export includes manifest.json, which lists each exported page’s ID, version and file path. When you load an earlier manifest, Flint compares it with the export you are preparing:

ResultRuleCommon causes
AddedThe page ID is newA new page, a page newly selected, or newly readable to you
ChangedThe version number differsAn edit was published in Confluence, including a rename
Paths changedThe file path differsA rename with title filenames, a move, or a different filename pattern
MissingThe page ID is no longer presentNot selected, outside the scope, no longer readable to you, moved elsewhere, or deleted

A missing page does not prove deletion. The comparison also ignores attachment contents, warnings and settings.

Example: one day of changes

The first sample export, made on 2026-11-02, contains the five-page handbook in Standard Markdown. Before the second export, four controlled changes happened:

Run the comparison

  1. Keep the earlier export’s manifest.json. It is in the ZIP’s top folder.
  2. Open the same root page, choose Apps → Export to Markdown and This page and descendants, then select the pages and preset for the new export.
  3. Open Compare with a previous export and choose the file under Previous manifest.json. Wait for Previous manifest loaded. A manifest from another Confluence site is rejected with Choose a Flint manifest from the same Confluence site.
  4. Choose Review selection → Prepare full preview, or Export ZIP. The comparison notice appears above the preview or the export summary.

The notice gives counts only. To see which pages they are, compare the two manifests. This jq command (tested with jq 1.7.1) prints one line per difference:

jq -c -n --slurpfile old manifest-2026-11-02.json --slurpfile new manifest-2026-11-03.json '
  ($old[0].pages | INDEX(.page_id)) as $a
  | ($new[0].pages | INDEX(.page_id)) as $b
  | ($b | to_entries[] | .value as $p | $a[.key] as $q
      | if $q == null then {change: "added", id: $p.page_id, title: $p.title}
        else (if $q.version != $p.version then {change: "changed", id: $p.page_id, title: $p.title, version: "\($q.version) -> \($p.version)"} else empty end),
             (if $q.path != $p.path then {change: "path changed", id: $p.page_id, path: "\($q.path) -> \($p.path)"} else empty end)
        end),
    ($a | to_entries[] | select($b[.key] == null) | {change: "missing", id: .key, title: .value.title})'
{"change":"changed","id":"1003","title":"First week","version":"4 -> 5"}
{"change":"changed","id":"1004","title":"System architecture","version":"4 -> 5"}
{"change":"path changed","id":"1004","path":"engineering-handbook/architecture-overview.md -> engineering-handbook/system-architecture.md"}
{"change":"added","id":"1006","title":"Incident response"}
{"change":"missing","id":"1005","title":"Release checklist"}

The rename counts twice: as changed, because it published a new version, and as a changed path, because Standard Markdown names files by title. With the Git documentation preset’s page-ID filenames the same rename keeps its path, while a move to another parent still changes it.

Decide what each result means

Sample files

Limits

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.