Adding field in touch ui dialog to define node name of page

Changing the node name on the fly would be rather costly from an effort perspective (as you need to make sure all references to that page are adjusted, plus managing un/publishing operations too).

If the goal is to control the name in the URL, maybe sling:alias (Alias field in page props) would be the way to go.

Hi @martin_reiss 

When you say you want to give the flexibility to author to specify the node name of the page, do you mean by the URL?

If that;s the ask then I will suggest you to refer the sling:alias property that is available OOTB with the page property. 

Please refer the link below:

https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html

http://www.sgaemsolutions.com/2019/02/usage-and-best-practices-of-page.html

Please Note: Alias won’t work in publish instance until you provide jcr:read permission for “/” for anonymous user. You just need to select root but you can deselect permission inside (like apps,etc etc ) root, because when you use sling:alias this particular logic (shown in the image below ) internally runs and if anonymous user don't have read access of “/” then it won’t work in publish.

Thanks!

Thanks for the fast and constructive feedback.

I have checked the out-of-the-box implementation and it already support defining the node name of a page. I have to check with my other colleagues why it has been customized to not to use the OOTB feature.

Kind regards

Martin