Help the WordPress Documentation team keep its issue tracker organized by labeling new issues. When issues have the right labels, they reach the right people faster and documentation stays accurate and up to date.
- Reference: Labels guide — detailed reference for all label groups
- Connect: Join #docs on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ and introduce yourself
Steps
- Set up your testing environment. Open WordPress Playground — you’ll use it to verify issues when needed.
-
Request labeling access. Ask in #docs to be added as a 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/ Issues Coordinator. This gives you labeling access to the Documentation Issue Tracker. Allow time for access to be granted.
-
Subscribe to new issues. Subscribe to the repo and join #docs-firehose so you see new issues as they come in.
-
Find an issue that needs labels. Use
is:open is:issue no:labelin the repo search to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. for unlabeled issues. -
Apply the appropriate labels. Read the issue and follow the labels guide. Start with the project label (which docs area), then add a type-of-work label, and a version label if the issue is tied to a specific release. If you’re not sure which labels to use, ask in #docs.
Contribution checklist
- Coordinator access to the Documentation Issue Tracker
- Subscribed to the repo and #docs-firehose
- Labeled at least one issue with the appropriate project and type-of-work labels
What happens next
A Docs team member or project rep may adjust your labels — that’s normal and part of how you learn the system. Keep labeling new issues as they come in.
As you get comfortable, you can take on the broader GitHub Issues Coordinator responsibilities, including assigning contributors to issues and managing project board columns.
Help
Stuck? Check the getting help guide, then ask in #docs.
Further reading:
– Get Involved with the Docs team
– GitHub roles onboarding video — video walkthrough of all GitHub-related roles
– GitHub Issues Coordinator role — full description of coordinator responsibilities
– What is WordPress Playground? — learn more about using WordPress Playground
