Capable Markdown for Confluence
Capable recognises 4 macros from Markdown for Confluence (Capable). 4 of them convert, and none are left behind.
#At a glance
Macro | Becomes | Support |
|---|---|---|
Markdown (Standalone → Suite) | Capable Markdown (suite) | Converted |
Markdown reference (Standalone → Suite) | Capable Markdown Reference (suite) | Converted |
Markdown templates (Standalone → Suite) | Capable Markdown templates (suite) | Converted |
Markdown embedded diagrams and images (Standalone → Suite) | Repointed diagram and image references inside migrated markdown | Converted |
#What each one does
#Markdown (Standalone → Suite)
Migrates to | Capable Markdown (suite) |
|---|---|
Support | Converted |
Worth knowing before you run it.
Currently matches nothing on a production site, by design: the standalone Markdown app has not been released to production yet, so this row renders with a count of zero and cannot be ticked. That reads as "nothing to migrate" rather than "not shipped yet".
#Markdown reference (Standalone → Suite)
Migrates to | Capable Markdown Reference (suite) |
|---|---|
Support | Converted |
Worth knowing before you run it.
A second pass.
#Markdown templates (Standalone → Suite)
Migrates to | Capable Markdown templates (suite) |
|---|---|
Support | Converted |
Copies markdown templates into the suite. Counted in items, runs once at the end.
#Markdown embedded diagrams and images (Standalone → Suite)
Migrates to | Repointed diagram and image references inside migrated markdown |
|---|---|
Support | Converted |
Finds diagrams and images embedded inside migrated markdown and repoints them at the copies the same run made.
Worth knowing before you run it.
This row always shows zero items and can never be ticked directly. That is intentional, not a broken row, it only reaches a run because the markdown and templates migrators name it as a prerequisite.
#Related
The embedded content is the hard part.
