Published Capable Site page looks different from the Confluence page
What you are seeing
The published Capable Site page looks different from the Confluence page.
#Why it happens
Raw HTML is switched off on the published site as well, and diagram code blocks appear as styled code rather than drawn diagrams.
#What to do
Expect the difference. Where diagrams matter, insert a Capable diagram reference instead of a code block.
#Settings involved
Setting | Where | What it does |
|---|---|---|
Capabilities → Markdown | Global settings | Hiding Markdown removes it from the Capable nav bar and the page byline menu across the whole site. It does not stop existing macros from rendering. |
Space Capability Settings | Space settings | Auto shows the byline entry only when the page already has markdown. Always shows it in the byline of every page in that space. Never hides it there. |
Features → AI integration | Global settings | The setting reads: “Allow AI-powered features across Capable. Turn off to disable AI for all users.” Turning it off removes the Studio section (Generate markdown with AI) from the markdown catalogue. |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Document size through Rovo and MCP | 512 KB (524,288 characters) | If you create or update a markdown document through the Capable tools and it is larger than this, the request is refused rather than cut short. You are asked to split the document. |
#Related
Published site page shows an export note where a markdown document should be
The exporter could not resolve the body from any of URL, attachment, stored custom content
Exported Word or PDF shows raw markdown source in a code block
The markdown source in a fenced code block, never rendered prose.
Export and published sites
The rest of this family.
Found it? Good.
