Macros on a published site

Capable Sites renders more than 160 macros from Confluence, Capable and over a dozen other apps, so they appear on your site as real, working content rather than as a gap or a screenshot. That is the main reason to publish rather than export a PDF.

A macro it cannot render shows a short notice or a grey box instead, so you can spot it before a visitor does.


#What renders

  • Capable macros across diagrams, formatting, markdown, images, calendar, approval and PDF embed.

  • Macros from other apps, including draw.io, Refined, Mosaic, Aura, Handy Macros, Just Add+, Macro Pack and PlantUML.

  • Native Confluence content: headings, tables, panels, code blocks, images, attachments, mentions, emoji, smart links and SVG images, plus Page Properties and reports, Live search and draw.io diagrams.

  • Links between published pages, which point to the right page on your site.

Colours you set in Confluence, on panels, table cells, text, highlights and status lozenges, get dark mode versions on the site, and table column widths match the editor.


#What does not

A macro Capable Sites cannot render shows a short notice saying why, or a grey box with the macro's name. Macros that read live Confluence data, such as search results, page trees and activity streams, are the usual case, along with apps that keep their content on their own servers. Text diagrams from other apps, such as Mermaid, show their source text rather than the drawing. The Macro support matrix lists every macro, app by app.


#If a macro matters

To see what made it onto your site, open your site in Capable Sites and choose Macros. It lists every macro from the last successful build, how many times each one was used, and which pages use it.

Capable Sites Macros page listing successful macros with vendor and count, expanded to show the pages that use each one
Macros in the site sidebar shows results from the last successful build. Expand a macro to see which pages use it.

The per-macro detail lives with each capability. Formatting covers how each macro behaves on a site, including which ones work differently on a site than they do in Confluence.


#A few things worth knowing

  • Some macros render but behave differently on a site. The macro's own page says which.

  • A grey box usually means the macro comes from an app Capable Sites does not support yet. The Macro support matrix says which.

  • Images are copied into your site when it builds, so your published pages do not depend on Confluence.



Ours render. So do a good many of everyone else's.