As developers migrate apps from Connect to Forge they often need to maintain legacy functionality for backward compatibility, while providing a clean and modern experience for new users.

One common scenario involves macros that exist solely to support content migrated from previous editions (e.g., Data Center). In Connect, these legacy macros can be excluded from the macro browser by using the hidden attribute in the dynamicContentMacro module. This allows developers to retain support for older content without cluttering the macro selection interface with deprecated options.

Current Limitation:
Forge currently does not offer an equivalent to the hidden attribute. As a result:

• Legacy macros must be exposed in the macro browser, even if they are no longer relevant for new content

• This creates confusion for users and leads to a degraded authoring experience

• It hinders efforts to maintain clean, intuitive user interfaces during and after migration

Request:
We request the introduction of support for hidden or non-discoverable macros in Forge, allowing developers to include functionality that is:

• Available for rendering existing content

• Not displayed in the macro browser or available for insertion by users

Impact:
Adding this capability would:

• Significantly improve user experience during and after migrations

• Enable better separation between legacy support and modern functionality

• Help teams meet architectural and UI goals in their Forge-based apps

• Reduce confusion and risk for customers migrating from earlier versions