The WordPress Documentation Team has introduced a structured meeting schedule and continues to manage a significant backlog of documentation issues, with 94 issues closed in the past month but 599 still open. This update highlights the ongoing challenges and efforts to improve WordPress documentation across multiple versions and projects.
Key Takeaways
- The Documentation Team follows a new monthly meeting cadence alternating Slack chats, video calls, and Contributor Day sessions.
- There are currently 599 open documentation issues across various WordPress versions and projects.
- In the past month, 94 issues were closed while 47 new issues were created, indicating active but challenging progress.
- Most open issues relate to end-user and developer documentation, with a notable backlog across recent WordPress versions including 7.0 and 6.4.
- Despite the volume of work, no pull requests were merged in the last month, signaling potential bottlenecks or resource constraints.
New Meeting Schedule Enhances Contributor Coordination
To improve collaboration and streamline contributions, the WordPress Documentation Team has adopted a new meeting format. The schedule includes Slack chat sessions on the first and third weeks of each month, video calls on the second and fifth weeks, and a Contributor Day video event on the fourth week. This structured cadence aims to maintain consistent engagement among contributors and provide multiple communication channels for different collaboration needs.
In practice, this schedule balances asynchronous discussion via Slack and synchronous interaction through video calls, addressing the diverse availability of contributors worldwide. Contributor Day sessions serve as focused sprints to encourage concentrated documentation work, aligning with the broader WordPress community’s release and development cycles.
Documentation Issue Tracker: A Snapshot of Current Challenges
The team’s Documentation Issue Tracker reports 599 open issues and 1,466 closed issues to date, alongside 51 issues tagged as “good first issues” and 132 self-assigned tasks. The distribution of issues by status shows 418 tasks marked “To do,” 50 “In progress,” and 131 “Review,” reflecting active workflows but also a considerable volume requiring attention.
Breaking down by WordPress version, open issues span from 6.1 to 7.0, with version 7.0 having 15 open issues and 6.4 the highest at 51. This spread indicates that documentation efforts are ongoing even for recent releases, not just legacy versions, underscoring the continual maintenance required for accurate and comprehensive user guidance.
Project-wise, the majority of open issues are concentrated in end-user documentation (352) and developer documentation (193), with smaller volumes in advanced administration (22) and contributor documentation (9). This allocation mirrors the typical demand within the WordPress ecosystem, where clear end-user and developer documentation are critical for adoption and effective site building.
Monthly Contributions: Activity and Bottlenecks
In the last month, the team closed 94 issues but did not merge any pull requests. Additionally, 47 new issues were created, reflecting ongoing identification of gaps or updates needed in documentation. The absence of merged pull requests is notable and suggests potential bottlenecks in review processes or volunteer bandwidth limitations.
Our analysis suggests that while issue triage and discussion remain active, the step from issue resolution to code or content merges may require additional focus. This gap can slow documentation updates and affect the wider community’s access to accurate information, especially as WordPress continues to evolve rapidly.
Ongoing and Active Documentation Projects
The team is concurrently managing documentation for a wide range of WordPress versions from 6.1 through 7.0, alongside specialized projects such as the Block Editor End User Docs, Advanced Administration Handbook, and the WordPress Glossary update. The breadth of projects illustrates the challenge of maintaining documentation that meets the needs of diverse users, from beginners to advanced administrators and developers.
Efforts to redesign HelpHub on WordPress.org and inventory technical parts of end-user docs demonstrate a strategic approach to improving documentation accessibility and quality. These initiatives aim to address historic weaknesses in discoverability and clarity, essential for empowering the WordPress user base effectively.
What This Means for WordPress Users
For most WordPress sites, accurate and up-to-date documentation is vital. The ongoing backlog and slow merge rate highlight a persistent challenge in keeping documentation current with the fast release cycle of WordPress core and related projects. Developers and agency owners should be aware that some documentation may lag behind the latest features, requiring cross-verification with source code or community forums.
We recommend contributors interested in improving WordPress documentation take advantage of the new structured meeting schedule to engage more effectively. Increased participation in Contributor Day events and Slack discussions can help accelerate issue resolution and pull request merges.
From a strategic perspective, the Documentation Team’s activity signals a continued commitment to improving WordPress usability at all levels. However, resource constraints typical of volunteer-driven projects mean that professional agencies and site operators should plan for documentation gaps and consider contributing back to the ecosystem where possible.
This update also illustrates the value of well-maintained issue trackers and transparent workflows. As WordPress evolves with new features and APIs, documentation will remain a cornerstone for adoption and innovation.
Frequently Asked Questions
Why are there so many open documentation issues in WordPress?
The volume of open issues reflects WordPress’s complexity and rapid release cycle. Many features and enhancements require updated documentation, and volunteer contributors must balance this work with other responsibilities, leading to a backlog.
How can contributors get involved with the WordPress Documentation Team?
Contributors can join the team’s scheduled Slack chats, video calls, and Contributor Day events. These meetings provide opportunities to discuss issues, propose fixes, and collaborate with other volunteers. The Documentation Issue Tracker is the central hub to find tasks.
What is the impact of delayed documentation updates on WordPress users?
Delayed documentation can cause confusion, especially for new users or developers adopting new features. It may lead to increased support requests or slower adoption until official docs catch up. Users often rely on community forums or third-party guides in the meantime.
What projects is the Documentation Team focusing on currently?
Current projects include documentation for WordPress versions 6.1 through 7.0, Block Editor End User Docs, Advanced Administration Handbook, WordPress Glossary updates, and redesigning HelpHub on WordPress.org.
