Go to Settings → Markdown Macros
Select at least one Macro that you want to convert.
Click Convert
Note: you can only have 1 conversion process running at any given time.
Markdown Macro for Confluence Cloud can import several Macros from other vendors into our equivalent counterparts. Currently supported Macros are:
Avono Flowchart https://avono-support.atlassian.net/wiki/spaces/PUML/pages/17727499/Macro+flowchart
Avono PlantUML https://avono-support.atlassian.net/wiki/spaces/PUML/pages/9699367/Macro+plantuml
Atlassian native HTML macro https://confluence.atlassian.com/doc/html-macro-38273085.html and HTML include macro
All macros from Iframes for Confluence
Markdown from URL from Markdown Macro for Confluence
Permission required: User must be an Admin
To start a conversion process:
Go to Settings → Markdown Macros
Select at least one Macro that you want to convert.
Click Convert
Note: you can only have 1 conversion process running at any given time.
How it works
Once a user has selected macros to convert and triggered conversion, our app will:
Impersonate that user
Query Confluence for all pages containing the selected macros
For each macro on each page, convert it to our counterparts and save the page
Common issues:
Lack of permission
The conversion process impersonates the current user, so make sure the user has read/write access to all the pages containing selected macros
Invalid Syntax post-conversion
Avono’s Macros rely on a locally installed Graphviz package (https://avono-support.atlassian.net/wiki/spaces/PUML/pages/17727510/Installation ), so their Macros may use an old version whose syntax is not compatible with our backend. In this case, users will need to edit the Macro body to update to a modern syntax.
Javascript functionality is broken after migrating native HTML macro
When javascript runs in the HTML macro on-premise, it has access to all of Atlassian provided code such as AJS and jQuery. We do not provide these libraries in our macro. You will need to load whatever libraries you need via a script tag.
Look and feel of content is broken after migrating native HTML macro
When html is inlined into a Confluence page using the on-premise HTML macro, it will inherit Atlassian provided CSS. We do not provide this CSS in our macro. You will need to add whatever CSS you need to your macros to achieve the desired design.
Other unknown errors: users can try and rerun the conversion process again