Documentation Team

Ever wished WordPress answers were easier to find, clearer to follow, and always up to date? That is exactly what the WordPress Documentation Team works on.

The Documentation Team helps people learn, use, and build with WordPress by improving documentation across the project. This includes end-user guides, developer resources, handbooks, and contributor-facing docs.

If you like writing, editing, organizing information, testing steps, fixing unclear instructions, or helping others learn faster, you will fit right in.

What Does the WordPress Documentation Team Do?

The Documentation Team coordinates documentation initiatives around WordPress and maintains the workflows that keep docs accurate and useful. 

A lot of work flows through the Documentation Issue Tracker on GitHub, which is the central place the team uses to track doc issues and improvements across different doc areas. The types of contributions include writing, editing, screenshots, testing instructions, triage, information architecture, and collaboration with other Make Teams.

Key Responsibilities of the WordPress Documentation Team

Maintaining and improving WordPress documentation

Contributors help update content so it matches current WordPress behavior, UI, and best practices. The team supports documentation across multiple areas and keeps quality consistent through shared workflows.

Triaging and fixing issues in the Documentation Issue Tracker

The issue tracker is where the team collects doc problems and planned improvements, and it is designed to cover any part of WordPress documentation.

Clear contribution workflows, reporting, and recognition

The Docs team maintains guidance on how to report issues and how to get involved, including using the #docs Slack channel as a quick way to raise documentation problems.

They also use a contribution submission flow to track work for recognition.

Collaborating across Make Teams

Docs often work together with Core, Support, Training, Hosting, and other teams. Many doc updates follow changes in WordPress releases, tooling, and team priorities, so cross-team coordination matters.

Challenges Faced by the Documentation Team

Keeping up with a fast moving product

WordPress changes often, so documentation can fall behind if updates are not tracked and maintained. The team periodically runs focused efforts to improve doc quality and update large areas that are outdated.

Making docs useful for different audiences

Documentation needs to work for beginners, advanced users, and developers, often for the same feature. Writing clearly without losing accuracy is a real skill.

Distributed collaboration and async communication

The team is global, so a lot of progress happens through asynchronous updates, issues, and Slack discussions.

How to Contribute During Contributor Day

Contributor Day is a great way to work with the Documentation Team, even if you are not a developer. Common Contributor Day tasks include:

  • Fixing unclear steps, typos, and outdated screenshots
  • Testing instructions and rewriting them to match what you see on screen
  • Triage: reviewing new issues, adding labels, or confirming the scope
  • Improving structure: headings, links, navigation, and glossary consistency
  • Helping with translation and localization initiatives when applicable

The team also holds regular meetings and online Contributor Days in the #docs Slack channel, with a published cadence on the team site.

Tools You Need Before Contributing

You can contribute to Docs with a very light setup. Here is what helps most:

  1. A WordPress.org account (for participating in Make discussions and community identity)
  2. Access to the WordPress Slack workspace (Docs uses the #docs channel)
  3. A GitHub account (Docs work is tracked in the Documentation Issue Tracker)
  4. A browser and a way to test WordPress (local site, staging, or Playground)
  5. A text editor for drafting and reviewing content

If you want recognition for your contributions, follow the team’s contribution reporting process on the Docs team site. 

Where to Start

  1. Read the Documentation Contributor Handbook to understand how the team works and where to contribute.
  2. Browse the Documentation Issue Tracker and pick something small to start with.
  3. Join #docs on WordPress Slack and say hello during a meeting or office hours.

The Documentation Team helps WordPress feel simpler, friendlier, and more reliable for everyone. If you enjoy improving clarity and helping people succeed faster, the Docs team will be happy to build with you.