Macros on a published site
The site generator ships around ninety macro exporters, so Capable macros render as real HTML rather than as a gap or a screenshot. That is the main reason to publish rather than export a PDF.
Anything without an exporter is skipped.
#What renders
Capable macros across diagrams, formatting, markdown, images, calendar, approval and PDF embed.
Native Confluence content: headings, tables, panels, code blocks, images and attachments.
Links between published pages, rewritten to site paths.
#What does not
A macro with no exporter does not render. Third-party app macros are the usual case, since their content lives in that vendor's app and the build has no way to reach it.
Clickable diagrams keep working. That is the difference between publishing and exporting a PDF: a PDF flattens a diagram, a site keeps its links.
#If a macro matters
The per-macro detail lives with each capability. Formatting records export behaviour on every macro page, including which macros behave 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 missing macro is usually a third-party one rather than a fault.
Images are downloaded at build time and rewritten to local paths, so the site does not depend on Confluence.
#Related
Ours render. Third-party ones do not.
