This post summarizes key discussions from the most recent core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committer A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. meeting held with project leadership. As with previous check-ins, the goal is to align on key initiatives, gather feedback, and clarify next steps for the WordPress project.
Note: This meeting followed the Chatham House Rule.
WordPress 6.9 Release Planning
Discussion focused on priorities and scope for a 6.9 release in 2025 (pending alignment on final schedule from @annezazu @jeffpaul). The group explored potential directions for 6.9, including:
- Completing and stabilizing in-progress features such as:
- Design tools and writing experience improvements
- Block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. bindings API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., HTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. API, and Interactivity API
- Enhancements to the command palette
- Early promotion of a canonical AI-related plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, focused on foundational APIs (e.g., the Abilities API), rather than bundling AI functionality directly into core.
- Continued iteration on infrastructure improvements and smaller UX User experience wins.
There was broad agreement to continue discussion asynchronously and collaboratively shape a public 6.9 roadmap post.
Admin (and super admin) Redesign / “MP7” Exploration
A significant portion of the meeting centered around evolving wp-admin. There was alignment on the need for wider user testing through the Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ plugin ecosystem, though implementation details are still to be worked out.
Key points:
- There’s early alignment to test the refresh using the Gutenberg plugin (potentially as an opt-in experiment or a separate “MP7-style” plugin).
- Using a larger testing base was favored over starting a new plugin from scratch.
- Additional strategies discussed included:
- Feature callouts in slash.news
- Outreach via WordCamps and testing cohorts
- Reviving structured usability testing programs
The redesign discussion also surfaced interest in expanding collaboration tools like block-level commenting and async workflows, some of which are already underway in Gutenberg.
Follow-up conversation is planned in #core-editor to shape implementation plans and clarify MVPs.
Plugin Classifications & Maintenance
The group discussed distinctions between canonical and feature plugins, and how those classifications inform expectations and maintenance.
Key takeaways:
- Feature plugins are exploratory, short-term, and may eventually graduate into canonical status. But that’s not a guarantee nor the expectation.
- Canonical plugins are officially supported, listed as authored by WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/, and expected to have a directly responsible individual (DRI Directly Responsible Individual - the people who are taking ownership or responsibility for a particular project or feature.).
- Two additional potential types were suggested:
- Experimental plugins: can still graduate to feature or canonical status if they prove valuable.
- Support plugins (ie. jQuery Migrate Helper and Memory Bump): these are temporary support focused tools addressing specific issues and may be retired when no longer needed.
Improving discoverability of these plugin types within the directory was raised as a longer-term goal, along with contextual activation within wp-admin (e.g., activating collaborative editing directly from the editor UI User interface), and better recognizing the contributors on the plugin pages in the directory.
Maintenance & Version Support Policy
The group discussed the challenges of maintaining older versions of WordPress, particularly as support is officially dropped for 4.1-4.6 later this month.
Discussion began around when it might be appropriate to trim another group of old versions. The next road block will be dropping support for 4.9.
- Its current usage (~1.5%) is roughly 0.5% higher than every other version < 5.8
- A number of sites are likely intentionally avoiding the block editor
Points raised:
- Consider aiming for a general sub-5% usage threshold before discussing deprecation.
- Support drop timing should be coordinated across PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher/MySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. minimums, database health efforts, and comms with hosts.
- Site Health visibility remains a pain point for users who don’t know their host/provider more visibility may be needed.
- A yearly support-drop cadence could help standardize communication and reduce confusion after catching up.
The security team will continue this conversation with the goal of bringing forward a clear and thoughtful resolution.
Data Liberation & Importers
There was strong interest in reviving data migration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. tooling as a strategic opportunity to support user freedom and growth.
Points discussed:
- Existing importers focus on legacy platforms (e.g., Movable Type) and are often unmaintained or broken.
- The importers are often the first plugin someone installs and can make or break whether the user stays with WordPress.
- Interest in adding support for platforms like Substack, Squarespace, Wix, and Framer.
- Approaches include canonical plugins, browser extensions, and API-based importers.
- Pairing tools with strong documentation and walkthroughs was emphasized as an effective early strategy.
- This work may also help identify feature gaps in WordPress itself.
The conversation included exploring how importers can influence core improvements, similar to how early Movable Type importers shaped WordPress functionality.
Next steps include creating a shared issue tracker or discussion hub to catalog opportunities and begin prototyping with the North Star metric being the number of sites successfully migrated.
Future of Default Themes
The group revisited the idea of default themes and whether a TT6 release is appropriate this year. There was not a consensus decision, but the following points were raised:
- Several contributors questioned whether a new theme was necessary this year, citing:
- Ongoing maintenance burdens for prior themes
- The opportunity to promote patterns, style variations, and starter templates instead
- The need to clarify the vision for how the various tools should work together holistically (pattern directory, templates, font library, block plugins, etc.)
- Others noted that default themes are a valuable way to:
- Showcase new features
- Support learning and education efforts
- Inspire community creativity
While no decision was finalized, there was clear interest in re-evaluating the purpose of default themes and exploring new ways to demonstrate front-end capabilities A capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). across the project.
Campus Programs: Credits & Connect
There was a concern shared about the project potentially being overwhelmed with new contributors due to the Campus Credit pilot program. An update on the Campus Credits pilot was given with the University of Pisa:
- The pilot includes 25–40 linguistics students contributing this fall.
- A public announcement is planned soon.
- Onboarding, mentorship, and scoping work are underway to ensure contributors have a positive and productive experience.
- Early feedback from Pisa has been positive, and expansion into other departments is being requested.
This pilot is distinct from Campus Connect, which is a separate, events-based program already in motion in multiple regions.
Further planning will take place in public to ensure contributors, mentors, and community members have clear expectations and support.
Additional Topics
- Theme support forums (particularly for 2025) are understaffed. Need to explore ways to improve coverage, AI-assisted support and better contributor onboarding were mentioned as possibilities.
- Several participants emphasized the need for a structured user testing program, similar to the original outreach program, to improve onboarding and usability insights.
- Interest in future tooling like WapuGPT, an LLM-powered support assistant trained on WordPress docs, was raised as a long-term idea.
- Admin banners and notices were flagged for discussion: fake dismissals, non-dismissible notices, and UX fatigue are causing frustration for users and contributors. Further UX guidance may be needed.
Next Steps / Follow-up
- Kick off admin redesign technical discussions in #core-editor.
- Share and collaborate on the 6.9 roadmap draft. (cc @annezazu)
- Draft plugin classification criteria and expectations for canonical, feature, experimental, and support plugins.
- Continue public discussion on importer strategy and prioritize modern platforms.
- Explore policy and timing for ending support for WordPress 4.7 and beyond.
- Begin scoping something theme related to showcase in 6.8 (a “pattern bundle” or style showcase).
- Re-engage with prior explorations from the Notifications API and WP Notify efforts to assess paths forward for more consistent, dismissible admin notices and improved admin interactions
Thanks to everyone who participated. These check-ins aim to improve visibility and encourage collaboration across WordPress Core and will continue at a roughly once per quarter cadence. Discussion will continue in Make Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. posts, and upcoming roadmap proposals.
Props: @jeffpaul @annezazu @desrosj
You must be logged in to post a comment.