Formats

What converts

Every format keeps:

  • headings, paragraphs, and bold, italic, strikethrough, code, subscript, superscript and coloured text
  • links, including links between pages
  • bulleted, numbered and task lists
  • tables, including column widths and merged cells
  • code blocks, with their language
  • quotes, panels and expand sections
  • status labels, dates, mentions and emoji
  • page layouts with columns
  • images and file attachments
  • right-to-left text, such as Arabic and Hebrew

Most formats have no syntax for some of these, such as status labels and mentions. For those, Markup bridge uses a convention of the format, marked with a cf- prefix, so the result still renders, and the import turns it back into the original. Macros the app doesn’t know are kept as data, and come back unchanged when the file is imported.

The examples below are the start of the same page in each format.

Markdown

GitHub-flavoured Markdown. Panels are GitHub alerts, expand sections are <details> blocks, and status labels and mentions are HTML spans, which GitHub, GitLab and most docs sites show as text.

This page describes the **payment service**, owned by <span data-mention="5b10ac8d82e05b22cc7d4ef5">@Ada Lovelace</span>.
Current state: <span data-status="blue">In review</span> since <time datetime="2026-01-01">2026-01-01</time>.

> [!NOTE]
> All amounts are stored in minor units (cents).

Tables with merged cells, cell colours or more than one paragraph in a cell are written as HTML tables, because Markdown tables can’t hold them. Unknown macros are a confluence-extension code block.

To render a page as HTML with Confluence’s look:

pandoc --from=gfm --standalone --css=confluence.css "Page.md" -o "Page.html"

AsciiDoc

Panels are admonition blocks, and status labels, mentions and dates are text with a role, such as [.cf-status-blue], which confluence.css styles.

Current state: [.cf-status-blue]##In review## since [.cf-date]##2026-01-01##.

[NOTE]
====
All amounts are stored in minor units (cents).
====
asciidoctor "Page.adoc"

reStructuredText

Panels are admonitions such as .. note::, columns and expand sections are containers, and status labels and mentions are interpreted text roles. The roles are declared at the top of each file, so Sphinx and docutils accept them without an extension.

Current state: :cf-status-blue:`In review` since :cf-date:`2026-01-01`\ .

.. note::

   All amounts are stored in minor units (cents).
rst2html --stylesheet=confluence.css --link-stylesheet "Page.rst" "Page.html"

Typst

Each page imports confluence.typ, which defines a function for each Confluence feature, such as cf-panel, cf-status and cf-expand. Change those functions to change how every page looks.

#import "confluence.typ": *
#show: cf-page

Current state: #cf-status("blue", "In review") since #cf-date("2026-01-01")\.

#cf-panel("info")[
  All amounts are stored in minor units (cents).
]
typst compile "Page.typ"

LaTeX

Each page is a complete document that loads confluence.sty, which defines commands such as \cfstatus and \cfmention, and environments such as cfpanel.

\documentclass{article}
\usepackage{confluence}
\begin{document}

Current state: \cfstatus{blue}{In review} since \cfdate{2026-01-01}.

\begin{cfpanel}{info}
All amounts are stored in minor units (cents).
\end{cfpanel}

Compile with XeLaTeX or Tectonic. They handle Unicode, and the shaping and direction of Arabic and Hebrew text:

xelatex "Page.tex"

Paths in nested pages

Pages in subfolders refer to the helper file and to images with relative paths, such as ../confluence.typ. Render each file from its own folder, or keep the folder structure as it was exported.