Embedded Forge Macros EAP

Forge Forge UI Kit and Custom UI
, ,
1

Hi everyone,

We’re excited to announce the Early Access Program (EAP) for a new Forge platform capability: Embedding Forge Macros within Confluence pages. This EAP aims to support Connect to Forge migration, enabling richer macro experiences and more powerful integrations for your apps.

What’s new?

  • Embed Forge macros inside other Forge macros: Developers can now render Forge macros within the body of other macros, unlocking new composability and extensibility scenarios.

  • Support for UI Kit and Custom UI: The solution works for both UI Kit and Custom UI macros, with a new renderer package and FAUS service route to handle rendering and communication.

  • Bridge methods supported for embedded macros
    Most core bridge methods are now wired to work from embedded macros in Confluence (for example showFlag, invoke, invokeRemote, requestConfluence, requestJira, router methods, and view methods). See documentation for all bridge methods currently supported.

Learn more in the documentation.

Note: This capability isn’t a 1:1 replica of Connect platform, nested bodied macros. Hence Custom UI apps may experience some performance trade‑offs compared to Connect, while UI Kit apps are expected to remain performant.

To join this Early Access Program, please complete the Forge EAP sign-up form.

We’re looking forward for your feedback! Please leave any feedback on this post or via your individual EAP tickets submitted.

5 Likes
2

Hey @VickyHu, just curious, will this EAP allow bodied macros to be rendered on published pages as actual native ADF, rather than in rendered iframes? Or is there a separate request for that? I ask because we use a lot of bodied macros at our company and rendering the content stored within those bodied macros via separate iframes creates a heavy load on our pages.

2 Likes
3

Hey @VickyHu,
this is great news and closes some gaps we’re facing wrt. migrating our bodied macros to forge.

Are there any plans to also support Connect macros embedded in Forge macros?
Because if we would migrate our bodied macros to Forge right now, we’d have a lot of customers rightfully complaining that other macros are not rendered anymore in their existing content.
This means that as long as other macros (from other vendors) are not yet migrated to Forge, we cannot migrate our bodied macros to Forge.
But at least with this EAP we will be able to migrate our inline macros to Forge.

3 Likes