Features¶
Exports individual pages, pages with descendants, or entire spaces via the Atlassian API. Skips unchanged pages by default, re-exporting only what has changed since the last run.
Supported Confluence features¶
Content & formatting¶
- Rich text: headings, paragraphs, bold, italic, underline, lists, tables, links, images, attachments, and image captions
- Code blocks: language-aware fenced code blocks
- Task lists: checkboxes with completion state
- Text highlights & font colours: preserved with inline HTML colour styling
- Status badges: converted to coloured inline highlights
- Info / note / tip / warning panels: converted to Markdown alert blocks (
[!NOTE],[!TIP], …) - Comments: open inline and/or page-level (footer) comments exported as sidecar files next to each page
- Include / excerpt-include macros: embedded pages either inlined or exported as Obsidian transclusion links (
![[Page Title]])
Page metadata¶
- Page properties: Page Properties macro exported as YAML front matter, Dataview inline fields, or Meta Bind VIEW fields; duplicate keys are disambiguated automatically (configurable via
export.page_properties_format) - Page Properties Report: dynamic cross-page property tables exported as a static snapshot or a live Dataview DQL query (configurable via
export.page_properties_report_format). Reports nested inside a third-party app macro (for example Table Filter) are also exported. Note that such apps apply their filtering, sorting and column hiding in the browser, and that behaviour is not available through the API, so the export contains the full unfiltered report. - Page labels: exported as
tagsin YAML front matter
Diagrams & add-ons¶
- draw.io: diagram files saved as attachments; embedded Mermaid diagrams extracted as fenced Mermaid blocks
- PlantUML: exported as fenced PlantUML code blocks, both the Server/Data Center macro (
plantuml) and the Cloud macro (plantumlcloud); the diagram source is exported, not the rendered image - Markdown Extensions: pass-through of raw Markdown macro content