The WordPress Documentation team has released its latest update, detailing progress on key initiatives and the current state of open issues. With over 685 open tickets and 1,331 resolved issues in the tracker, the team continues to refine and expand support resources for WordPress users and developers.
Key Takeaways
- The Documentation Issue Tracker reports 685 open issues and 1,331 closed tickets.
- Active projects include documentation updates for WordPress versions 6.0 through 6.9.
- Only three issues are marked as “Ready to Publish,” highlighting bottlenecks in review processes.
- End-user documentation remains a priority, with 402 issues tied to this project alone.
- 74 issues were closed in the past month, while 29 new ones were created.
Current State of the Documentation Issue Tracker
The Documentation Issue Tracker serves as the central hub for managing updates and tasks across WordPress’s documentation ecosystem. According to the February 2026 report, the tracker lists:
- 685 open issues
- 1,331 closed issues
- 70 “Good First Issues” designed for new contributors
- 162 self-assigned tasks
Breaking down by status, the issues are categorized as:
- 428 “To Do”
- 66 “In Progress”
- 156 “Under Review”
- 3 “Ready to Publish”
The relative scarcity of “Ready to Publish” items suggests that bottlenecks in the review phase may be slowing overall progress. For context, our previous coverage of WordPress teams often highlights similar challenges in review-heavy workflows.
Version-Specific and Project Breakdown
Documentation updates are aligned with WordPress versions, ranging from 6.0 to 6.9. Current statistics reveal the following distribution of issues by version:
- Version 6.9: 5 issues
- Version 6.8: 2 issues
- Version 6.7: 36 issues
- Version 6.6: 28 issues
- Version 6.5: 13 issues
- Version 6.4: 71 issues
- Version 6.3: 21 issues
- Version 6.2: 7 issues
From a project perspective, end-user documentation leads with 402 tracked issues, followed by developer documentation (161 issues), advanced administration (12 issues), and contributor-focused efforts (17 issues).
Recent Activity and Key Initiatives
Over the past month, the team has merged two pull requests, closed 74 issues, and added 29 new issues to the tracker. While these numbers reflect steady progress, the ratio of new issues to resolved ones underscores the ongoing workload.
Projects currently in focus include updates to the Block Editor End-User Docs, reviews of content from WordPress 5.9, and a redesign for HelpHub on WordPress.org. Other efforts include maintaining the advanced administration handbook and the WordPress Glossary, which are vital resources for administrators and contributors.
What This Means for WordPress Users
The update highlights both the scale and complexity of WordPress documentation efforts. For developers, the backlog of “To Do” items may signal opportunities to contribute, especially for those familiar with specific WordPress versions or features. Agencies relying on end-user documentation should note that critical updates for versions 6.4 and earlier are still pending, which could affect client support workflows.
For site operators, the slow pipeline to “Ready to Publish” status may mean delays in accessing polished, actionable documentation. We recommend monitoring the official WordPress documentation repositories for updates if your operations depend on recently introduced features.
Finally, this report reveals a strategic emphasis on end-user documentation and foundational resources like the WordPress Glossary, signaling WordPress’s continued focus on accessibility and usability.
Frequently Asked Questions
How do I contribute to WordPress documentation?
Contributors can start by visiting the Documentation Issue Tracker and exploring “Good First Issues.” These tasks are designed for beginners and often include clear instructions.
What is the HelpHub redesign?
The HelpHub redesign aims to improve the user interface and workflows for WordPress.org’s end-user support documentation, making it more accessible.
Why are so few issues marked as “Ready to Publish”?
The bottleneck often occurs during the review phase, where issues need approval before publication. Limited reviewer availability is a common challenge.
What is the WordPress Glossary project?
This project updates and expands the glossary of WordPress terms, providing a consistent reference for developers and end-users.
