infoannouncementAtlassian calls it: Announcement
Forge Confluence Static Macros are now in Preview
- Announced
- Tags
- adopting-forge-from-connect, forge-core-platform
- Severity
- info, set by
reef/atlassian-rule-v2 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3505
Static macros for Confluence on Forge have progressed from EAP and are now available in Preview.
Static macros allow you to render Forge macro content natively on Confluence pages without iframe overhead. By returning ADF or Confluence Storage Format nodes directly, your app improves page load performance and provides a more seamless user experience.
Key features of the Preview release include:
- Native rendering: Content is rendered as part of the page HTML, eliminating iframe latency.
- Batch rendering: The
concurrencyproperty allows you to process multiple macro instances in a single invocation, further reducing app overhead. - Export support: Static macro content is automatically included when exporting pages to PDF or Word.
The feature is suitable for early adopters in development, staging, and production environments.
What you need to do
- Update your manifest: Add the
staticproperty to yourmacromodule inmanifest.yml. - Implement the render function: Ensure your function or endpoint is configured to receive an array of macro arguments and return the appropriate ADF or Storage Format nodes.
- Review the documentation: For full configuration options, schemas, and best practices, see the static macros documentation.
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.