Currently, when you install a new Drupal site with the Standard profile, you get 3 user roles by default: admin, Authenticated user (logged-in user when this issue → is fixed) and Anonymous. The admin role is supposed to serve for site building and development purposes and comes with almost every existing permission by default. The Authenticated/logged-in role has the same permissions as the Anonymous user (viewing content) plus is able to post comments. Drupal is a content management system but we don’t have any default user role to just manage content.
This proposal aims to create an out-of-the-box editor role to serve Drupal’s main purpose: manage content.
This solution will be focused mainly on content editors’ needs, but it’ll also be useful to guide and help site builders as part of the basic setup. So instead of the initial user story phrasing focused on the site builder/developer (for example: "A module developer can assign permissions to a content editor role"), we would say “A content editor can create content (...)” to focus on the content editor requirements. We need to define the minimum common functionalities that make sense in most of the project scales, and the initial set up should be easily extended.
Also, as @mlncn suggested, any modules that choose to use progressive enhancement if this particular role is present will be much improved.
As a result, when Drupal is installed with the standard profile, a new role will be created with a new set of permissions and options.
For content editors, the minimum industry-expected standard permissions for content editors will be set already.
For site builders, this role will be already created with basic permissions defined, which also might serve as a the starting point to enhance a project if needed and as a guide for best practices.
We need to define what are the minimum common functionalities/permissions and what are the industry-expected standards. Given Drupal solves a diverse scale and functionality-wise spectrum, we need to define a set of minimum of permissions and options that:
To find out this minimum common functionalities, we need to know what users expect and what the rest of the industry is doing. To do so, this initial plan is suggested to define and validate decisions and ideally it’ll be updated with sub-tasks if it’s approved:
Note that, like #479708: Rename 'Authenticated user' and 'anonymous user' so they are clearer → , this is not the opposite of ✨ Remove hardcoded anonymous and authenticated user roles Postponed: needs info .
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The Ideas project is being deprecated. This issue is moved to the Drupal project. Check that the selected component is correct. Also, add the relevant tags, especially any 'needs manager review' tags.
Changing to the standard issue template → would also help other contributors.
with the addition of recipes now is this something that's still needed?