**Description of the need**
Since URL Aliases often closely match the title of a piece of content, you could think of a node's URL Alias like its machine name...
**Proposed solution**
That got me thinking; why not make the URL Alias field part of the node's Title field, in the same way that a Machine Name field is part of the entity's Title field?

So, when you create a piece of content for which URL Aliases are enabled, they would appear next to the Title as text that's generated automatically as you enter the Title. And there'd be a button that would enable an editable field for if you wanted to change the URL Alias to something other than the default.

Based on this (and other) screenshots, I believe WordPress does (or did) something very similar:

(Source: https://www.theblogstarter.com/how-to-add-links-to-your-wordpress-blog/)
EDIT: Updated WP screenshot/source.
Recent comments
Change --db-password= to --db-pass= https://github.com/backdrop-contrib/bee/blob/1.x-1.x/commands/install.be...
Can I run Backdrop CMS install script with Bee?
I found that I can run this bee command to run the install script: lando bee install --db-name=backdrop --db-user=backdrop --db-password=backdrop --username=admin --password=test1234 --email=test@...
Can I run Backdrop CMS install script with Bee?
There is also this issue: https://github.com/backdrop/backdrop-issues/issues/490 I have to say, I prefer having an explicitly defined summary field rather than part of the body field, so support that...
Summaries and Images