Skip to content
Docs

Markdown Export

Some content has a second life outside Confluence: in a docs site, in a repository beside the code, in a notes app, or handed to an AI assistant that reads plain text better than a PDF. XPress gives you the page as Markdown: the content itself, cleanly, and laid out the way the place it is going expects, with nothing to tidy up afterwards.

Make it a template

Section titled “Make it a template”

A Markdown export is a template like any other. In the template designer, set Format to Markdown, and the Markdown section sets how the files come out. Start from where they will go:

Where the files will go What you get
GitHub Folders that follow your page tree, files named by their titles, GitHub’s own callouts for info and warning panels, HTML for tables that need it, your attachments, and an index
Obsidian Folders that follow your page tree, files named by their titles, [[Page]] links between them, callouts, page details at the top of every file, and your attachments
Documentation site Folders in your page tree’s order, page details at the top of every file, :::note style callouts, HTML for tables that need it, and an index
AI assistant Every page in one file, with each page’s details under its title and no pictures: one file to hand over
Custom Whatever you set below

Every setting under it stays yours to change. The preview shows the files the template makes and the Markdown of each page, from sample pages, by the same converter every export uses.

Make it a space’s default and every one-click export in that space comes out as Markdown: the byline’s Export (XPress) makes it in one click, and the page’s ··· menu and the XPress page both say Export Markdown.

Every setting

Section titled “Every setting”
Setting Your choices
Files One file per page, folders that follow the page tree (a page’s children sit in a folder named after it, beside it), or everything in one file
File names Numbered in the order of your page tree, such as 01-Getting-started.md, or the page title alone, such as Getting started.md
Page details The page’s title, author, last update, labels and address, as front matter at the top of each file, the way documentation sites and Obsidian read them. In one file, a line under each page’s title
Info, note and warning panels Quotes that say which they are, GitHub and Obsidian callouts (> [!NOTE]), or documentation site callouts (:::note). Each panel keeps its colour: a warning stays a warning, an error a caution
Pictures In the zip beside the files, as links to Confluence, or left out
Other attachments The PDFs, spreadsheets and other files attached to a page, in the zip, with the page’s links pointing at them
Links between exported pages Links to the exported files, or Obsidian’s [[Page]]
Tables Markdown tables, or HTML for a table Markdown cannot hold: merged cells, or a list, code or another table inside a cell
Index file An index.md that lists every page, nested the way your tree is, or none

Three places to ask for it

Section titled “Three places to ask for it”
  • From the page itself. Open Export (XPress) in the page’s ··· menu. With a Markdown template the button says Export Markdown; with any other, press Export as Markdown.
  • From the XPress page. Pick the page under Apps → XPress: the Will export panel says Export Markdown for a Markdown template, and offers Export as Markdown for the rest.
  • For many pages. In a space’s XPress page, tick the pages or branches you want and press Export as Markdown under the export button. For every Markdown setting, choose More options: tick the pages in that window, open Adjust for this export and set Format to Markdown. Save as new template keeps the settings.

What you get

Section titled “What you get”

One file arrives as a .md. Anything more, pictures or several pages, arrives as a .zip you can drop straight into a repository or a vault:

  • Pictures beside the pages, in an images folder, already linked from the pages that show them.
  • Links that still work. A link to another page in the same export points at that page’s file. A link to anything else points back to Confluence.
  • Names in your own letters: a page called Ürün Yönetimi becomes Ürün-Yönetimi.md, or Ürün Yönetimi.md when files are named by their titles.

What comes through

Section titled “What comes through”
In Confluence In Markdown
Headings, bold, italic The same, as Markdown
Lists Lists, as tight as Confluence shows them
Tables Markdown tables however long, or HTML where a table needs it
Code blocks Fenced code, with its language where Confluence names one
Task lists - [x] and - [ ]
Info, note, warning and tip panels Quotes that say which they are, or callouts
Status lozenges Bold words
Mentions The person’s name
Emoji The emoji itself
Pictures Files in images, linked from the page

Markdown is your content and nothing else. A cover page, a contents page, headers, footers, watermarks, fonts and colours belong to a page, and a Markdown file has none, so those stay with your PDF and HTML exports.

Where it is not offered

Section titled “Where it is not offered”

Some spaces require a watermark on everything they export, and some templates lock the look of a page in place. A Markdown file cannot carry either, so there XPress exports a PDF instead. A Markdown template can lock its own format, its file name and its Markdown settings, and those hold as Markdown. There is nothing to configure: where Markdown is not shown, that is why.

Next

Section titled “Next”