**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
Funnily we launched a new Dutch website this very week, milieucafe.nl It is not a 'news' website but operates in the context of local government. The layout focuses on content instead of...
Looking for examples of (local) news websites running on BackdropCMS
The answer is off topic, but I'll add a little. 1. Backend. Why you don't need links to other websites: Since you know the structure of your site and content, you can decide for...
Looking for examples of (local) news websites running on BackdropCMS
Hi Chrys, AI isn't always your best friend. A form alter hook is correct, but hiding by CSS isn't ideal. You could look at how the TinyMCE integration does it, which provides hiding...
CKEditor5: Here's how to prevent "Select Image from Library" from appearing