{"id":9995,"date":"2026-03-24T23:11:10","date_gmt":"2026-03-24T17:41:10","guid":{"rendered":"https:\/\/asia.wordcamp.org\/2026\/?page_id=9995"},"modified":"2026-04-06T21:04:08","modified_gmt":"2026-04-06T15:34:08","slug":"documentation","status":"publish","type":"page","link":"https:\/\/asia.wordcamp.org\/2026\/contributor-day\/make-teams\/documentation\/","title":{"rendered":"Documentation Team"},"content":{"rendered":"\n

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.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

If you like writing, editing, organizing information, testing steps, fixing unclear instructions, or helping others learn faster, you will fit right in.<\/p>\n\n\n\n

What Does the WordPress Documentation Team Do?<\/strong><\/h2>\n\n\n\n

The Documentation Team coordinates documentation initiatives around WordPress and maintains the workflows that keep docs accurate and useful. <\/p>\n\n\n\n

A lot of work flows through the Documentation Issue Tracker<\/em> on GitHub<\/a>, 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.<\/p>\n\n\n\n

Key Responsibilities of the WordPress Documentation Team<\/strong><\/h2>\n\n\n\n

Maintaining and improving WordPress documentation<\/strong><\/h3>\n\n\n\n

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.<\/p>\n\n\n\n

Triaging and fixing issues in the Documentation Issue Tracker<\/strong><\/h3>\n\n\n\n

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

Clear contribution workflows, reporting, and recognition<\/strong><\/h3>\n\n\n\n

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.<\/p>\n\n\n\n

They also use a contribution submission flow to track work for recognition.<\/p>\n\n\n\n

Collaborating across Make Teams<\/strong><\/h3>\n\n\n\n

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.<\/p>\n\n\n\n

Challenges Faced by the Documentation Team<\/strong><\/h2>\n\n\n\n

Keeping up with a fast moving product<\/strong><\/h3>\n\n\n\n

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.<\/p>\n\n\n\n

Making docs useful for different audiences<\/strong><\/h3>\n\n\n\n

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

Distributed collaboration and async communication<\/strong><\/h3>\n\n\n\n

The team is global, so a lot of progress happens through asynchronous updates, issues, and Slack discussions.<\/p>\n\n\n\n

How to Contribute During Contributor Day<\/strong><\/h2>\n\n\n\n

To make the most of your Contributor Day experience, we recommend reviewing the team\u2019s\u00a0call for contributors<\/a>. It includes details on what to expect, how to get started, and any prerequisites.<\/p>\n\n\n\n

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