If you attempt to create a menu entry for a node at /about, you can enter about into the menu UI, and it knows that's an alias. The menu entry it saves is actually for the system path, at node/2.
Could we do something similar for layouts? Many people who are new to backdrop try to put in an aliased path for the layout instead of the system path. Would it be possible check the path table, and do a switcheroo for them if we find a match?
For example, if they entered about we could
* lookup the matching system path of node/2, then
* realize that there's a system path of node/%, and
* rewrite that field as node/% for them.
This might have to be done with ajax as soon as they tab out of that field, since the contexts in the next question need to be added dynamically too...
Recent comments
Hi Kevin I am interested assisting you developing a theme by cloning feature from existing WordPress website. Please let me know your suitable time to discuss further...
Create a theme from existing website
I've updated the Zulip link in both places I found it. No need to post again, unless you have something new to say. We'll pull together feedback from all the sources.
Backdrop CMS Core Priorities
Should we post here again, what we posted over there? Or would that unnecessarily duplicate things? The link to a Zulip thread in this initial post leads to an internal one, but there's...
Backdrop CMS Core Priorities