This article is meant to give a comparative analysis between the HTML macros of both apps. Both apps work on the same premise, to display HTML on Confluence pages, and have similar capabilities. Thus, there is a need to understand the differences in the apps and its features.
The analysis is done on the HTML macro (HTML for Confluence) and the HTML Macro macro (HTML Macro for Confluence).
Apps overview
HTML macro - HTML for Confluence | HTML Macro macro - HTML Macro for Confluence | |
|---|---|---|
Overview | The macro allows users to access HTML and XML content from a remote location or from Confluence itself, and displays it on Confluence pages. | This macro allows users to incorporate snippets of HTML on Confluence pages. |
Macro editor |
|
|
.gif?version=1&modificationDate=1713194333925&cacheVersion=1&api=v2&width=899)
Features parity
Features | HTML for Confluence | HTML Macro for Confluence |
|---|---|---|
Can enter HTML in macro editor directly |
|
|
Can access HTML content from remote locations |
Can specify URLs or use profiles to access content from remote locations, or, from GitHub/GitLab/Bitbucket repositories. |
...
App features analysis
Macro editors
...
| ||
Can access HTML content from other spaces or pages in Confluence |
Can use the Attachment parameter to access content across Confluence. |
|
Ability to publish content in other formats |
Can publish content as XHTML or plain text. |
|
Data security measures |
Can configure app to allow access from specific domains and strip JavaScript in the HTML content. Also, use the Allow script execution parameter to “clean” the HTML content to be displayed. |
Can configure the app to sanitize the HTML content. Also, use the Sanitize parameter to control display of the HTML content. |
Conclusion
The HTML Macro macro supports an easy, simple and efficient way of displaying HTML content.
The HTML macro, in comparison, supports more comprehensive methods to access and display the relevant HTML content from various sources.