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 off there too, and diagram fences come out as styled code blocks rather than diagrams.
#What to do
Expect the difference; where diagrams matter, insert a Capable diagram reference instead of a fence.
#Settings involved
Setting | Where | What it does |
|---|---|---|
Global settings → Capabilities → Markdow | - | Hiding Markdown removes it from the Capable nav bar and the content byline menu across the site (app property capable-global-hidden-capabilities). It does NOT stop existing macros from rendering. |
Space settings → Space Capability Settin | - | Auto shows the byline entry only when the page already carries markdown; Always pins it in every page's byline in that space; Never hides it there. Stored on the space property <APP_HASH>_capable under capabilities.alway |
Global settings → Features → AI integrat | - | 'Allow AI-powered features across Capable. Turn off to disable AI for all users.' Turning it off removes the Studio (Generate markdown with AI) section from the markdown catalogue. Studio additionally requires the app's |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
MCP / Rovo document size cap | 512 KB (524,288 characters) | Creating or updating a markdown asset through the Capable tools refuses (rather than truncates) anything larger, with a message telling the caller to split it. |
#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.
