We’re currently using Scroll Viewport for Confluence Cloud to render our Confluence knowledge base into a separate site. I’m not entirely sure what goes on in Scroll Viewport’s backend, but since it’s translating Confluence content into a website format, not all macros are supported out of the box. We were considering using a scaffolding addon to create a dynamic article footer, but we’ve been experimenting with using Forge to replicate that functionality instead.
The good news is that we were able to create a Confluence macro with Forge to display a dynamic article footer. It’s essentially a basic HTML block served through React, and displays on normal Confluence pages fine. The bad news is that Scroll Viewport won’t render it. In talking with their tech support, they linked me to How to Build Viewport Optimized Macros which states that the macro needs to support the export_view format in order to render properly. I created a UI Kit and Custom UI version of the app, but wasn’t able to find out how to set the render mode for the macro. From what I could gather from my research, it seemed like UI Kit/Custom UI can set the render mode as a recent feature?
Ultimately, what I’m thinking I might need to do, and would like some help with, is to see how to set the render output of the macro to a different format, maybe an Atlassian document format or PDF format or the like. I’m hoping that would be what we need to get this macro’s output to render in Scroll Viewport properly. Failing that, is there another way I could approach this problem in the app itself, such as translating the Forge app’s output into acceptable Confluence content first before export?
Any insights would be helpful. Thanks.