Adding a default editor role to Drupal Core

So far, we’ve had 166 submissions. Here is a summary of the results.

More than 84% approve of including a content editor role in Drupal core. 10.8% were neutral on the proposal, and only about 4.2% actually disagreed.

Naming the role

We also asked for suggestions on what the role should be named. Of the most popular, “Content Editor” took the lead (61.4%). 42.8% opted for naming it just “Editor,” and “Content Creator” received under 12% of the vote.

In the comments given, there was some debate about “Editor” sounding like a role that would have more reviewing tasks, as compared with a Content Contributor / Author / Writer.

We listed several types of permissions that could be included. Our guidelines for creating the list were to keep the basic set of permissions simple and avoid adding complexity. We included those tasks in the survey that comes enabled with Drupal core and would be widely used. Our premise is to help site builders expedite site configurations. We don’t want them to have to disable permissions, which can be easily forgotten and could lead to problems later on. Also, we would not be able to include common tasks that are found in the most popular features such as media management, revisions, and content moderation, etc., since they are not enabled by default.

Looking at the results, there were several tasks that were clear leaders. The following permissions are the ones most strongly agreed on for adding in the default set:

Other tasks that were generally favored include:

Respondents were more ambivalent about adding “Use the full HTML text format” to the basic permissions set. “Administer Blocks” is the only task that clearly received a negative rating.

We also asked about permissions on some of the most commonly used features from contrib modules to gain ideas for future consideration. A few that were generally favored are:

A section was included for respondents to write in what other tasks they thought should be considered. Most ideas centered around permissions from modules not enabled by default, but it is useful to have this insight for future exploration.

A few respondents suggested that they would like to see more responsibilities given to a content editor, such as:

Respondents also mentioned default permissions that would be useful to have in certain modules, such as:

In general, there was a consensus that editors should not have complete access to Structure and Configuration pages by default.

After reviewing the feedback in the issue, Twitter feeds and Slack channels, we found there was some interest in adding not one, but two roles to Core — that of an Editor and a Content Manager/Publisher. As a result, we added this question in the survey to better gauge relevance.

The respondents were more ambivalent about adding a content manager role as a default. Those who agreed/strongly agreed totaled 44%. The neutral votes were quite high at 25.3%. Those who disagreed/strongly disagreed came in at 30.7% combined.

Of those who favored adding this role, approximately 40 respondents wrote in the following permissions as ones suggested to add to the basic set of the Content Editor permissions:

Most of the tasks are focused on content moderation, although there were a range of ideas, sometimes conflicting.

In the survey, we also asked for additional comments and received good inputs on the content editor role as well as other recommended additions to Drupal core.

In a couple of cases, respondents wrote in that they did not agree with adding a default role because they view its usage as too specific and not relevant to a lot of websites. On the other hand, the Standard installation profile is already opinionated: it includes content types such as Basic Page and Article, as well as Taxonomy Vocabulary for tags. The goal of Standard is to try to fit 80% of use cases. Those who don’t want to start with this predefined set of defaults can use Minimal installation profile.

One suggestion that seemed interesting to us to consider in the future is to ask a question during the base Drupal install on whether to add the content editor role or not rather than installing it automatically.

Some other feedback that can inspire more discussion is to look into reviewing the Administrator role. Some took the opportunity to comment on better defining this role as they view it to be too broad, and perhaps splitting some permissions out into other admin type roles. This will be interesting to discuss on a separate drupal.org issue in the future.

Based on the conclusions and responses received in the survey and other discussion channels, we propose to add the Content Editor role as a default role.

The permissions should start out as a basic set. We recommend adding the following, listed as generic sets of permissions to be defined in a follow up issue:

Based on the survey results, we do not see enough support for adding other permissions. It is best to start out small and then evolve the primary concepts in future releases once we can evaluate the impacts of the MVP.

We look forward to discussing this further in the Drupal.org issue.

Are you a developer or designer for Drupal, and interested in the efforts to improve Drupal? Then get involved!

Related posts:

I write to liberate the truth I feel inside me.. “I choose to write” is published by Kelly Croot.

I spent this morning in controversy, doubting one of my latest free-will choices. I typically start my Sunday with a long-run. To manage expectations, long is rather subjective, indicating a longer…

Pada era globalisasi saat ini dimana kita hidup di masa Ilmu Pengetahuan dan Teknologi (IPTEK) mengalami perkembangan yang sangat pesat. Dalam era teknologi yang terus berkembang, pengguna gadget…