Moderating content

Last updated on
22 September 2016

Content moderation happens via Content issue queue
IRC channel for questions/discussion: #drupalorg

General guidelines

Unpublishing vs deleting content

Always delete spam, empty or test content. You should only unpublish a post if you can conceivably imagine it being re-published in the future. This should only be for very rare cases.

Content that is heavily outdated and/or replaced by newer, more relevant content should be deleted. It is a good practice to highlight that specific content will be deleted soon (either via Discuss tab or issue in the Content queue) and give community members time to raise any concerns. After set time period passed, and if no valid concerns about deletion were raised, you can delete the content.

Duplicate content

If you see duplicate (identical) pieces of content, keep one instance and remove the other copies. 

If there are duplicate posts in multiple forums, choose the best forum and remove the remaining duplicates unless they already have responses. If they already have comments, make a polite note about duplicate posts referencing the other.

Badly formatted posts

If you see a post with bad formatting which messes up the page's layout, please edit it. A common mistake for newbies is to use two opening tags rather than an opening/closing pair. Tags like bold and italic can 'bleed through' beyond the post, while unclosed block-level tags can mess up the positioning of the sidebar.

If someone made a serious mistake while posting a forum topic and posted a correction in a comment below, try to update the original post and delete the correction.

Document your actions

If you are editing a node, use the "Log message" field and be sure that the "Create new revision" checkbox is on. If you edit a comment, just add [edited by {yourname} because...] and provide the reason for the change.

Front page promotion

How to review front page promotion request

  1. Make sure the story is highly relevant to the broad Drupal community and the Drupal project.
  2. Make sure the post is written in proper English, headings and images used where appropriate.
  3. At least two content moderators need to review the post for it's appropriateness and quality before it can be promoted.

Promoting / Demoting content on front page

  1. Posts need to be spaced out by at least 24 hours. Before promoting anything - check when the previous post was promoted and if there is anything queued in Front Page Schedule
  2. If previous post was promoted more than 24 hours ago and there is nothing scheduled for today/tomorrow in Front Page Schedule - you can promote the post.
  3. Edit the post and check "Promoted to front page" checkbox.
  4. Change "Authored on" date of the post to the date of promotion.
  5. Select the revision box and note the reason in the log and include the link to the issue requesting promotion.

How "Front page news" drop-down works:

  • If you simply promote a post to the front page without selecting anything in drop-down - post will appear on the front page and in
  • If you choose either "Drupal News" or "Association" in drop-down - same thing will happen.
  • If you promote a post to the front page and select "Planet Drupal" in drop-down, post will additionally appear on Planet.
  • If you just select something from drop-down without promoting a post to the front page - nothing will happen.

Moderating case studies

How to review a case study for promotion to Featured section

1. Check if the site and case study meet requirements for Featured section. Make sure content of the case study follows the guidelines.

Tip: to check if the site is built with Drupal you can use

2. Leave a comment in the issue with your opinion: should the case study be promoted to Featured? Why or why not? How can it be improved?

Case study can be promoted once there is an agreement of at least 2 members of the content team. However all opinions and reviews are welcome as they will help team members to make the right decision.

If both the site and case study do not meet the requirements and there are at least 2 comments from the content team members stating that, issue can be set to "closed(won't fix)"

How to review Community case studies

1. Browse Community showcase or use management view.

a. If you found spam, either as a comment or in the text of case study - open an issue in the Webmasters queue.

b. If you found a case study which has too few (or no) descriptions and technical details, leave a comment suggesting authors to improve their case study and link to Case study guidelines. You might also suggest them to consider moving their post to forum.
If there is no response and improvement to case study in a week - open an issue in the Content queue. Poor quality case studies will be hidden and eventually deleted.

c. If you found a high quality case study which is a good candidate for Featured section - open an issue and nominate case study for promotion.

Contribute as a writer

There are various way for anyone to contribute as a writer:

  • Seek impressive examples of Drupal websites and encourage their owners to write a case study for
  • Write case studies for those sites whose owners can't do it themselves but agree to provide information
  • Be available for requests from community members to write a case study for their site

Promoting/Hiding case studies

To promote case study to Featured section:
1. edit a case study and set "Status" field value to "Featured",
2. change "Authored on" date to the date of promotion,
3. select the revision box and note your actions in the log.
Do not check "Promote to front page" checkbox, Featured case studies appear in "Sites made with Drupal" block on the front page automatically.

To hide a case study (list of hidden case studies):
1. edit a case study and set "Status" field value to "Hidden",
2. select the revision box and note your actions in the log.

Moderating Drupal Planet

How to review a Planet Drupal or Planeta Latinoamerico request

  1. Check if the feed validates. Use to test the feed and link the result in your post in the issue queue.
  2. Check the content of the feed. We prefer to review feeds with at least two posts of which at least one has to be recent. Are these posts in the language appropriate for Planet or Planeta? Is the content wanted on the Planet/ Planeta both regarding to topic and content quality?
  3. Сheck if a dedicated "Planet Drupal" or "planeta" tag or flag is in use. Note: This tag or flag has not necessarily to be visible.

State your findings to all these checks in your post. If you come to positive results on all of these set the status of the issue to "reviewed&tested by the community". If you are unsure about the quality of the content ask for another opinion and leave the issue at "needs review". In case that there is a problem with any of these requirements set the issue to "needs work".

What about Planet Drupalgive requests?

Planet Drupalgive was created to give companies which actively contribute back to the community a showcase. The only things that need to be checked for those feeds are if the the feed validates and if the company requesting to be added indeed is giving something.

For moderators adding feeds to the Planet or Planeta:

  • To add a feed go to h
  • The name of the feed should be the person's name if it is written by one person, the company or blog's name for a multi-user blog (although we do not strongly enforce this pattern). No taglines.
  • Update interval should be 3 hours.
  • Feeds for Drupalgive should only be tagged for the Drupalgive feed and set to an update interval of 1 day.

Conditions for removal or temporary suspension from the Planet:

  • Feed does not conform to the content guidelines stated above: suspension and notify author.
  • Violations of the Drupal Trademark: removal.
  • Spam, hacked site, or offensive posts: suspension and notify author.
  • Off-topic posts: use common sense. If it's development-related and would be valued by community, no worries. If not, warn author via comment on site or e-mail. For repeated occurrences, suspension and notify author. Also be sure to encourage authors to create a 'Drupal Planet' specific tag.
  • Feed no longer works or no longer Drupal specific: removal.
  • Feed hasn't been updated in a year: set feed refresh interval to '1 day'.
  • Feed hasn't been updated in two years: removal.

Note: suspensions and removals should always have a 'Planet Drupal' issue created in the Content queue so we can log what action was taken, when, and by whom.