**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?
![image](https://user-images.githubusercontent.com/2385329/63654058-e8acf800-c77d...)
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.
![image](https://user-images.githubusercontent.com/2385329/63654119-9ddfb000-c77e...)
Based on this (and other) screenshots, I believe WordPress does (or did) something very similar:
![WordPress screenshot](https://www.theblogstarter.com/wp-content/uploads/2014/04/blog-post-link...)
(Source: https://www.theblogstarter.com/how-to-add-links-to-your-wordpress-blog/)
EDIT: Updated WP screenshot/source.
GitHub Issue #:
3993
Recent comments
Why not insert the script using a custom block at the very top of the page, <header>? Who said that it won't work correctly if you don't place it in the <head>? Especially...
Google tag and event snippet on the conversion page
You can use https://statichost.host for hassle free static experience.
Generate a Static Site
that was the first thing i tried, but thanks. i cannot see css file changes without clearing the css/js cache. for that reason i have been adding css snippets (<style> tags) into my...
Bandwidth optimization settings