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.
We’re catching up with these posts now, as they have not been posted in a while. Since the recent releases have been smaller in scope, this post combines updates from both the 20.4 (March 5) and 20.5 (March 20) releases.
Both versions introduce a collection of enhancements, 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. fixes, and improvements. These updates concentrate on refining the editor experience, improving 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). (https://en.wikipedia.org/wiki/Accessibility), and ensuring consistent design. Additionally, the releases incorporate under-the-hood updates focused on code quality and performance.
Persist the user’s ‘Show Template’ preference in the editor
Query LoopLoopThe Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_LoopBlockBlockBlock 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. now supports sorting posts by menu order
The create-block package now supports blocks manifest and relevant CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. APIs by default
Changelog
20.4 (5 March) – Highlights
Persist the user’s ‘Show Template’ preference in the editor
The editor now remembers the ‘Show Template’ preference set by the user and uses it as the default rendering mode. (69286)
Query Loop Block now supports sorting posts by menu order
The Query Loop block now lets users sort posts by their menu order, in both ascending and descending order, for post types that support it. (68781)
Changelog
Enhancements
Generate built CSSCSSCascading Style Sheets. file containing the adminadmin(and super admin) color theme CSS custom properties. (69128)
Post Editor
Editor: Conditionally enable the new default rendering mode for Pages. (69160)
Post Template Panel: Display popover on the left side of the 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.. (69134)
Block Library
Post Navigation Link: Enable all non-interactive formats. (69325)
Block Action: Implement cut functionality in block actions and settings menu. (68554)
Global Styles
Allow :Focus-visible pseudo-selector to be set in theme.jsonJSONJSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.. (68521)
Core Data: Allow ‘null’ as raw attribute value. (69257)
Dataviews: Fix alignment issue of “Title” column 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.. (68840)
Fix addQueryArgs and removeQueryArg on URLs with fragments. (69313)
Post formats: Make title and description human readable. (69275)
Site Editor: Fix back link from “Navigation” sub-menus in mobile web. (69192)
TextControl: Fix text direction for URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org and email fields in block editor for RTL languages. (68561)
Block Library
Fix: Extra top and bottom margin issue in Social Link block for classic theme below twenty twenty. (69100)
Make navigation block wavy underline more visible on dark backgrounds. (69004)
Template Part block: Guard against get_block_file_template returning null. (69309)
Video Block: Disable autoplay when video is not muted. (69232)
Post Editor
Editor: Add an extra check before enabling the new default rendering mode for Pages. (69209)
Editor: Avoid a ‘flash’ when rendering in ‘template-locked’ mode. (69173)
Editor: Revert bulk editing support for post actions. (69341)
Site Editor
Fix space on the left or right of the menu in mobile view. (69327)
Show pattern categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. step in navigation for mobile. (69206)
Site Hub: Navigate correctly in mobile view. (69157)
NumberControl: Fix invalidinvalidA resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid.HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. attributes for infinite bounds. (69033)
Colors
Format Library: Prevent the text and color picker from overlapping. (69169)
Format Library: Text-color popover width to fit sidebar. (68881)
Interactivity 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.
iAPI Router: Revert “Handle styles assets on region-based navigation”. (69222)
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 https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.
Fix typo for ‘ignore_sticky_posts’ REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”)
https://developer.wordpress.org/rest-api/ support. (69171)
Block Editor
Inserter: Hide drag-and-drop help text on mobile devices when previewing patterns. (69159)
Block hooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.
Close patterns modal on insertion and focus on inserted pattern. (68975)
Block Editor
Fix CSS classes for the post editor 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. body. (68481)
Performance
Interactivity API
Introduce withSyncEvent action wrapper utility and proxy event object whenever it is not used. (68097)
Documentation
Added Missing Double Quote in Number Control. (69207)
Added Missing Global Documentation in Query Total Block. (69233)
Fix typo incorrect article before “user interface”. (69168)
FontSizePicker: Fix FontSizePicker Storybook control type and improve documentation. (68936)
Update 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-in-the-block-editor.md – fix link. (62431)
ESLint: Improve lint regex for preventing “toggle” word usage in translationtranslationThe process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. ready functions. (68958)
Media Utils: Add tests for new error behavior. (69215)
Performance Tests: Update method for creating sample content. (69210)
The create-block package now supports blocks manifest and relevant Core APIs by default
Blocks created using the create-block package now include a block manifest file by default, making it easier to manage metadata and improving performance when working with multiple block types. (69446)
Pre-publish panel: Do not show suggestions for tags and categories if there are none.
The conditions that determine if the pre-publish panel should show suggestions to add categories or tags have been updated if no categories or tags are added. (69453)
Enhance create-block package to support blocks manifest and relevant Core APIs by default. (69446)
Remove trailing periods from Show or hide settings panel. (69356)
Site Editor: Make current theme and editor settings available to route area resolvers. (69299)
Block Library
Button Block: Add draft page creation capabilitycapabilityA 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).. (69368)
Query Total: Update the block color support settings. (69500)
Block Editor
BlockEditor: Resolve MediaReplaceFlow UIUIUser interface text inconsistency. (69546)
Comment Template: Use fallback when there’s an HTTPHTTPHTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. error. (69422)
Fix: Show the author and author name examples in the Stylebook. (69436)
Image block: Unwrap img element in editor. (68666)
Latest Posts: Make Latest Posts block consistent with sticky posts display. (69428)
Query Total: Prevent stricted type fatal errors on post per page. (69508)
Social Icons: Disable edit as HTML support. (69374)
Spacer: Revert height defaults to 100px if left unset. (69450)
SpacerControls: Default the height to 100px if left unset. (68819)
Table Of Contents: Include headings exclusively within the core/post-content block. (69366)
Site Editor
Classic themes: Prevent access to parts of the Site Editor. (69473)
Hide admin bar in classic theme site preview. (69514)
Prevent access to the Design/Styles screen from classic themes without StyleBook support. (69377)
Fix template lookup preloading for non-draft pages. (69400)
Experiments
Added Missing Trailing periods in Experiment Settings Page. (69395)
Documentation
Docs/update reference to JSJSJavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. build setup 404 in scripts README, fix absolute links. (69495)
Fix: Update invalid JSON Schema link in README.md. (69505)
Update documentation about wp-scripts build-blocks-manifest in relation to new WordPress 6.8 function. (69445)
Code Quality
Alignment note with WordPress report 62426. (69519)
Skip failing post preview end-to-end tests. (69429)
Template UI mu-plugin: Run filterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. after the setup_theme action. (69542)
Various
Plugin
Update hierarchical data compat directory. (69550)
First-time contributors
The following PRs were merged by first-time contributors:
@Anuj-Rathore24: Fix: Update invalid JSON Schema link in README.md. (69505)
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. Europe is today!
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 should be announced soon. Follow #6-8-release-leads for updates.
As a follow-up to this post, he asked the following to be discussed:
After a couple of weeks, I’m almost done on reviewing the Workflow Keywords sequence. I only need some extra info in the committing part as is the part I’m less knowledgeable, so I would need some committers to help me out on the review
[I] need committers to help with the revision of the Workflow Keywords (specially the committercommitterA 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. and 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. part where I have more doubts). First I’m willing to publish an article explaining the new ideas with the first revision of the revised diagram and it could serve as an attention call for anyone willing to make an opinion or add anything else before the final proposal.
Some discussion happened in the Core Slack channel about this post/proposal.
To sum-up, some committers pointed out that:
@jorbin: This post seems to make the assumption that just because there is 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. and the patch has no flaws, that it should be committed, but if something should be committed isn’t just a question of if there is a patch ready, it’s also things such as: Does this fit within the current priorities? Is this going to cause issues with future backwards compatibility? Are there alternative solutions that haven’t been considered that should be? How risky is this to commit? What other teams would be affected by this change? Have they been given a chance to chime in?
@desrosj: The crux of the post seems to suggest we can’t create a report for tickets that need a code review with the current keywords. Wouldn’t a report that shows tickets with has-testing and has-patch but does not have commit accomplish the same thing?
@sirlouen pointed out that the post is not completely assuming that every patch perfectly reviewed must be committed, but every patch perfectly reviewed should be considered by committers with more priority than patches from scratch.
The discussion then switched to patches that are reviewed and tested, and waiting for a committer review and commit:
@jorbin: Bringing those tickets up during 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. scrubs can be a great way to get attention on them, [but] just because it fits [someone’s] definition of 100% baked doesn’t mean that a committer is going to agree.
@audrasjb: The best way to help these tickets is to ask to move them into the current milestone.
@jorbin: There are about 75 bug gardenersBug GardenerA contributor who has been given advanced privileges in Trac. who can modify milestones in addition to all of the committers. In addition, there is nothing that would prevent at the end of the bug scrub a post along the lines of: “After this scrub, we think that the following tickets should be included in 6.8.2 and the following ones in 6.9”. Once someone has demonstrated enough good judgement, they will likely be given bug gardenerBug GardenerA contributor who has been given advanced privileges in Trac. status so that they can do it themselves.
@justlevine wanted to bring attention to ticketticketCreated for both bug reports and feature development on the bug tracker.#61175: “Beyond the usual i could use a bit of help from people better skilled at WP CI/CD (PHPStan passes locally, but isn’t discovering certain symbols when run on CI)”. See the related GitHub PR.
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 CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 and 6.8.3 will be announced soon.
Discussions 💬
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core 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.
Proposal concerning Core TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. workflow keywords
He asked the following: “Need committers to help with the revision of the Workflow Keywords (specially the committercommitterA 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. and 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. part where I have more doubts). First I’m willing to publish an article explaining the new ideas with the first revision of the revised diagram and it could serve as an attention call for anyone willing to make an opinion or add anything else before the final proposal.”
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.
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. Europe is one week away!
@benjamin_zekavica facilitated the organization of the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team tables. If you plan to attend, check the Core Team at WCEU 25 | Contributor Day article.
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/ 20.9 is now available
The new version of the Gutenberg 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 https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. is now available in our plugin directory.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The Core Team is putting together a squad for future minor releases.
In preparation for the WordCamp Europe 2025 Contributor Day, @benjamin_zekavica called for important Core 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. tickets to be submitted for planning.
@realloc will lead the MultisitemultisiteUsed to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site table and is working with maintainers to identify good first bugs.
Core committers are encouraged to actively participate and make at least one commit — with @mamaduka offering remote support.
Where do bugs go if they are introduced in a point releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.?
There was a discussion about how to handle bugs found during a point release. Usually, these bugs should be included in the next point release, especially if there is 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. or if it is a regressionregressionA software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5..
Whether a fix is backported depends on factors such as the bug’s age, severityseverityThe seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs., and the risk of the fix. Since clear guidelines are lacking, decisions are made case by case by release leads. More documentation on this process was recommended.
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.
Announcements 📢
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. Europe is one week away 🤯 @benjamin_zekavica facilitated the organization of the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team tables. If you plan to attend (please do!), check the Core Team at WCEU 25 | Contributor Day article.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The Core Team is putting together a squad for future minor releases. And yes, more volunteers are welcome.
Next 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/ version: 20.9
Gutenberg 20.9 is scheduled for release on Wednesday, May 28, 2025. So it might be out by the time we start dev chat 💪
Discussions 💬
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core 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.
@benjamin_zekavica posted about WordCamp Europe Contributor Day in Basel. Do you have ahigher-priority ticket dear to your heart? This is a great time to work on it and shepherd it to resolution. Please add them to the WCEU prep post as commentsso the table leads and supporters can prepare.
Where do bugs go if they are introduced in a point releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.?
@sirlouen asked: Should bugs introduced during a point release cycle be moved into the next point release or the next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.? This item is not documented. Since we are moving to a different release cadence, it could use some clarity.
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.
We’re so excited—next week, on June 5th, we’re heading to Basel for WordCamp Europe! 🎉 The event kicks off with Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/, a fantastic opportunity to come together and help shape the future of WordPress.
New contributors are especially welcome!
Whether you write code or not, everyone can get involved with the WordPress CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. Wondering how? It’s easier than you think.
We’ll have several tables dedicated to the Core Team, and we’ve brought together a fantastic group of experienced contributors to guide and support you.
⚠️ Before the event, we kindly ask you to prepare everything at home.
Please prepare your setup at home: Install all necessary software, clone the repositories, and download Node.js packages and all software in advance! To avoid slowdowns or connection issues, we encourage everyone to limit heavy downloads during the event.
New to contributing? No problem! We have experienced mentors at each table who are happy to help you get started.
Bring your charger and adapters It’s going to be a full day – make sure your devices stay powered!
Join the conversation Don’t be shy! Ask questions, share ideas, and get to know fellow contributors.
Prepare at home 🏡
Register for a WordPress.orgWordPress.orgThe 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/ profile and the WordPress.org Slack instance
The large majority of the communication around contributing to the WordPress open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. projects happens on WordPress.org or in the WordPress Slack instance. Your first step should be to register for both in that order.
To get started right away working with us on WordPress and the 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/ Editor, please make sure your technical setup is ready. You’ll need a laptop and access to all the accounts we’ve linked for you above.
WordPress Core
If you’d like to contribute directly to WordPress Core, you should start by forking the WordPress Development Repository. Then, make your changes in your own 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".. Once ready, submit a pull request referencing the related ticketticketCreated for both bug reports and feature development on the bug tracker. number. The system will automatically detect the number and link your 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. to the corresponding ticket.
To contribute to the Gutenberg Editor, you don’t necessarily need Docker. Simply fork the Gutenberg repository, make your changes in a new branch, and submit a pull request. The only requirement is a recent version of Node.js.
Want to contribute to the future of WordPress? Whether you’re into fixing bugs or creating new features for the Gutenberg editor – your skills are needed! Learn how to get started and explore all the ways you can make an impact – more information available at the link below.
GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ Repositories
These links are specially curated for new contributors who want to help with the WordPress Core or the Gutenberg Editor 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 https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.. They provide filtered resources and guidance to get you started smoothly and make meaningful contributions. Welcome aboard!
Want to make a real impact on WordPress? Help improve the platform by testing new features and catching bugs before they go live. Learn how you can get involved and support the community – all the details are in the link below.
Great documentation helps users and contributors alike. Whether you enjoy writing guides, updating existing content, or translating for a global community – your input is essential.
No problem – you are welcome to ask your questions in the #contributor-day channel as well as in the #core channel. @mikachan and @audrasjb will be available throughout the day to assist you with any inquiries.
Sign up for our Contributor Day stats!
We want to make Contributor Day even better for everyone — and we need your help! Please take a moment to fill out our quick form to share who participated, which tickets you worked on, and whether you’re new or a returning contributor.
Rest assured, the data you provide in Google Forms will be deleted after the event. The summarized results will be published as a recap post on the Core Blogblog(versus network, site) — with contributors properly credited and tagged.
It only takes a few minutes — but makes a big difference! The submission is now closed. ⚠️
On June 5, 2025, the Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ at 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. Europe will take place in Basel, and the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is looking for experienced volunteers to support onsite.
Co-Lead (preferably a Core CommittercommitterA 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.) | One position available:
You are a Core Committer or very experienced with the WordPress Core project
You have helped lead or support a Contributor Day before
You can assist with technical questions and confidently guide new contributors through tools like TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/
You communicate clearly and feel comfortable using English
Supporter | Two positions available:
You are familiar with the Core Team workflows
You help new contributors with setup, explain tools, and assist with initial tasks
You communicate clearly and feel comfortable using English
Please apply by leaving a comment under this post by May 29, 2025. We look forward to your support—let’s make this Contributor Day a success together! 🥳
There are no major announcements from the past week.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases.
Next 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/ version: 20.9
Gutenberg 20.9 is scheduled for release on Wednesday, May 28, 2025.
Discussion 💬
Refreshing Workflow Documentation
@SirLouen suggested updating the TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. workflow keyword documentation, noting that some terms are outdated, misused, or conflicting. He plans to draft a revised version to provide clearer guidance for contributors and aims to publish it on the blogblog(versus network, site). The goal is to support future discussion and improve overall understanding of keyword use.
Improving the Local Development Environment
The current local development environment for WordPress is minimal and does not include all tools needed for comprehensive testing. Since different approaches are used, the documentation should be updated and improved to reflect the latest state.
Reducing Redundant Test Reports
@krupajnanda suggests limiting the number of test reports on simple tickets (e.g., UIUIUser interface/UXUXUser experience, 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). (https://en.wikipedia.org/wiki/Accessibility)) to around 5 and adding a message to guide contributors to more important tickets, to reduce redundant testing. @jorbin and others agree but emphasize that this shouldn’t be automated, as a person needs to verify the validity of test reports.
Additionally, once enough test reports are received, the needs-testing label should be removed to focus efforts on tickets still requiring testing.
Open floor 🎙️
Review Needed: Unicode Email Addresses
@agulbra is requesting a review for ticketticketCreated for both bug reports and feature development on the bug tracker.#31992. The code was written last year, but it’s now ready to be merged since PHPMailer has released the required dependencies. @ironprogrammer has already reviewed it and suggested asking for further feedback here. It would be great if someone could take a look. Thanks!
Call for Core Bug Tickets for the 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. Europe 2025 | Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/
@benjamin_zekavica mentioned that preparation for the WordCamp Europe Contributor Day in Basel should begin. To support this, suitable tickets need to be collected. If anyone finds higher-priority tickets that could be worked on during the event, they are encouraged to add them as comments in this article. This would help streamline the preparation process.
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.
Announcements 📢
There are no major announcements from the past week.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases.
Next 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/ version: 20.9
Gutenberg 20.9 is scheduled for release on Wednesday, May 28, 2025.
Discussions 💬
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core 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.
Refreshing Workflow Documentation
@sirlouen suggests updating the workflow keyword documentation, as some terms are outdated, misused, or conflicting. He proposes drafting a clearer version to publish on the blogblog(versus network, site) for better contributor guidance.
Improving the Local Development Environment
The current WordPress development setup makes certain testing tasks (like email testing) harder than necessary. @sirlouen recommends adding helpful tools to make the environment more complete and testing more efficient.
Reducing Redundant Test Reports
@krupajnanda points out that some simple tickets, especially UIUIUser interface/UXUXUser experience and 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). (https://en.wikipedia.org/wiki/Accessibility) ones, receive too many test reports, while more complex tickets are often ignored. She proposes setting a soft limit (e.g. 5 reports) and adding a message to guide contributors to other important tickets.
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.
A Month in CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. – April 2025
In case you haven’t seen it yet, here’s a statistical report from the month of April published by the Core Team. You can find more details in the article.
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/ 20.8 is now available
The new version of the Gutenberg 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 https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. is now available in our plugin directory.
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). (https://en.wikipedia.org/wiki/Accessibility) Focused Bug Scrub
@jorbin is hosting an Accessibility-Focused Bug Scrub tomorrow at 15:30 UTC in #core to help move tickets forward. More detailed information you can find here.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The Core Team need to set up a release squad, a plan/scope and a schedule for 6.8.2 (and beyond)
Discussion 💬
Call for Topics for the Dev Chat agenda
@sirlouen suggested to publish the “Call for Topics for the Dev Chat agenda” earlier to give contributors more time to suggest topics. @benjamin_zekavica, speaking for the Team Reps, noted that while it can be challenging due to time constraints, they will aim to publish the Call for agenda 1–2 days in advance and update it as needed.
He supports the idea of raising topics early and will discuss improvements with the other reps. Further updates on this will follow.
PHPCSPHP Code SnifferPHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. for Class FTPFTPFTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients files
In the discussion on ticketticketCreated for both bug reports and feature development on the bug tracker.#63436, it was agreed that PHPCS should not be applied to the FTP class files. These files come from an old external library, and applying coding standards would only make sense if WordPress fully adopts the code. There was also agreement on the need for clearer rules and improved documentation.
You must be logged in to post a comment.