Adobe Experience Manager

Description - We would like to create meta tags (not limited to keywords) on pages through page properties. We would also like to have meta keywords (tags currently in page properties) inherit to child pages or be able to set default tags.Why is this feature important to you - This feature would make tag management simpler and more manageable out of the box.How would you like the feature to work - Add tags through page properties in 2 sections, one for keywords and one for miscellaneous with an option to inherit to prepopulate and customize from there.  For example, if a user selects to inherit tags, it would prepopulate with the parent page's mete tags.  The user can then add tags or remove tags from their page as needed.Current Behaviour - Custom page properties and Java needs to be developed for this implementation of tag management

Description -This feature helps the distributed authors be able to view tags in their localized language when they've set their language preferences as part of their user profile. How would you like the feature to work - This feature would display the localizations for tags vs the Tag Title when the Author's language profile is set to their local language and the localization is provided.Current Behaviour - The system currently displays the Tag Title regardless of user language setting and regardless of whether their is an available translation.

Hello,our client would like to have the ability to edit a page with enabled Live Copy Status view. This was possible with AEM 6.1.There are use cases where this is helpful, especially if there are a lot of components on a page and an editor needs to find and update the one with the broken inheritance.Can this be added to AEM?Thanks & Many regardsHendrik 

Hi All,In our day to day AEM dev life, we come across various requirements which demands us to create similar dialogs over and again. One such day a simple thought crossed my mind - What can make my life simpler?Below is the result of it --Request for Feature Enhancement (RFE) Summary :Ability to create the component & dialog from the author's instance.Use-case:Need to have author console/editor where developers can open that editor and start creating the component and dialog. Access should be given to the specific dev-users and only those users should be able to see the console and create the components. Able to provide the widgets similar to the metadata profile so that developers will just go and create the widget by drag & drop functionality. Ability to choose the root path of the project where the component needs to be created and other properties which are required for a component (eg., resourceType,component group). Current/Experienced Behavior:We cur