Macro migrators
They are run from the Migration settings tab.
#Where you do it
Task | Where |
|---|---|
Add a markdown document to a page | Confluence editor → /Markdown (Capable) [Suite] or /Markdown macro (Capable) [standalone], or the Markdown byline entry on a published page |
Write or edit the document body | The macro's Configure action, the maximize button on the rendered macro, or Edit on the library page |
Show a border and a title on the macro | Configure Markdown → 'Show border' checkbox and the 'Markdown title' field |
#Settings that affect this
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. |
Global settings → Migration | - | Markdown is not on the tab's exclusion list, so the tab ships. |
There is no Markdown-specific settings t | - | It contributes only a byline, query actions, an asset browser, a Search panel, a custom content renderer, migrators and the two macros. Every switch above is a shared Capable settings surface. |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Large-document scroll mode | 500,000 characters | Past this the document macro shows '⚠️ Large content detected. Rendering in scrollable mode.' and renders inside a fixed 1200px-high scroll box instead of inline. |
Virtualised rendering threshold | 500,000 chars ; 1,000,000 chars (large p | Above the threshold the document is chunked (400 lines or 60,000 characters per chunk, fences kept intact) and only visible chunks are rendered. |
Macro title and description input length | 50 characters each | The macro config's 'Markdown title' and 'Markdown description' fields and the from-scratch editor's title field all stop at 50 characters. |
#Worth knowing
The document macro's Title is not written by the released config UI: it is saved onto the stored document, and the header shows that document's title.
The macro reads the raw config and the form defaults set an empty array.
A macro whose stored document belongs to a different page refuses to save. This is what a copied page hits before reconciliation.
'Used on Pages' and the byline count both key on indexed data, and 'Used on Pages' counts only reference-macro usage. A plain document macro contributes nothing to it.
The byline is never shown to logged-out readers at all, regardless of the macros' anonymous access.
#Related
Better with company.
