Since 2010, WordPress has released a new default theme every year but one. Each default theme (though sometimes stylistically opinionated) is meant to provide a solid and flexible foundation that site owners can use to build out their new WordPress Continue reading Proposal: Retiring Older Default Themes
This post proposes adding the fetchpriority=”high” attribute to LCP images in WordPress core to enhance LCP performance. The proposal was created as a collaboration between members of the Core Performance Team. Context The fetchpriority attribute is a standard HTML attribute Continue reading Proposal for enhancing LCP image performance with the fetchpriority attribute in WordPress core
Overview This post outlines a proposal to add a script loading strategy enhancement to core’s existing Scripts API. The underlying goal of this effort is to make it easier for WordPress plugin and theme developers and core to use “modern” Continue reading Enhancing the Scripts API with a loading strategy
This call for feedback will be open until September 9th. Let’s introduce a reliable tool WordPress could use to adjust the HTML block markup. The current practice of using basic replacements seems fine at a first glance but is easy Continue reading A new system for simply and reliably updating HTML attributes
This is a follow-up post for the first WordPress 6.1 Planning Roundup published in this blog on June 23rd. The WordPress 6.1 Development Cycle page has been published with an updated timeline and release team and will be kept up Continue reading WordPress 6.1 Planning Roundup v2
Add a dominant color background to images Contributors to this doc: Paul Bearne, … Category: Proposals, ImagesTags: feature projects, performance, ImagesThis proposal seeks to integrate dominant color background for images into WordPress core, targeting the WordPress 6.1 release. ShareTweetSharePostSharePin It!
This proposal seeks to integrate two new Site Health checks for Persistent Object Cache and Full Page Cache into WordPress core, targeting the WordPress 6.1 release. Context Providing valuable recommendations for site owners is crucial to improving WordPress performance. These Continue reading Proposal: Persistent Object Cache and Full Page Cache Site Health Checks
The early months of this year saw a published proposal to create a Developer Blog on developers.wordpress.org. The blog is still an overall project goal for 2022. The next steps are to firm up some editorial guidelines and introduce the Continue reading Proposed Editorial Process for the new Developer Blog
This call for feedback will be open for the next two weeks until July 18th. I propose extending the useEntityRecord hook to support editing and deleting WordPress data. It should make building features and plugins on top of WordPress REST Continue reading Proposal: Better REST API handling in JavaScript
While it is a rare occurrence, updating plugins and themes can fail in such a way that leaves the old plugin/theme non-functional, and may leave users with a broken site. #51857 intends to add the ability for core to “rollback” to the Continue reading Rollback Feature: Testing Call to Action
The CSS rendered by the block editor needs improvement. The challenges are many and they have been documented. There are, nevertheless, several recurring themes: An overabundance of rendered inline style tags and duplicated CSS rules. For example, see #41434.Confusing or Continue reading Block editor styles: initiatives and goals
WordPress 6.1 will be the third major release of 2022. Following WordPress 6.0 Arturo, 6.1 will aim to refine those experiences found in Arturo and in 5.9 Joséphine [ref]. In preparation, this post includes target dates, features, and a call for the Continue reading WordPress 6.1 Planning Roundup
This post is a proposal to start weekly Editor Bug Scrubs in #core-editor the week of June 28th. The scrubs will have a singular focus on issues in the Gutenberg GitHub repository. If you have feedback, please comment by June Continue reading Proposal: Editor Weekly Bug Scrubs
This post is a follow up to last month’s Enabling WebP by default, which proposed a feature that would generate both JPEG and WebP images and output WebP sub-sized images in WordPress core. The post received quite a bit of Continue reading Follow-up on WebP by default proposal