Handy Macros for Confluence (Formatting)
Capable recognises 7 macros from Handy Macros for Confluence (Stiltsoft). 6 of them convert, and 1 are detected and reported without being changed.
A reported-only macro is left exactly as it is on the page. It is counted so you can see how much of it you have, and decide what to do about it, but nothing is rewritten.
#At a glance
Macro | Becomes | Support |
|---|---|---|
Handy Button | Capable Buttons | Converted |
Handy Timestamp | Capable Metadata | Converted |
Handy Date | Native Confluence date | Converted |
Handy Poll | Capable Poll | Converted |
Handy Slider | Capable Progress bar | Converted |
Handy Status | Not converted, reported only | Reported only |
Handy Cards | Capable Search cards | Converted |
#What each one does
#Handy Button
Migrates to | Capable Buttons |
|---|---|
Support | Converted |
What survives the move
Label, link and the exact button colour, with a light or dark label picked automatically for contrast
What does not come across
Button width and open-in-new-tab behaviour may differ
#Handy Timestamp
Migrates to | Capable Metadata |
|---|---|
Support | Converted |
What survives the move
The value type (published date, last updated, or a custom value)
Worth knowing before you run it.
The date format is matched against a fixed list of supported patterns; anything unrecognised silently falls back to a standard day-month-year with time format.
#Handy Date
Migrates to | Native Confluence date |
|---|---|
Support | Converted |
What does not come across
Due-date colouring
Expiry behaviour
Worth knowing before you run it.
A Handy Date with no value is reported unsupported.
#Handy Poll
Migrates to | Capable Poll |
|---|---|
Support | Converted |
What survives the move
The question, the option list, and whether it was single or multiple choice
What does not come across
Existing vote counts, these live on the vendor's servers and cannot be migrated, so every migrated poll starts from zero
Worth knowing before you run it.
A poll with no options is reported unsupported.
#Handy Slider
Migrates to | Capable Progress bar |
|---|---|
Support | Converted |
What survives the move
Minimum, maximum, step, unit, label and current value
Interactivity, edit-in-view stays on
What does not come across
The red-to-green colouring by value
Worth knowing before you run it.
A slider sitting mid-sentence is moved onto its own line and the sentence is split around it, because the Capable macro is a block.
#Handy Cards
Migrates to | Capable Search cards |
|---|---|
Support | Converted |
Worth knowing before you run it.
Contributed by the Search capability, so it is only visible in the Search or Suite apps.
#Detected but not converted
These are found and counted so the report is honest about what is on your pages. They stay exactly as they are.
#Handy Status
Migrates to | Not converted, reported only |
|---|---|
Support | Reported only |
Worth knowing before you run it.
Status set names and colours live on the vendor's servers and only internal identifiers appear on the page, so there is nothing to convert. The recommendation is to recreate the sets in Capable Status Badge and swap the macros over by hand.
#Related
Native beats a macro, where native will do.
