Triaging Content Development Issues


The Training Team manages content development in the LearnWP Content – Development GitHub project board. This is where content and feedback are passed between Content Creators and Editors before content is finally published on https://learn.wordpress.org/.

Project board overview

Issues in this project board pass through 5 columns, or statuses, as progress is made.

General contributors do not have access to add/delete labels, set custom fields, or move issues between columns/statuses. Faculty Members need to check each issue and manually move them between statuses on behalf of contributors.

Column name Ready to Create Drafts in Progress Reviews in Progress Preparing to Publish Published or Closed
Issue details Issues have been vetted and relevant labels have been added. Issues being worked on by a Content Creator. Content waiting for reviews. Content has been reviewed and is in the final stages before being published. Completed issues.
Issues moves to the next column when… A Content Creator has commented on the issue, volunteering to create it. An Admin has confirmed the volunteer has necessary access to create the content on Learn. A Content Creator has attached the created piece of content. A piece of content has received three reviews. The content has been published –
Next destination “Drafts in Progress” column “Reviews in Progress” column “Preparing to Publish” column “Published or Closed” column –

Triage Tasks

Triaging is when a Training Team member checks through each column of the project board to assess the progress and status of issues. Triaging ensures that contributors are assigned, unblocked and enabled for the issues they are responsible for. This work also ensures that the Training Team meets their content creation goals by working to guide tasks to completion.

A GitHub triage can be performed at any time by Training Team Administrators or Representatives. Follow the steps below to triage issues in each status.

Issues in “Ready to Create”

  • Make sure the correct content creation checklist is applied to the issue.
  • Ping Content Creators for issues based on their expertise.

Issues in “Drafts in Progress”

  • Check in to see if the Content Creator needs any unblocking or assistance.

Issues in “Review in Progress”

  • If the content has not been reviewed yet, ping the @WordPress/learn-editors directly on the GitHub issue to see if any Faculty Editors have capacity to pick up the review; alternatively, ping specific Editors for issues based on their expertise.
  • All content requires three reviews. These can be counted by adjusting the Review Stage custom field.
    • An exception is if a piece of content has been waiting for reviews for two weeks. If so, then the content can be published even if it hasn’t received three reviews.
  • Once all reviews are complete, or a piece of content has been in “Ready for Review” for two weeks, then a Training Team Rep or administrator can publish the content on Learn WordPress.

Issues in “Preparing to Publish”

  • If an issue has been in this status for more than two weeks, see if the Content Creator needs any assistance to publish the content.

Issues in “Published or Closed”

  • Make sure that the Content Creator has properly publicized their content by announcing it:
    • to the Content Creator
    • to Marketing
  • In accordance with WordPress update releases, flag any out of date content with the Revisions Needed label and moving it back to the Ready to Create column.