What Capable Markdown is

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

Capable Markdown puts real markdown documents inside Confluence. It ships exactly two Confluence macros. A Markdown document macro that holds one document on a page, and a Markdown reference macro that points at a shared template and always shows its latest version. Plus a page byline entry, a "Capable Markdown" library page (global and per-space) with a catalogue, folders, version history and an AI "Studio", and a Search side panel. Documents are written in a three-mode editor (edit / split / preview) and can come from four places: written in place and stored under the page, a template from the space or global library, a markdown file attached to the page, or an external URL (GitHub, GitLab and Bitbucket web links are rewritten to the raw file automatically). Rendering is GitHub-Flavored Markdown. Tables, task lists, strikethrough, footnotes, GitHub alerts, syntax highlighting. With raw HTML stripped for safety, and fenced code blocks in any of 27 diagram languages (mermaid, plantuml, graphviz, d2, excalidraw, tikz, vega and more) rendered as live diagrams. Markdown has no settings tab of its own: everything an admin can change lives on the shared Capable settings surfaces. It is sold both as part of the Capable Suite and as a standalone "Capable Markdown" app, and the two differ in macro names, page export, AI Studio, indexing and library inserts.

#At a glance

Macros

Markdown, Markdown reference

Sold as

A standalone app, and a capability inside the Capable Suite

#A few things worth knowing

  • Exactly two Confluence macros exist and no more. There is no separate 'templates' macro. Templates are library assets, consumed either by copying into the document macro (a snapshot that then diverges) or by pointing the reference macro at

  • The document macro's Title is not written by the released config UI: it is saved onto the stored document, and the header shows that document's title.

  • The document macro's 'Markdown description' field is captured but never saved, while the unsaved-changes guard still counts editing it as a change.

The short version.