Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events

Sites: provide sling:alias property value in configurable columns for list view

Avatar

Level 3

5/13/24

Request for Feature Enhancement (RFE) Summary: Enhance the view settings for the list view so that you can select the alias (sling:alias property) next to the options which are available currently.
Use-case:

If you want to localize the URL's of your web pages, the way to go is to keep the name of the page in English and use the alias value for the translation. E.g. if you have a page about history, you would create a page with name history in AEM and set the alias of this page to geschichte (which is the German translation). So at the end you will get .../geschichte.html as external URL.

 

Current/Experienced Behavior: The alias value is hidden in the page properties of the page. So, from all views which are available in Sites console, you don't see this important value at one glance. If you have an external localized URL and want to figure out which page in AEM is behind, you need to open page properties of the pages in the folder in question. This is not really efficient as it could be hundreds.
Improved/Expected Behavior: With having the option to display the sling:alias property as a column at least in the list view, you could easily identify the page.
Environment Details (AEM version/service pack, any other specifics if applicable):  
Customer-name/Organization name: Carl Zeiss AG
Screenshot (if applicable):  
Code package (if applicable):  
2 Comments

Avatar

Administrator

5/22/24

@lutzU 

Thanks for proposing this idea
This has been reported to the engineering under the internal reference SITES-22127. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
Status changed to: Investigating

Avatar

Administrator

5/22/24

@lutzU 

Thanks for proposing this idea
This has been reported to the engineering under the internal reference SITES-22128. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
Status changed to: Investigating