Confluence Cloud: 'note' panel renders as 'warning' (yellow instead of purple)

[romenrg]

Problem

When using either the GitHub alert syntax (> [!NOTE]) or the admonition syntax (!!! note), the resulting Confluence Cloud page renders the panel as a warning panel (yellow) instead of a note panel (purple).

The info, warning, and tip panel types all render correctly with their expected colors. Only note is affected.

Reproduction

1. Create a markdown file with:

   > [!NOTE]
   > This should be a purple note panel

   Or equivalently:

   !!! note
   
       This should be a purple note panel

2. Upload to Confluence Cloud using text2confl upload

3. The panel renders with a yellow/warning appearance instead of purple/note

Expected behavior

The note admonition type should produce a purple panel-note in Confluence Cloud, matching the behavior when you manually create a "Note" panel in the Confluence editor.

Actual behavior

The panel renders as yellow (panel-warning) instead of purple (panel-note).

Environment

• text2confl version: 0.25.2 (also tested with latest)
• Confluence Cloud (not Server/DC)
• Using the @v2 reusable workflow from turo/docs-as-code

Notes

• info → blue panel ✅ works correctly
• warning → yellow panel ✅ works correctly
• tip → green panel ✅ works correctly
• note → yellow panel ❌ should be purple

The storage format output looks correct (<ac:structured-macro ac:name="note">), so this may be an issue with how Confluence Cloud converts the v1 storage format note macro to the v2 ADF panel-note type.

[romenrg]

After further investigation, the issue seems to be in Confluence Cloud's conversion from v1 storage format to v2 ADF, rather than in text2confl itself.

text2confl correctly generates <ac:structured-macro ac:name="note"> in the storage format output. However, when Confluence Cloud converts this to the v2 editor format, it seems to map the note macro to panel-warning (yellow) instead of panel-note (purple).

The other macro types seem to convert correctly:

• <ac:structured-macro ac:name="info"> → panel-info (blue) ✅
• <ac:structured-macro ac:name="warning"> → panel-warning (yellow) ✅
• <ac:structured-macro ac:name="tip"> → panel-success (green) ✅
• <ac:structured-macro ac:name="note"> → panel-warning (yellow) ❌ should be panel-note (purple)

One possible workaround in text2confl: when targeting Confluence Cloud (v2 editor), output the ADF-compatible <div data-type="panel-note"> format directly instead of the legacy <ac:structured-macro ac:name="note"> macro. This would bypass the seemingly broken conversion.

[romenrg]

Tested outputting <div data-type="panel-note"> directly in the markdown — Confluence Cloud ignores it when uploaded via the v1 storage format API. The ADF panel syntax is only understood when using the v2 ADF API, which text2confl doesn't currently support.

So the workaround of outputting ADF-style HTML would require text2confl to switch to the v2 API for page creation/updates, which is a bigger architectural change.

For now, note panels are the only panel type affected — info, warning, and tip all render correctly through the v1 storage format.

[zeldigas]

@romenrg thank you for the report. Indeed there is no one-to-one mapping when note macro is used.

I see that admonition in wysiwyg editor in cloud produces

<ac:adf-extension>
        <ac:adf-node type="panel">
            <ac:adf-attribute key="panel-type">note</ac:adf-attribute>
            <ac:adf-attribute key="local-id">d06bb716804d</ac:adf-attribute>
            <ac:adf-content>...content...</ac:adf-content>
        <ac:adf-node ...>
        <ac:adf-fallback>...</ac:adf-fallback>
</ac:adf-extension>

I'll work on using this block for confluence cloud (editor v2)