Title: Become a GitHub Issues Coordinator
Author: WordPress.org
Published: April 10, 2026
Last modified: October 14, 2026

---

# Become a GitHub Issues Coordinator

## In this article

 * [Steps](https://make.wordpress.org/handbook/pathways/organize/coordinate-documentation-issues/?output_format=md#steps)
 * [Contribution checklist](https://make.wordpress.org/handbook/pathways/organize/coordinate-documentation-issues/?output_format=md#contribution-checklist)
 * [What happens next](https://make.wordpress.org/handbook/pathways/organize/coordinate-documentation-issues/?output_format=md#what-happens-next)
 * [Help](https://make.wordpress.org/handbook/pathways/organize/coordinate-documentation-issues/?output_format=md#help)

Take on the 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 by the repository
owner. [https://github.com/](https://github.com/) Issues Coordinator role for the
WordPress Documentation team. Beyond labeling, you’ll assign contributors to issues,
welcome them with the right resources, manage project board columns, and help prevent
issues from going stale.

 * **Prerequisite:** [Label Documentation Issues](https://make.wordpress.org/handbook/pathways/organize/triage-docs-issues/)—
   you should be comfortable labeling issues and familiar with the Documentation
   Issue Tracker before taking on this role
 * **Reference:** [GitHub Issues Coordinator role description](https://make.wordpress.org/docs/handbook/get-involved/team-roles/non-project-roles/#github-issues-coordinator)
 * **Connect:** Join [#docs](https://wordpress.slack.com/archives/docs) on SlackSlack
   Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
   The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
   if you haven’t already

## 󠀁[Steps](https://make.wordpress.org/handbook/pathways/organize/coordinate-documentation-issues/?output_format=md#steps)󠁿

 1. **Monitor new issues daily.** Subscribe to the [Documentation Issue Tracker](https://github.com/WordPress/Documentation-Issue-Tracker)
    and watch [#docs-firehose](https://wordpress.slack.com/archives/docs-firehose).
    Label new issues as they come in — project label first, then type-of-work, then
    version if applicable.
 2. **Assign contributors to issues.** When someone comments on an issue expressing
    interest, assign them. They must have commented on the issue for GitHub to allow
    assignment.
 3. **Welcome assigned contributors.** Comment with the name of the project rep for
    that documentation area, a link to any relevant onboarding docs, and when the next
    Docs team meeting is where they can ask for help.
 4. **Manage project board columns.** Move issues to the appropriate column (To do,
    In progress, Review, Done) as work progresses. If an issue has been assigned but
    untouched for a month, reassign it or move it back to unassigned.
 5. **Attend or follow triage meetings.** Every two weeks the team runs an issues triage.
    This is where priorities are discussed and stale issues get unblocked. Attending
    helps you understand what the team needs most.

## 󠀁[Contribution checklist](https://make.wordpress.org/handbook/pathways/organize/coordinate-documentation-issues/?output_format=md#contribution-checklist)󠁿

 * Labeling new issues as they arrive
 * Assigning and welcoming contributors with relevant project info
 * Keeping project board columns up to date
 * Flagging or reassigning stale issues

## 󠀁[What happens next](https://make.wordpress.org/handbook/pathways/organize/coordinate-documentation-issues/?output_format=md#what-happens-next)󠁿

This role complements the [Issues Triage Facilitator](https://make.wordpress.org/docs/handbook/get-involved/team-roles/non-project-roles/#issues-triage-facilitator)
and [Issues Reviewer](https://make.wordpress.org/docs/handbook/get-involved/team-roles/non-project-roles/#github-issues-reviewer)
roles. As you build a picture of the full issue landscape, you may want to take 
on one of those roles as well — or combine them.

## 󠀁[Help](https://make.wordpress.org/handbook/pathways/organize/coordinate-documentation-issues/?output_format=md#help)󠁿

Stuck? Check the [getting help guide](https://make.wordpress.org/handbook/pathways/before-you-begin/#getting-help),
then ask in [#docs](https://wordpress.slack.com/archives/docs).

**Further reading:**
 – [GitHub roles onboarding video](https://wordpress.tv/2023/11/14/the-documentation-team-github-roles-onboarding/)—
video walkthrough of all GitHub-related roles – [Labels guide](https://make.wordpress.org/docs/handbook/github-repository-and-projects/documentation-issue-tracker/)—
detailed reference for all label groups – [Team roles](https://make.wordpress.org/docs/handbook/get-involved/team-roles/)—
list of all project reps and their areas

  Organize

 Join a team

New here? [Get set up](https://make.wordpress.org/handbook/pathways/before-you-begin/)
with accounts, community basics, and info on badges.

First published

April 10, 2026

Last updated

October 14, 2026

Edit article

[ Improve it on GitHub: [article_title] ](https://github.com/WordPress/contributor-handbook/edit/main/pathways/organize/coordinate-documentation-issues.md)

Changelog

[ See list of changes: [article_title] ](https://github.com/WordPress/contributor-handbook/commits/main/pathways/organize/coordinate-documentation-issues.md)

[  Previous: Label Documentation Issues](https://make.wordpress.org/handbook/pathways/organize/triage-docs-issues/)

[  Next: Triage Theme Check Issues and PRs](https://make.wordpress.org/handbook/pathways/organize/triage-theme-check-issues/)