What becomes a page
The build publishes current Confluence pages in the spaces you selected. Several content types are never published at all, and the product tells you how many it is skipping.
One thing here is more important than everything else on this page, so it is first.
Confluence page restrictions are not access control on a published site. The build reads every page in scope as the app. A page restricted to three people in Confluence IS published unless it carries an exclude label. Check this before you publish a space you have not audited.
#Published, and never published
What is published | Only CURRENT Confluence pages in the selected spaces. Drafts, archived pages and trashed pages are never published. |
|---|---|
What is NEVER published | Blog posts, whiteboards, databases, Confluence smart-link/embed content, comments and the page attachment list. There is no export path for these. The Overview tab counts them and says "N whiteboards will not be published" / "N blog posts will not be published" / "N smart links will not be published", informational only. |
Page restrictions | The build reads every page in scope as the app, and the ONLY filter is the exclude labels. A page restricted to a few people in Confluence IS published on the site unless it also carries capable-sites-exclude. This is the single most important thing to check before publishing a space. |
Folders | Confluence folders appear in the sidebar as non-clickable expand/collapse headings. They have no page of their own and are skipped by the previous/next links. |
Page order and URLs | Sidebar order and previous/next order both come from Confluence's own page tree, with the space homepage forced to the top and published as the space's index page. Every other page's file name is its slugified title. Two pages with the same title in one space BOTH get the page ID appended. |
Native Confluence content that converts | Tables, panels (info/note/warning), code blocks, expand and nested expand, layout sections and columns, task lists, decision lists, status lozenges, dates, emoji, mentions, inline/block/embed cards, media, plus the excerpt, children and include macros (children render as link cards; include splices the referenced page's content |
Native macros with exporters | Expand (details), Table of contents, and the legacy-content migration wrapper. |
Capable macros that publish | Image reference, Diagram, Diagram reference, Cards, HTML (sanitised, in a sandboxed frame), Embed/iFrame (https only), Progress bar, Buttons, Banner, Animated banner, Color palette, Lorem ipsum, Tooltip, Diff, Code, Background, QR code, Table (static), Footnote and Footnotes summary, Gallery, LaTeX math and LaTeX math inline, An |
Capable macros that DEGRADE | Form and Input publish as visibly disabled, read-only controls that cannot be submitted; user/space/page pickers become a note. Web extraction publishes its prefix and suffix with the literal text "N/A" where the live value would be. Diagram from URL/attachment publishes attachment source as plain text (truncated at 16,000 chara |
Capable macros that DO NOT publish (each shows a titled note explaining why) | RSS feed, Poll, Search cards, Search table, Word cloud, Github file, Image folder gallery, Link graph, Links, Word Count (the note calls it "Page statistics"), Space graph, Table from CSV, Capable Form reference. |
Capable macros that render NOTHING at all | Capable Studio and the legacy Image library macro (both are authoring pickers, not page content), and the Google Analytics macro, its tracking genuinely does not run on a published site. Use the site-level Integrations settings for analytics instead. |
Third-party macros supported | draw.io (core, ecosystem and both zero-egress Forge variants) as the stored preview image; PlantUML Diagrams for Confluence; Refined panels, expands (rendered open), steps, buttons and tabs; Kolekti / Mosaic cards, expand, background, tabs, AUI buttons, LaTeX, footnotes and tooltip; 19 Aura Content Formatting macros (Seibert); H |
Third-party macros that do NOT publish | Embedded draw.io (it points at a diagram on another page), Refined Activity Stream, Refined Page Tree, Refined Wiki Children, Handy Cards, Handy Poll, Handy Status (its data lives on the vendor's servers). |
Any other third-party macro | Publishes as a grey box quoting the macro's name or key on the live page. Only Capable's own macros get a friendly "not available on published sites" note. Confluence-native macros other than excerpt, children and include (Jira issues, roadmap planner, page tree, recently updated, task report…) land in that same grey box, which |
#The counts on the Overview tab
The Overview tab counts what it will skip: "N whiteboards will not be published", "N blog posts will not be published", "N smart links will not be published". Those are informational, not warnings.
#A few things worth knowing
There is no export path for blog posts, whiteboards or databases. If you need them published, they have to become pages.
Comments and the attachment list are never published.
Drafts, archived and trashed pages are never published.
#Related
Restrictions do not carry over. Check before publishing.
