Triaging Content Development Issues

The Training Team manages content development in the LearnWP Content – Development GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. project board. This is where content and feedback are passed between Content Creators and Editors before content is finally published on

Project board overview

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

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

Column nameReady to CreateDrafts in ProgressReviews in ProgressPublished or Closed
Issue detailsIssues have been vetted and relevant labels have been added.Issues being worked on by a Content Creator.Content waiting for reviews.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, and has been published.
Next destination“Drafts in Progress” column“Reviews in Progress” column“Published or Closed” column

Top ↑

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 Administrator Faculty Members or Training Team Representatives. Follow the steps below to triage issues in each status.

Top ↑

Issues in “Ready to Create”

  • Make sure the correct content creation checklist is applied to the issue
  • PingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @faculty-content-creators to see if any Faculty Content Creators have capacity to create the content; alternatively, ping specific Content Creators for issues based on their expertise

Top ↑

Issues in “Drafts in Progress”

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

Top ↑

Issues in “Review in Progress”

  • If the content has not been reviewed yet, ping @faculty-editors 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, and receive a Review # Complete label once that review has been completed; outlined below are the types of reviews and their guidelines:
  • If all reviews are complete, a Training Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. or Faculty Member can publish the content on Learn WordPress

Top ↑

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.

Last updated: