Some links on this page are affiliate links. We may earn a commission when you click through and make a purchase, at no additional cost to you.
The WordPress Core development team is set to hold their next Developers Chat on Wednesday, May 6, 2026, at 15:00 UTC in the core channel on Make WordPress Slack. This live meeting is a crucial opportunity for contributors and hosting partners to coordinate on upcoming releases and core improvements. The agenda outlines key topics including the imminent release candidate for WordPress 7.0, a proposal to automate documentation generation for blocks, and an open floor for wider discussions and ticket assistance.
Key Takeaways
- WordPress 7.0 Release Candidate 3 (RC3) is scheduled for May 8, marking a critical phase before the final release.
- Hosting providers like Bluehost, Kinsta, GoDaddy, and others are actively participating in Real-Time Communication (RTC) testing, crucial for the release stability.
- A new proposal aims to auto-generate Block Editor Handbook documentation directly from block.json files, streamlining contributor efforts.
- The dev chat emphasizes community-driven discussions and ticket prioritization for the upcoming major and maintenance releases.
Upcoming WordPress 7.0 Release Candidate and RTC Testing
WordPress 7.0 is approaching its final stages with Release Candidate 3 (RC3) scheduled for Friday, May 8. This milestone, also referred to as the “new Beta 1,” represents the last opportunity for contributors and testers to identify and resolve issues before the general availability release. RC phases are critical in ensuring quality, performance, and compatibility across the broad WordPress ecosystem.
One notable aspect of this cycle is the increased involvement of hosting providers in Real-Time Communication (RTC) testing. Partners including Bluehost, Kinsta, GoDaddy, XServer, Ionos, and WordPress.com are contributing by validating RTC capabilities on their platforms. RTC features enable real-time collaboration and communication in the block editor and other parts of WordPress, which require robust support from hosting environments to deliver a smooth user experience. Our testing across various hosts confirms that RTC integration remains a complex but vital component for modern WordPress workflows.
Proposal to Auto-Generate Block Editor Handbook Documentation
One of the agenda highlights is a general proposal to automate the generation of Block Editor Handbook documentation using the block.json metadata files that plugin and theme developers use to register blocks. In practice, this would mean that much of the descriptive content, attributes, and usage guidelines could be extracted directly from the block’s JSON schema, reducing duplication and the maintenance burden on documentation contributors.
This move aligns with broader efforts to streamline the onboarding of new contributors and ensure that documentation stays accurate and up-to-date with the codebase. The Block Editor Handbook is a key resource for developers working with blocks, and automating parts of it could accelerate feature adoption and reduce errors caused by outdated docs. However, this approach requires careful design to handle nuances and contextual information that JSON alone cannot express.
Community Discussions and Ticket Prioritization
The dev chat maintains an open floor section, encouraging contributors to raise any topic relevant to the upcoming releases or the overall direction of WordPress Core. This inclusive approach helps surface critical issues that may not be on the official agenda but impact real-world deployments.
Tickets slated for the next major or maintenance release receive priority during the chat. Contributors are urged to provide ticket or Pull Request (PR) links, along with availability for synchronous or asynchronous discussion. This method ensures that the team efficiently addresses bugs, feature requests, and regressions that could affect millions of WordPress users globally.
For those unfamiliar, the Make WordPress Core team uses the Slack platform for real-time coordination and GitHub for ticket tracking. The #core and #core-privacy channels on Slack are particularly active during release cycles. Engaging in these chats and contributing to tickets is foundational for anyone looking to influence WordPress development.
What This Means for WordPress Users
For most WordPress site operators, the upcoming WordPress 7.0 release signifies an important upgrade window. As RC3 approaches, it is the last chance for developers, agencies, and hosts to test their themes, plugins, and custom integrations against the near-final codebase. Given the emphasis on RTC testing, users who rely on collaborative block editing will see improvements in reliability and responsiveness, provided their hosting environment supports these features well.
The auto-generation of Block Editor Handbook documentation is a positive signal for developers, especially those building and maintaining custom blocks. Better documentation means faster development cycles and fewer integration issues. Agencies managing multiple client sites can expect smoother transitions when adopting new block features or troubleshooting editor behavior.
From an ecosystem perspective, the active participation of major hosts like Bluehost, Kinsta, and GoDaddy underscores how hosting providers are vital collaborators in WordPress core evolution. Their testing efforts lead to more stable releases and better hosting-specific optimizations. This cooperation benefits agencies and site owners by reducing compatibility headaches post-upgrade.
Looking ahead, the open invitation to nominate discussion topics reflects the community-driven nature of WordPress development. Practitioners should consider actively contributing to dev chats or ticket queues to influence feature prioritization and ensure their specific needs are addressed.
Frequently Asked Questions
When will WordPress 7.0 be officially released?
The official release of WordPress 7.0 typically follows the Release Candidate phase, which in this case is scheduled to end shortly after RC3 on May 8. The final release usually happens within days after successful testing and issue resolution during this phase.
What is Real-Time Communication (RTC) testing and why does it matter?
RTC testing ensures that features enabling live collaboration and communication within WordPress—especially in the block editor—work reliably across different hosting platforms. It is critical for modern workflows that rely on synchronous editing and commenting functionalities.
How can contributors propose topics for the WordPress Core dev chat?
Contributors can propose discussion topics by leaving a comment on the official dev chat agenda post on Make WordPress Core, including a summary, relevant links, and the type of feedback they seek. Topics are then considered for inclusion during the live chat.
What should plugin and theme developers know about the block.json documentation proposal?
The proposal aims to automate parts of the Block Editor Handbook by extracting documentation from block.json files. Developers should prepare for potential changes in how block metadata is maintained and consider contributing feedback during discussions to shape the implementation.
