**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.
GitHub Issue #:
3993
Recent comments
Ruby Text can be a bit of a hassle to edit... Yes, I can imagine that. No idea, how an editor dialog (or whatever) for easier editing of those should look like - in terms of...
Specific tags to work in CKEditor 5
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Specific tags to work in CKEditor 5
Out of curiosity: why are these tags only relevant for admins? Don't "regular" editors on that site also need them under circumstances? Yes, the editors play nicely, no problem to...
Specific tags to work in CKEditor 5