The WordPress Documentation Team has shared its latest update, offering insights into ongoing projects, issue tracker statistics, and future priorities. With 677 open issues and 1339 closed issues, the team continues to tackle a significant workload across various documentation categories, including end-user guides, developer resources, and contributor handbooks.
Key Takeaways
- The Documentation Issue Tracker currently has 677 open issues and 1339 closed issues.
- Active projects include updates for WordPress versions 6.9 through 6.0 and the Block Editor End-User Docs.
- Only three issues are marked “Ready to publish,” signaling a need for more review resources.
- Contributor documentation remains underdeveloped, with just 17 issues logged compared to 395 for end-user documentation.
- Recent activity includes 76 issues closed, 12 created, and two pull requests merged.
Breaking Down the Issue Tracker
The Documentation Issue Tracker highlights the breadth of work being undertaken. Here’s how the current 677 open issues are distributed:
- By status: 424 issues are “To do,” 63 are “In progress,” 154 are “Under review,” and only 3 are “Ready to publish.”
- By version: Issues span multiple WordPress versions, with 6.4 leading at 71 issues, followed by 6.7 with 35 and 6.6 with 28. For the upcoming 6.9 release, there are 5 issues logged so far.
- By project: End-user documentation is the most active category, with 395 open issues, while developer documentation has 161, advanced administration resources have 12, and contributor documentation has 17.
In practice, this distribution reflects the ongoing prioritization of user-facing materials, which are critical for onboarding and troubleshooting.
Recent Activity and Key Projects
In February 2026, the Documentation Team made progress by closing 76 issues, merging two pull requests, and creating 12 new issues. Despite this activity, the “Ready to publish” count remains low, highlighting bottlenecks in the review and publishing process.
Active projects include documentation updates for WordPress versions 6.9 through 6.0, updates to Block Editor End-User Docs, and a redesign of HelpHub on WordPress.org. Additionally, inventories of technical parts from end-user docs and updates to the WordPress Glossary are underway.
Several repositories support these initiatives, including the WordPress Documentation Style Guide, the Documentation Issue Tracker, and end-user and contributor documentation repositories.
Challenges for Contributor Documentation
One notable gap in the team’s efforts is contributor-focused documentation. With only 17 logged issues, this category lags far behind end-user and developer documentation. For a platform reliant on community contributors, improving this area could streamline onboarding and participation.
Additionally, advanced administration documentation has just 12 issues, which may indicate either a lack of demand or a need for more specialized contributor expertise.
What This Means for WordPress Users
For WordPress professionals, the Documentation Team’s update underscores the importance of staying engaged with ongoing documentation efforts. Agencies and developers should monitor updates for versions 6.9 and earlier to ensure their workflows align with new documentation standards.
End-user documentation remains the team’s primary focus, which benefits site operators and less-technical users. However, the low “Ready to publish” count suggests delays in finalized resources. Developers and contributors can assist by reviewing and contributing to open issues.
The lag in contributor and advanced administration documentation signals an opportunity for experienced users to share their expertise. Improving these areas can directly impact WordPress’s community-driven ethos.
Frequently Asked Questions
What are the priorities for the Documentation Team?
Current priorities include updates for WordPress versions 6.9 through 6.0, improvements to Block Editor End-User Docs, and redesigning HelpHub on WordPress.org.
How can contributors get involved?
Contributors can assist by reviewing open issues in the Documentation Issue Tracker, merging pull requests, or tackling “To do” items across various projects.
Why is contributor documentation underdeveloped?
Contributor documentation has fewer logged issues, which may reflect a lack of focus or specialized resources. Addressing this gap could improve community engagement.
What is the “Ready to publish” status?
“Ready to publish” indicates issues that have passed review and are awaiting final publishing. Currently, only three issues hold this status.
