Sneak Peak at Referentiality within Confluence

[GTD]

@PhilipFeldmann

Our macros have custom ui that is necessary to configure the parameters. This can be as “simple” as picking a color from a color picker, but can get very complex. Some of our macros are collections, for example we do offer a card collection, where a user can add multiple cards in a single macro and re-order them, adding multiple attributes to each cards as they go.
We also have controls like custom color palettes that get loaded from a remote configuration or a control that connects to unsplash to allow users to instantly import content from there. The default controls simply don’t cut it, our functionality simply can’t be build without custom ui. I am more than happy to show you a live demo of all the features that we’ve built with custom ui, that simply can’t be replicated using the defaults. Removing the option to use custom ui would kill our app, and many more, since a lot of vendors rely on this kind of functionality.

Thank you for elaborating on your use case and let me assure you that our Ecosystem team does not have any plans to remove the option to use custom ui. We are building multiple User Experience paths for Referentiality: use of ContextualToolbar and use of RightContextPanel. They are functionally similar in their ability to provide data to the Target app; however the latter would provide for better configuration of the Referentiality chain. With the Developer Preview of Referentiality released, you can try it on your test instance.