**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.
Recent comments
We can no longer add contrib projects in the Tugboat sandboxes that we use for core PR's? Can this be fixed or is there a reason for this? We can add contrib projects to demo...
Apr 25th Weekly Meetings
The Mail System and MimeMail modules are now installed. I'll let you know if they solve the problem. Edit: Using Mail System with MimeMail I was able to send plain text emails. There is...
HTML Email treated as plain text
If you haven't already I recommend installing Mail System and MimeMail. The latter will help format emails as HTML and first helps with configuring which module will handle the formatting...
HTML Email treated as plain text