The WordPress Community has publicly released the first version of the project’s contributor dashboard, with data going back to 2021.
Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.
Program transcript
Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.
In this episode, you’ll find the information from March 2 to 8, 2026.
The WordPress contributor dashboard pilot is now publicly live. The tool makes it possible to visualize how project contributors participate, featuring a leveling system, activity tracking, and a data import framework.
The next phase has two proposals on the table. The first is allowing each team to define its own contributor profiles tailored to how that specific team operates. For example, the Polyglots team could create profiles by language, and the Support team could distinguish between users who answer in forums and those who are seeking help.
The second proposal is to automate contributor recognition when they reach key milestones, such as a first contribution or a new level on the scale. The idea is that the system could send congratulatory messages or even swag from the official store without anyone having to do it manually.
WordPress 7.0 Beta 3 is now available. This release includes more than 148 fixes and improvements over Beta 2, spread across both the editor and WordPress core. As with every beta, the focus is on stability and closing bugs before the final release.
The standout new feature in this beta is that the AI connectors screen now dynamically registers providers from the AI client registry, in addition to the three default providers. This adds more flexibility when integrating AI services into WordPress.
The planned release date for the final version of WordPress 7.0 is April 9, 2026.
WordPress 7.0 brings several important updates for developers, and this week a number of dev notes were published with the details: more control, more flexibility, and less reliance on JavaScript for things that can be handled server-side.
The most notable one for PHP developers is the ability to register blocks using PHP only, with no JavaScript required. Just add the autoRegister flag when calling register_block_type and provide a server-side render callback. The editor will automatically generate editing controls for the block’s attributes. It’s a significant simplification for blocks that only need server-side rendering, and the community has responded very positively.
On the mobile block editor side, WordPress 7.0 introduces customizable navigation overlays. Previously, tapping the hamburger menu on a mobile device displayed a fixed overlay with no customization options. Going forward, that overlay can be built with blocks from the Site Editor, including menus, logos, search bars, or any other content. Themes will also be able to ship their own predefined overlays. For now it only works in full-screen mode, with panel-style support coming in future releases.
For more technical developers, there are three additional highlights. The Interactivity API introduces a new watch() function that allows reacting to state changes programmatically without being bound to a DOM element, opening the door to use cases like navigation analytics or cross-store synchronization. The DataViews and DataForm components, used internally in the editor to display lists and forms, receive improvements including a new activity-style layout, improved data grouping, and new validation rules. And lastly, there is a new breadcrumb block that can be placed once in a theme and updates automatically based on the site’s navigation hierarchy, with PHP filters so developers can customize which taxonomies and terms appear in the trail.
The artificial intelligence team has had a busy few weeks. With WordPress 7.0 on the horizon, efforts are focused on three fronts: the new AI provider connection screen, the AI Experiments plugin, and the MCP adapter.
The new connectors screen, shipping with WordPress 7.0, aims to make connecting to AI providers — Google, OpenAI, and Anthropic — as straightforward as possible, with a single button and an API key. It will also include an experimental API so third-party providers can register their own connectors, avoiding a fragmented experience. Along those lines, official plugins are now available for each of those three providers, and a plugin for Ollama — which enables the use of local models — is also in the works.
The AI Experiments plugin has released version 0.4. The highlights include image generation from the block editor and from the Media Library, and a new content review feature that suggests accessibility, readability, grammar, and SEO improvements directly in the editor. The next version, 0.5, will add image editing, context-based auto-tagging, and onboarding flows for new WordPress 7.0 users.
Finally, the MCP adapter — which lets external AI assistants like Claude or ChatGPT interact with WordPress — is moving more slowly due to limited contributor availability, but remains a priority for upcoming sprints.
Another brief but significant post on Polyglots. Matt Mullenweg posed an open question to the team responsible for translating WordPress into every language in the world. The question is simple: what can we learn from platforms like Crowdin, which already integrate AI into their translation workflows? His argument is that human time is valuable and should be focused on what truly matters.
The community’s response came quickly, and it isn’t entirely optimistic. One team member pointed out that the real problem isn’t the tooling — it’s the quality of contributions. With or without AI, if inexperienced users flood the system with poor translations, editors are still left doing the same review and cleanup work.
It’s a conversation that many open source translation teams are having right now, and WordPress is no exception. AI can speed up the process, but human judgment, context, and cultural nuance remain hard to replace.
The Meta team has announced that WordPress.org has added Markdown support across virtually all of its sites. Any documentation page can now be retrieved in Markdown format by appending the output_format=md parameter to the URL, or by sending the Accept: text/markdown header in the HTTP request.
The primary driver is AI. Language models and AI agents constantly consume documentation, and HTML is full of structure and markup that adds no value to that process. Markdown is far cleaner and more efficient. A contributor in the comments provides a concrete example: fetching the block API documentation in HTML costs around 68,000 tokens, while in Markdown it comes in at roughly 11,000. A huge difference in both cost and speed.
The Community team has announced the retirement of the dedicated mentor program for WordPress Campus Connect. The program was created when the format was new and needed a dedicated group to define and document it. Now that it’s well established, maintaining it separately only added unnecessary overhead.
Going forward, support for Campus Connect event organizers will be handled within the general Event Supporters program — the same one that already supports WordCamps and other event formats. The goal is to streamline processes, eliminate duplication, and make better use of the existing team’s experience. Documentation has already been updated, and Campus Connect mentors who meet the requirements will be able to join as Event Supporters.
The Photo Directory has published its stats for March 2026, and the numbers are impressive. Over 33,000 published photos, contributed by nearly 2,900 collaborators from around the world, all under the CC0 license — free to use without restrictions.
Over the past two years the directory crossed two major milestones: 20,000 and 30,000 photos. Events like the WordPress Photo Festival, the Share Your Pride campaign, and Photo Walks at Contributor Days have been key drivers of that growth.
The directory is moderated by a team of 34 volunteers who review every photo before it goes live. New moderators are currently in the process of being onboarded.
And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.
Thanks for listening, and until the next episode!
Leave a Reply