We heavily use Static Content Macros as a psuedo-template on 100s of our documentation pages that need to follow a specific format. In the static content macro we are embedding some other macros but they do not render correctly in the new editor/view.
In this screenshot, there are 3 “note” macros. The top one with the “native version” text is the macro added directly to the page. The bottom two are the macro embedded into a staticContentMacro using the adf-extension format and the structured-macro format.
Here is the code in our html page loaded by the staticContentMacro. The adf-extension code is the exact same code that Confluence stores for the native version, if you add the Note macro to a page and then View Storage Format.
<ac:adf-extension>
<ac:adf-node type="panel">
<ac:adf-attribute key="panel-type">note</ac:adf-attribute>
<ac:adf-content>
<p>adf-extension version</p>
</ac:adf-content>
</ac:adf-node>
<ac:adf-fallback>
<div class="panel conf-macro output-block" style="background-color: rgb(234,230,255);border-color: rgb(153,141,217);border-width: 1.0px;">
<div class="panelContent" style="background-color: rgb(234,230,255);">
<p>adf-extension version</p>
</div>
</div>
</ac:adf-fallback>
</ac:adf-extension>
<ac:structured-macro ac:name="panel">
<ac:parameter ac:name="panelIcon">:note:</ac:parameter>
<ac:parameter ac:name="panelIconId">atlassian-note</ac:parameter>
<ac:parameter ac:name="bgColor">#EAE6FF</ac:parameter>
<ac:rich-text-body>
<p>structured-macro version</p>
</ac:rich-text-body>
</ac:structured-macro>