Adobe Experience Manager (AEM) provides non-technical users with a lot of power and flexibility when creating content as well as supplying tools for significant content reuse, like Content Fragments, but there are still situations in which developers need to be brought in to handle specific requirements. One of those cases is when content needs to be authored on a specific page but also surface values that are authored elsewhere in AEM.
Bounteous is always looking for ways to enable our partners using AEM to be self-sufficient and empowered in their authoring environment and so Contextual Content Variables, a newly released feature in Adobe Consulting Services (ACS) AEM Commons, seeks to solve this need for direct developer intervention when trying to surface a contextual variable inside authored content.
Contextual Content Variables
This new feature allows authors to use a specific token syntax that references variables stored elsewhere in the repository directly in the content they are authoring. By default, the feature comes preloaded with the following:
Aggregated properties from the current page
Aggregated inherited properties from pages above the current page in the content tree
The option to have the replaced value URL encoded
Here are a few examples of how the authored vs. rendered values will appear to authors and users of the site