Thank you all so much for your feedback. The core theme we heard was the “top right” problem, where our proposed configuration control could conflict with key macro content, negatively impacting existing app macros.
Resolution & updated design based on your feedback
Based on your feedback, we’ve iterated on our design. Now, to make it intuitive for users to both interact with AND configure macros in the Editor, we will move forward with the following interaction design for macros in the Editor.
When a user hovers over a macro, while editing a Confluence page, a selection / configuration control will appear next to the name of the macro, outside of the macro’s content. This way, it’s clear that:
- If a user wishes to interact with the macro, they can simply click on whatever they wish to interact with within the macro frame (example: clicking on the button to create a new page from a template.)
- If a user wishes to select the macro or configure the macro (i.e. to update its parameters, copy it, delete it, etc), they can click on the new selection / configuration control next to the name of the macro, outside of the macro’s content which will bring up the editing toolbar when clicked.
Demo: while editing a page, the user hovers on a macro, and can access configuration by clicking on the button that appears above the macro.
Demo: while editing a page, the user hovers on a macro, and can access configuration by clicking on the button that appears above the macro.
Implications for apps
We aim to begin a gradual rollout of these improvements to macros in the Editor by the end of June while closely watching macro engagement metrics and qualitative feedback.
These changes will apply to all macros when viewed in the editing experience:
- Macros built by vendors or customers using Connect
- Macros built by vendors or customers using Forge
- Macros built by Atlassian
No changes would be made to macros when viewed in the rendered experience.
No updates or work are be required on your end as a result of these changes.