Welcome!

The WordPress coreCore Core 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 bugbug A 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.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Joe McGill 12:43 am on July 23, 2024
Tags: 6-7 ( 28 ), dev chat ( 755 ), proposal ( 37 )

Proposal: Adjusting Dev Chat times for the 6.7 release

Background The weekly WordPress Dev Chat meeting is a tradition that dates back to the days when WordPress contributors primarily communicated via IRC. Since that time, these meetings have continued to serve as a regular time each week where contributors working on CoreCore Core is the set of software required to run WordPress. The Core […]

Héctor Prieto 3:24 pm on July 5, 2024
Tags: 6-7 ( 28 ), planning ( 30 )

WordPress 6.7 Planning Proposal & Call for Volunteers

With WordPress 6.6 almost ready, it’s time to start planning WordPress 6.7 so that the release leads can participate from the start of the release cycle. The timeline for the third release of 2024 takes into consideration WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They’re one of the places where the […]

bernhard-reiter 4:41 pm on June 24, 2024

Proposal: Block Variation Aliases

To provide an easy way for blockBlock 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 […]

Dennis Snell 12:53 pm on June 8, 2024

Proposal: Bits as dynamic tokens.

A proposal for starting to introduce Bits (dynamic tokens/placeholders) into WordPress. When Blocks came into the scene Shortcodes were largely abandoned, but Shortcodes had value. They had many problems, but they also had value. It wasn’t clear at the time how to bring them back without bringing back many of the problems they brought with […]

Pascal Birchler 7:39 pm on May 7, 2024
Tags: 6-6 ( 56 ), feature plugins ( 121 ), feature projects ( 51 ), i18n ( 35 ), merge-proposals ( 6 ), polyglots ( 6 ), preferred-languages ( 7 )

Merge Proposal: Preferred Languages

Almost 8 years ago the Preferred Languages feature project was kicked off in response to a feature requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each […]

Jon Surrell 3:26 pm on May 6, 2024
Tags: javascript ( 127 ), Script Loader ( 5 )

Proposal: Server to client data sharing for Script Modules

Abstract Script Modules were introduced in WordPress 6.5. wp_add_inline_script is often used to initialize or make data available to Scripts. Feedback on Script Modules and explorations suggest this would be a useful feature for Script Modules, but nothing exists at this time. This post will describe the problem in detail and propose a solution. The […]

Andy Fragen 5:21 pm on April 19, 2024
Tags: 6-6 ( 56 ), feature projects ( 51 ), feature-autoupdates ( 26 ), merge-proposals ( 6 ), rollback ( 3 )

Merge Proposal: Rollback Auto-Update

Background The biggest risk for a site owner when updating plugins is encountering a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher fatal error that crashes their website. While CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. […]

Héctor Prieto 9:12 pm on March 29, 2024
Tags: 6-6 ( 56 ), planning ( 30 )

WordPress 6.6 Planning Proposal & Call for Volunteers

With WordPress 6.5 almost ready, it’s time to start planning WordPress 6.6 so that the release leads can participate from the start of the release cycle. The timeline for the second release of 2024 takes into consideration WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They’re one of the places where the […]

Ari Stathopoulos 1:17 pm on February 1, 2024

Proposal: Implement a PHP autoloader in WordPress Core

Past discussions 8 years ago, a ticket was created in WordPress, suggesting a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher autoloader for WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. classes. In that ticketticket Created […]