Title: 2023 – Make WordPress Core --- # Yearly Archives: 2023 [ ](https://profiles.wordpress.org/webcommsat/) [Abha Thakor](https://profiles.wordpress.org/webcommsat/) 10:24 pm _on_ December 28, 2023 Tags: [make.wordpress.org/project ( 18 )](https://make.wordpress.org/core/tag/make-wordpress-org-project/), [p2-xpost ( 210 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: WordPress End of Year Celebrations!](https://make.wordpress.org/core/2023/12/28/xpost-wordpress-end-of-year-celebrations/)󠁿 X-comment from [+make.wordpress.org/project](https://make.wordpress.org/project/): Comment on [WordPress End of Year Celebrations!](https://make.wordpress.org/project/2023/12/22/wordpress-end-of-year-celebrations/#comment-498) [ ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/) 9:55 pm _on_ December 22, 2023 Tags: [6-5 ( 76 )](https://make.wordpress.org/core/tag/6-5/), [6-6 ( 57 )](https://make.wordpress.org/core/tag/6-6/), [6-7 ( 75 )](https://make.wordpress.org/core/tag/6-7/), [planning ( 36 )](https://make.wordpress.org/core/tag/planning/)    # 󠀁[Call to action: 2024 major releases call for volunteers](https://make.wordpress.org/core/2023/12/22/call-to-action-2024-major-releases-call-for-volunteers/)󠁿 Based on the previous [proposal around the 2024 Major Release Timing](https://make.wordpress.org/core/2023/11/06/proposal-2024-major-release-timing/), it’s time to call for volunteers. Since there are release dates for the upcoming three releases, let’s formalize the 6.5 release squad and begin shaping the other two squads of the year ahead. Knowing who will participate in 6.6 and 6.7 in advance will let folks shadow previous releases and allow for better preparation and mentoring. ## WordPress 6.5 Schedule | Milestone | Date | | Alpha (trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. open for 6.5 release) | October 17, 2023 | | BetaBeta A 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. 1 | February 13, 2024 | | Beta 2 | February 20, 2024 | | Beta 3 | February 27, 2024 | | Release Candidaterelease candidate One 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)](https://make.wordpress.org/core/2023/?output_format=md#alpha-beta). 1 | March 5, 2024 | | Release Candidate 2 | March 12, 2024 | | Release Candidate 3 | March 19, 2024 | | Dry Run | March 25, 2024 | | WordPress 6.5 General Release | March 26, 2024 | ## WordPress 6.5 call for volunteers The [WordPress 6.5](https://make.wordpress.org/core/6-5/) release squad is still looking for diverse volunteers in every role. Ultimately, each volunteer will **only participate in a single role**, and each role aims to have two to three people; past releases have shown that while it’s beneficial to share the responsibility with other people, there are diminishing returns when there are too many folks involved. The following names are **not assignments**, only the summary of folks who have volunteered so far: * Release Coordinator: Héctor Prieto * CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead: Pascal Birchler* * Editor Tech Lead:  Dave Smith * Core Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead: Rajin Sharwar * Editor Triage Lead: Anne McCarthy* * Documentation Lead: * Marketing & Communications Lead: * Test Lead: Anne McCarthy*, Vipul Ghori, Patrick * Design Lead: * Performance Lead: Pascal Birchler* _(*) People who have volunteered for more than one role. Their participation will be adjusted to a single focus depending on the release squad’s needs._ **As of today, every role has openings; if you are interested in participating, please leave a comment below by January 12th.** ## WordPress 6.6 and 6.7 timeline These are the updated release dates for WordPress 6.6 and 6.7: * WordPress 6.6 Beta 1 is planned for June 4, and the general release for July 16 (no changes since the original proposal). * WordPress 6.7 Beta 1 is planned for October 1, and the general release for November 12. The dates have been pushed one week to consider [WordCamp US 2024](https://us.wordcamp.org/2024/)( September 17-20) and give some breathing room in between. Please bear in mind these dates are not fixed and might change as the year progresses. This early planning aims to provide clarity around the release timeline and shape the upcoming release squads in advance. ## WordPress 6.6 and 6.7 call for volunteers Since we have a rough idea of the WordPress 6.6 and 6.7 dates, let’s start shaping their release squads. Please volunteer in the comments below if you would like to participate in these releases, being mindful of your availability throughout the year before committing. Needless to say, if your availability changes later due to unforeseen circumstances, adjustments to the squads can be made. Thanks to this early planning, we will experiment with **starting the next default theme as early as 6.6**, so if you are interested in working on the successor of the amazing Twenty Twenty-Four, please raise your hand in the comments. --- _Thanks to [@cbringmann](https://profiles.wordpress.org/cbringmann/) and [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) for reviewing this post._ [#planning](https://make.wordpress.org/core/tag/planning/) [#6-5](https://make.wordpress.org/core/tag/6-5/) [#6-6](https://make.wordpress.org/core/tag/6-6/) [#6-7](https://make.wordpress.org/core/tag/6-7/) [ ](https://profiles.wordpress.org/webcommsat/) [Abha Thakor](https://profiles.wordpress.org/webcommsat/) 10:05 pm _on_ December 20, 2023 Tags: [dev chat ( 914 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 972 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev Chat seasonal break, highlighted posts December 2023](https://make.wordpress.org/core/2023/12/20/dev-chat-seasonal-break-highlighted-posts-december-2023/)󠁿 (Updated post Dec 23, 2023 with volunteer call for 2024 releases; Dec 28, to add‘ WordPress end of year post’) It was agreed at the Dev Chat that there would be a break for a few weeks, from and including December 20, 2023, and restarting on January 10, 2024. During this period, I will be publishing a list of new posts and reminders that come up in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. If there are any others, please do add them in the comments. ## Highlighted posts [End of Year WordPress celebration](https://make.wordpress.org/project/2023/12/22/wordpress-end-of-year-celebrations/) post from [@chanthaboune](https://profiles.wordpress.org/chanthaboune/), with some of the highlights by Make team. [Volunteer call for 2024 WordPress releases](https://make.wordpress.org/core/2023/12/22/call-to-action-2024-major-releases-call-for-volunteers/)( December 22, 2023) – thanks to [@priethor](https://profiles.wordpress.org/priethor/) for the update, which also includes the proposed schedule for releases. If you are interested, please leave a comment on that post by January 12, 2024. [What’s new in Gutenberg 17.3?](https://make.wordpress.org/core/2023/12/20/whats-new-in-gutenberg-17-3-20-december/)( December 20, 2023). GutenbergGutenberg 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/](https://wordpress.org/gutenberg/) 17.3 has been released and is [available for download](https://wordpress.org/plugins/gutenberg/)! This update incorporates numerous enhancements, 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. fixes, improvements in performance and accessibilityAccessibility Accessibility (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 ongoing development of Phase 3 features. [Overflow questions from the State of the Word 2023](https://make.wordpress.org/project/2023/12/12/overflow-questions-from-state-of-the-word-2023/) post. [Reminder: core team rep nominations and elections](https://make.wordpress.org/core/2023/12/04/nominations-for-core-team-reps-2024-edition/). Note: The nomination period was extended until January 12, 2024 at 23:59 UTC, to give more time for Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. [https://core.trac.wordpress.org](https://core.trac.wordpress.org) to consider and nominate other contributors and/or themselves. Proposal to [add company icons to sponsored contributors](https://make.wordpress.org/core/2023/12/19/proposal-add-company-icons-to-sponsored-contributors-on-about-page/) [@pbiron](https://profiles.wordpress.org/pbiron/) is suggesting this approach to encourage companies to support WordPress more and so user can see where the support is coming from. [Updating WordPress to use more modern versions of Node.js/npm: Part 2](https://make.wordpress.org/core/2023/12/20/updating-wordpress-to-use-more-modern-versions-of-node-js-npm-2/) [@desrosj](https://profiles.wordpress.org/desrosj/) sets out the actions contributors to core will need to take to upgrade the version of Node.js installed locally to be able to contribute to WordPress through `wordpress-develop` or `WordPress/Gutenberg`. [WordPress performance impact on Core Web Vitals in 2023](https://make.wordpress.org/core/2023/12/19/wordpress-performance-impact-on-core-web-vitals-in-2023/), December 19, 2023 From the Developer Blogblog (versus network, site), [Extending plugins using custom Slot Fills](https://developer.wordpress.org/news/2023/12/22/extending-plugins-using-custom-slotfills/). [Other new posts on the Blog](https://developer.wordpress.org/news/). Call for volunteers for the Dev Blog – posts in need of writers and reviewers are listed in the last [Dev Blog editorial meeting from December 14, 2023](https://make.wordpress.org/core/2023/12/16/dev-blog-editorial-meeting-summary-december-14-2023/). For information, in the [#fse-outreach-experiment](https://wordpress.slack.com/archives/C015GUFFC00/p1702356362566639), there was an opportunity for developers to share their theme building workflow with contributors working on theme tooling. Similar opportunities will be promoted in the future. Join the channel to keep up to date with developments. ## Bug scrubs and tickets [Last bug scrub link in Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1703012756568529) New bug scrubs will be added to the Bug Scrub schedule for 6.5. Could you help run a scrub or have tickets you would like to progress? [Find out more about bug gardening in the Core Handbook](https://make.wordpress.org/core/handbook/testing/bug-gardening/). [@pbiron](https://profiles.wordpress.org/pbiron/) would like people to carry out unit tests that he is adding for TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets. By mid-December, there were nearly 100 ready to go. Pick up the testing challenge by following this [Trac query](https://core.trac.wordpress.org/query?status=!closed&reporter=pbearne) ## Update from core-editor Props to [@annezazu](https://profiles.wordpress.org/annezazu/) for preparing this update. ### **For information** * [High priority labeled items for the Gutenberg repo](https://wordpress.slack.com/archives/C02QB2JS7/p1702996696603749) has been triaged with an open convo around whether to add the label to 6.5 priority items to help improve project organization and communication. * [New overview issue: Pattern / Template Part Unification – the technical challenges](https://github.com/WordPress/gutenberg/issues/57011#top) ### 6.5 related updates * Data Views: check out an [early prototype of inline editing](https://github.com/WordPress/gutenberg/pull/56945) to explore what will be needed for a future APIAPI 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., [add list layout to templates](https://github.com/WordPress/gutenberg/pull/57014#top) PR merged, [align filter implementations](https://github.com/WordPress/gutenberg/pull/57059#top) PR merged, new issue for [show total count in menu item](https://github.com/WordPress/gutenberg/issues/57072#top), and new issue for [implement Kanban layout](https://github.com/WordPress/gutenberg/issues/57024#top). * Font Library: [add global configuration variables for font directory](https://github.com/WordPress/gutenberg/pull/57044#top), which enables the option to set a custom directory as font directory. * Interactivity API: [check out on experiment with Comments block: client-side form submission](https://github.com/WordPress/gutenberg/pull/53737#top). * Design tools: early draft PR to [add backgroundSize feature with implicit repeating backgrounds](https://github.com/WordPress/gutenberg/pull/57005#top) to add more functionality to the Group 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 consistent API and user experience.’s background image support that was added in 6.4. * Command Palette: please share feedback around whether it would be helpful to  [enable the command palette feature everywhere in WordPress](https://github.com/WordPress/gutenberg/pull/54515). * Navigation: Check out the latest prototype for being able to [customize the navigation overlay with a template part](https://github.com/WordPress/gutenberg/issues/43852#issuecomment-1858549451), enabling a separate menu experience for mobile. * Performance: loads of recent performance improvements [particularly from ellatrix](https://github.com/WordPress/gutenberg/issues?q=label%3A%22%5BType%5D+Performance%22+is%3Aclosed+author%3Aellatrix)( too many to link to) with [more to come ](https://github.com/WordPress/gutenberg/issues?q=label%3A%22%5BType%5D+Performance%22+author%3Aellatrix+is%3Aopen) that should greatly improve both the post and site editor experience. Please share feedback as these fixes and enhancements land! * RevisionsRevisions The 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.: the PR to [integrate style book](https://github.com/WordPress/gutenberg/pull/56800#top) is close to landing, the PR to [show change summary on selected item](https://github.com/WordPress/gutenberg/pull/56577#top) landed for GB 17.3, and the PR to [extend support to other post types for Core data revisions](https://github.com/WordPress/gutenberg/pull/56353#top) landed for GB 17.2. * Pattern overrides (new working name for the previous partial sync patterns): the UXUX User experience of the experience is being established and refined with the PR to [edit source pattern in focus mode in post editor](https://github.com/WordPress/gutenberg/pull/57036#top). * Work continues to align page editing features in Site and Post Editor with [the latest update here](https://github.com/WordPress/gutenberg/issues/52632#issuecomment-1860096206). * [HTML API: Backport updates from Core](https://github.com/WordPress/gutenberg/pull/57022#top) and [HTML API: Add support for H1-H6 elements in the HTML Processor.](https://core.trac.wordpress.org/changeset/57186/) ### Next major WordPress release: 6.5 For information, existing links: * [Roadmap to 6.5](https://make.wordpress.org/core/2023/12/07/roadmap-to-6-5/)  * [#6-5-release-leads](https://wordpress.slack.com/archives/C065MBW03EH) channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) * Reminder [Hallway Hangout ](https://make.wordpress.org/core/2023/11/23/hallway-hangout-lets-explore-wordpress-6-5/) on exploring 6.5 will take place on [Tuesday, 16 January 2024 at 21:00 GMT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240116T2100). * [6.5 documentation tracker](https://github.com/orgs/WordPress/projects/154) has been started on GitHubGitHub GitHub 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/](https://github.com/). * [WordPress 6.5 Editor Tasks board](https://github.com/orgs/WordPress/projects/148). * [Development cycle page](https://make.wordpress.org/core/6-5/). ## Next meeting The next dev chat will be on [January 10, 2024 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240110T2000). Catch up with Dev Chats and summaries from other core meetings at this [link](https://make.wordpress.org/core/tag/summary/). [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/desrosj/) [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj/) 7:11 pm _on_ December 20, 2023   # 󠀁[Updating WordPress to use more modern versions of Node.js/npm: Part 2](https://make.wordpress.org/core/2023/12/20/updating-wordpress-to-use-more-modern-versions-of-node-js-npm-2/)󠁿 As of [[57212]](https://core.trac.wordpress.org/changeset/57212) in the wordpress- develop SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. repository and [415ecc9](https://github.com/WordPress/gutenberg/commit/415ecc997f03c97f92a201fc83c3b2b8191d8b4a) in the GutenbergGutenberg 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/](https://wordpress.org/gutenberg/) repository, the versions of Node.js and npm required for WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development are now 20.x and 10.x. ## Required action by contributors In order to continue contributing to WordPress through `wordpress-develop` or `WordPress/ Gutenberg`, you’ll need to upgrade the version of Node.js installed on your machine to one that’s greater than or equal to 20.10.0 (currently the most recent generally available version 20.x version). This should also update npm to the correct, expected version appropriately (10.2.3 or higher is required). Using [nvm (Node Version Manager)](https://github.com/nvm-sh/nvm) is the recommended and most common way to change the version of Node.js you are running. Both `wordpress- develop` and the Gutenberg repositories have an `.nvmrc` file specifying the desired version. Running `nvm install` within your checkout’s directory will automatically install the latest version that falls within the defined constraints. If you need further guidance on how to install or use Node.js, npm, or nvm, there is a [great tutorial](https://learn.wordpress.org/tutorial/installing-node-js-and-npm-for-local-wordpress-development/) explaining in great detail on [learn.wordpress.org](https://learn.wordpress.org/). > [Installing Node.js and npm for local WordPress development](https://learn.wordpress.org/tutorial/installing-node-js-and-npm-for-local-wordpress-development/) Note: If you have any open pull requests, you will likely need to update your branchbranch A 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". to include these changes to ensure they work and are tested properly. ## How does Node.js versioning work? Before diving in to some of the background for this change, here is a brief overview of how the versioning for Node.js releases works: * Excluding the `main` branch (which is always considered unstable), there are 3 states for versions: current, active (LTS or long term support), and maintenance. * Major versions (18.x, 19.x, etc.) are released every April and October. * October releases (always odd numbered) have a support life of 8 months: 6 in current state, 2 in maintenance. They enter maintenance state in April when the next major version is published. * April releases (always even numbered) are converted to active LTS in October after 6 months as the the current version. They remain in active LTS state for 12 months before moving to maintenance for 18 additional months. You can read more about this on the [project’s Releases page](https://nodejs.dev/en/about/releases/), or the project’s [README file on GitHub](https://github.com/nodejs/node#release-types). ## Why Node.js 20 and not 18 or 21? While it’s always the preference to use the latest version of any software, that’s not always feasible. When upgrading, the team always looks to upgrade to the newest possible version at the time. Initially 18.x was targeted for the next update. However, version 20.x is now the current active LTS version. While 18.x is still in maintenance mode and will not reach end of life (EOL) until April of 2025, 20.x will not reach EOL until April 2026. Testing revealed that there were no blockers for updating to 20.x, so this was determined to be the best landing spot at this time. While it’s true that 21.x is newer and the current version of Node.js, 20.x is the current active LTS version. Because odd versions of Node.js are only supported for 8 months, the project does not typically utilize them. ### Can I use Node.js 21 if I want? Yes! You are free to use any version of Node.js over 20.10.0. But 20.x will always be used to perform any official processing and building of the two projects. However, the Gutenberg repository will now run some tests against newer versions of Node.js as they become available with the hope that problems can be caught earlier, reducing the level of effort required to update Node.js version requirements in the future. If you discover a problem working with the `wordpress-develop` or `gutenberg` repositories on Node.js 21.x, please open a ticketticket Created for both bug reports and feature development on the bug tracker. in the appropriate location so it can be investigated. ## How does this work? There is an upper limit defined for the npm version. The upper limit for the npm version allowed has been removed. This was previously in place because a new format for the `package-lock.json` file was introduced in [npm 7](https://blog.npmjs.org/post/621733939456933888/npm-v7-series-why-keep-package-lockjson.html). While the new and old formats were both forward and backward compatible, running` npm install` using 6 and 7 caused the format to change back and forth. There are currently no known issues that would cause similar problems, so the limit has been removed to allow contributors to use Node.js 21.x if desired, and allow for testing newer versions. If new compatibility issues are discovered, adding a new upper limit can be explored at that time. ## What about the other branches of WordPress Core? The version of Node.js used by all branches of WordPress is currently 14.x with two exceptions: `trunk` and `6.4`. Before today, both were using 16.x. To limit the number of different versions used throughout Core, the 6.4 branch has also been updated to use 20.x. As a reminder, only the most recent version of WordPress is actively supported ( currently 6.4.x). Though security patches are occasionally backported to WordPress 4.1.x, this is not guaranteed and is only done as a courtesy. The build tools in these older branches were [recently updated to be more consistent and reliable](https://make.wordpress.org/core/2021/04/08/recent-build-test-tool-changes-and-github-actions-update/). The level of effort to update, test, and commit the changes required to support Node.js 20.x to all 24+ branches that can potentially receive a security update is very high and is not a good use of time until it’s absolutely necessary. Because of this, there are currently no plans to update older branches to use Node. js 20.x at this time. ## Will the required version be updated to 22.x when it’s released in April 2024? Maybe. This will be evaluated to determine if the update makes sense for the project when the time comes. ## Where can I learn more? Here is a list of locations where discussions related to these changes took place: * [Previous announcement of updating to Node.js 16.x](https://make.wordpress.org/core/2023/08/09/updating-wordpress-to-use-more-modern-versions-of-node-js-npm/) * [WordPress/gutenberg PR-56331](https://github.com/WordPress/gutenberg/pull/56331) * [WordPress/wordpress-develop PR-5515](https://github.com/WordPress/wordpress-develop/pull/5515) * [[Discussion] Upgrade `node` and `npm` to latest LTS versions](https://github.com/WordPress/gutenberg/issues/48588) * Core TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket [#59663](https://core.trac.wordpress.org/ticket/59663) * [Read about the most recent version bump to 16.x](https://make.wordpress.org/core/2023/08/09/updating-wordpress-to-use-more-modern-versions-of-node-js-npm/). This change will likely require some documentation and handbook updates. If you notice any adjustments that need to be made, please do point them out in the appropriate locations so that they can be corrected! _Props [@jorbin](https://profiles.wordpress.org/jorbin/) for pre-publish review._ [ ](https://profiles.wordpress.org/madhudollu/) [Madhu Dollu](https://profiles.wordpress.org/madhudollu/) 2:13 pm _on_ December 20, 2023 Tags: [block-editor ( 137 )](https://make.wordpress.org/core/tag/block-editor/), [core-editor ( 754 )](https://make.wordpress.org/core/tag/core-editor/), [gutenberg ( 544 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-new ( 213 )](https://make.wordpress.org/core/tag/gutenberg-new/)    # 󠀁[What’s new in Gutenberg 17.3? (20 December)](https://make.wordpress.org/core/2023/12/20/whats-new-in-gutenberg-17-3-20-december/)󠁿 “What’s new in GutenbergGutenberg 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/](https://wordpress.org/gutenberg/)…” posts (labeled with the [#gutenberg-new tag](https://make.wordpress.org/core/tag/gutenberg-new/)) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, [here’s an overview](https://make.wordpress.org/core/2020/05/20/ways-to-keep-up-with-full-site-editing-fse/) of different ways to keep up with Gutenberg and the Site Editor project (formerly called [Full Site Editing](https://make.wordpress.org/updates/2022/11/04/site-editor-a-more-user-friendly-name/)). [[ --- Gutenberg 17.3 has been released and is [available for download](https://wordpress.org/plugins/gutenberg/)! This update incorporates numerous enhancements, 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. fixes, improvements in performance and accessibilityAccessibility Accessibility (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 ongoing development of Phase 3 features. 1. [Summary of changes in global styles revision history](https://make.wordpress.org/core/2023/12/20/whats-new-in-gutenberg-17-3-20-december/#global-style-revision-change-summary) 2. [Updated preferences panel](https://make.wordpress.org/core/2023/12/20/whats-new-in-gutenberg-17-3-20-december/#updated-preferences-panel) 3. [Integration of Gravatar Service for Social Icons](https://make.wordpress.org/core/2023/12/20/whats-new-in-gutenberg-17-3-20-december/#integration-of-gravatar-service-for-social-icons) 4. [Other Notable Highlights](https://make.wordpress.org/core/2023/12/20/whats-new-in-gutenberg-17-3-20-december/#other-notable-highlights) 5. [Changelog](https://make.wordpress.org/core/2023/12/20/whats-new-in-gutenberg-17-3-20-december/#changelog) 6. [First time contributors](https://make.wordpress.org/core/2023/12/20/whats-new-in-gutenberg-17-3-20-december/#first-time-contributors) 7. [Contributors](https://make.wordpress.org/core/2023/12/20/whats-new-in-gutenberg-17-3-20-december/#contributors) ## Summary of changes in global styles revision history [[ A brief summary of the revision change set in the global styles and now offers a concise overview for enhanced visibility. ([#56577](https://github.com/WordPress/gutenberg/pull/56577)) ## Updated preferences panel [[ An improved organization of the preferences modal, with introduction of new panels for Appearance and Accessibility settings. ([#56481](https://github.com/WordPress/gutenberg/pull/56481)) ## Integration of GravatarGravatar Is an acronym for Globally Recognized Avatar. It is the avatar system managed by WordPress.com, and used within the WordPress software. 󠀁[https://gravatar.com](https://gravatar.com/)󠁿 Service for Social Icons [[ A new social icon for the Gravatar service in the social icons 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 consistent API and user experience.. Gravatar, widely utilized across various WordPress platforms, provides profile pages that allow individuals to list their web presence. ([#56544](https://github.com/WordPress/gutenberg/pull/56544)) ## Other Notable Highlights * Introduces the ability to adjust the dimensions (margin and padding) of individual list-item blocks. [#55874](https://github.com/WordPress/gutenberg/pull/55874) * Unified post editor with template and post-only editing modes. ([#56671](https://github.com/WordPress/gutenberg/pull/56671)) * Start using modules in the interactive create-block template. ([56694](https://github.com/WordPress/gutenberg/pull/56694)) ## Changelog ### Bug Fixes * (edit-site)(use-init-edited-entity-from-url) Safely access `toString()` on `siteData`‘ s `page_on_front`. ([57035](https://github.com/WordPress/gutenberg/pull/57035)) #### Components * Fix form token field suggestion list reopening after blurring the input. ([57002](https://github.com/WordPress/gutenberg/pull/57002)) ## Contributors The following contributors merged PRs in this release: [@fullofcaffeine](https://profiles.wordpress.org/fullofcaffeine/) [@talldan](https://profiles.wordpress.org/talldan/) = 17.3.0-rc.1 = ### Enhancements * Components: Replace TabPanel with Tabs in the editor’s ColorPanel. ([56878](https://github.com/WordPress/gutenberg/pull/56878)) * Editor: Move the edit template blocks notification to editor package. ([56901](https://github.com/WordPress/gutenberg/pull/56901)) * Editor: Unify the preview dropdown between post and site editors. ([56921](https://github.com/WordPress/gutenberg/pull/56921)) * Editor: Use the same PostTemplatePanel between post and site editors. ([56817](https://github.com/WordPress/gutenberg/pull/56817)) * Tabs: Replace id with new tabId prop. ([56883](https://github.com/WordPress/gutenberg/pull/56883)) * Update main toolbar buttons to all be compact. ([56635](https://github.com/WordPress/gutenberg/pull/56635), [ 56729](https://github.com/WordPress/gutenberg/pull/56729)) * Update preferences organization. ([56481](https://github.com/WordPress/gutenberg/pull/56481)) #### Components * FocalPointPicker with __next40pxDefaultSize. ([56021](https://github.com/WordPress/gutenberg/pull/56021)) * Font Library: Improve usability of font variant selection. ([56158](https://github.com/WordPress/gutenberg/pull/56158)) * Tabs: Sync browser focus to selected tab in controlled mode. ([56658](https://github.com/WordPress/gutenberg/pull/56658)) * Use consistent styling for duotone panels. ([56801](https://github.com/WordPress/gutenberg/pull/56801)) * BorderControl: Fix button styles. ([56730](https://github.com/WordPress/gutenberg/pull/56730)) * DimensionControl: Add __next40pxDefaultSize prop. ([56805](https://github.com/WordPress/gutenberg/pull/56805)) * FontSizePicker: Add opt-in prop for 40px default size. ([56804](https://github.com/WordPress/gutenberg/pull/56804)) * QueryControls: Add opt-in prop for 40px default size. ([56576](https://github.com/WordPress/gutenberg/pull/56576)) #### Block Library * Control dimensions (margin and padding) of the list-item block. ([55874](https://github.com/WordPress/gutenberg/pull/55874)) * Consistent default typography controls across blocks. ([55208](https://github.com/WordPress/gutenberg/pull/55208)) * Social Icons: Add Gravatar service. ([56544](https://github.com/WordPress/gutenberg/pull/56544)) * Tweak table block placeholder with __next40pxDefaultSize props. ([56935](https://github.com/WordPress/gutenberg/pull/56935)) #### Site Editor * Merge the post only mode and the post editor. ([56671](https://github.com/WordPress/gutenberg/pull/56671)) * Site Editor SidebarSidebar A 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.: Add “Areas” details panel to all templates and update icon. ([55677](https://github.com/WordPress/gutenberg/pull/55677)) #### Block Editor * Allow dragging between adjacent container blocks based on a threshold. ([56466](https://github.com/WordPress/gutenberg/pull/56466)) * Components: Replace TabPanel with Tabs in the editor’s ColorGradientControl. ( [56351](https://github.com/WordPress/gutenberg/pull/56351)) #### Data Views * Update data view layout. ([56786](https://github.com/WordPress/gutenberg/pull/56786)) #### Layout * Match the front end layout classname in the editor. ([56774](https://github.com/WordPress/gutenberg/pull/56774)) #### Global Styles * Global style revisionsRevisions The 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.: Show change summary on selected item. ([56577](https://github.com/WordPress/gutenberg/pull/56577)) #### Icons * Another round of HiDPI icon tweaks. ([56532](https://github.com/WordPress/gutenberg/pull/56532)) #### Media * Update external images panel in post publish sidebar. ([55524](https://github.com/WordPress/gutenberg/pull/55524)) #### Post Editor * Implement Tabs in editor settings. ([55360](https://github.com/WordPress/gutenberg/pull/55360)) ### Bug Fixes * Create-block-interactive-template: Add all files to the generated pluginPlugin 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. zip. ([56943](https://github.com/WordPress/gutenberg/pull/56943)) * Create-block-interactive-template: Prevent crash when Gutenberg plugin is not installed. ([56941](https://github.com/WordPress/gutenberg/pull/56941)) * Fix end-to-end test: Update how we find the template title to match markup changes.( [56992](https://github.com/WordPress/gutenberg/pull/56992)) * Fix: Fatal php error if a template was created by an author that was deleted.( [56990](https://github.com/WordPress/gutenberg/pull/56990)) * Fix: PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.1 deprecated warning strpos(). ([56171](https://github.com/WordPress/gutenberg/pull/56171)) * Fix: Use span on template list titles. ([56955](https://github.com/WordPress/gutenberg/pull/56955)) * Font Library: Add font family and font face preview keys to schema. ([56793](https://github.com/WordPress/gutenberg/pull/56793)) * Remove unnecessary CSSCSS Cascading Style Sheets. for shrinking central headerHeader The 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. area. ([56220](https://github.com/WordPress/gutenberg/pull/56220)) * Revert format types hook refactor. ([56859](https://github.com/WordPress/gutenberg/pull/56859)) * Show template center UIUI User interface when no block is selected. ([56217](https://github.com/WordPress/gutenberg/pull/56217)) * setImmutably: Don’t clone all objects. ([56612](https://github.com/WordPress/gutenberg/pull/56612)) #### Block Library * Fix error when using a navigation block that returns an empty fallback result.( [56629](https://github.com/WordPress/gutenberg/pull/56629)) * Fixture Tests: Correctly generate fixture files for form-related blocks. ([56719](https://github.com/WordPress/gutenberg/pull/56719)) * Image: Fix resetting behaviour for alt image text. ([56809](https://github.com/WordPress/gutenberg/pull/56809)) * Social Links Block: Prevent Theme Styles Distorting Size. ([56301](https://github.com/WordPress/gutenberg/pull/56301)) * Update image block save to only save align none class. ([56449](https://github.com/WordPress/gutenberg/pull/56449)) #### Components * DropdownMenuV2Ariakit: Prevent prefix collapsing if all radios or checkboxes are unselected. ([56720](https://github.com/WordPress/gutenberg/pull/56720)) * FormToggle: Do not use “/” math operator. ([56672](https://github.com/WordPress/gutenberg/pull/56672)) * PaletteEdit: Temporary custom gradient not saving. ([56896](https://github.com/WordPress/gutenberg/pull/56896)) * ToggleGroupControl: ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. [https://reactjs.org](https://reactjs.org/) correctly to external controlled updates. ([56678](https://github.com/WordPress/gutenberg/pull/56678)) #### Block Editor * Apply __next40pxDefaultSize to TextControl and Button component in renaming UIs.( [56933](https://github.com/WordPress/gutenberg/pull/56933)) * Pattern inserter: Fix Broken preview layout. ([56814](https://github.com/WordPress/gutenberg/pull/56814)) * Patterns: Keep synced pattern when added via drag and drop. ([56924](https://github.com/WordPress/gutenberg/pull/56924)) #### Design Tools * Background image support: Fix duplicate output of styling rules. ([56997](https://github.com/WordPress/gutenberg/pull/56997)) * Fix sticky position in classic themes with appearance tools support. ([56743](https://github.com/WordPress/gutenberg/pull/56743)) #### Post Editor * Editor Canvas: Fix animation when device type changes. ([56970](https://github.com/WordPress/gutenberg/pull/56970)) * Editor: Fix display of edit template blocks notification. ([56978](https://github.com/WordPress/gutenberg/pull/56978)) #### Site Editor * Fix active edited post. ([56863](https://github.com/WordPress/gutenberg/pull/56863)) * Show back button when editing navigation and template area in-place with no URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org params. ([56741](https://github.com/WordPress/gutenberg/pull/56741)) #### Typography * Fix order of typography sizes and families. ([56659](https://github.com/WordPress/gutenberg/pull/56659)) * Font Library: Fix font uninstallation. ([56762](https://github.com/WordPress/gutenberg/pull/56762)) #### Navigation in Site View * Navigation editor: Fix content mode. ([56856](https://github.com/WordPress/gutenberg/pull/56856)) #### Patterns * Fix top position and height of Pattern Modal Sidebar. ([56787](https://github.com/WordPress/gutenberg/pull/56787)) #### Interactivity APIAPI 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. * Start using modules in the interactive create-block template. ([56694](https://github.com/WordPress/gutenberg/pull/56694)) #### Layout * Fix input not showing when switching to “Fixed” width. ([56660](https://github.com/WordPress/gutenberg/pull/56660)) #### Data Views * Align data view icon usage. ([56602](https://github.com/WordPress/gutenberg/pull/56602)) #### Block Styles * Consolidate and resolve display issues between InserterPreviewPanel and BlockStylesPreviewPanel.( [56011](https://github.com/WordPress/gutenberg/pull/56011)) #### Inspector Controls * Decode some characters if used in taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. [https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies). name so it’s displayed correctly in Query LoopLoop The 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_Loop](https://codex.wordpress.org/The_Loop) filters. ([50376](https://github.com/WordPress/gutenberg/pull/50376)) ### Accessibility #### Data Views * Add scroll padding to dataviews container. ([56946](https://github.com/WordPress/gutenberg/pull/56946)) * Adding aria-sort to table view headers. ([56860](https://github.com/WordPress/gutenberg/pull/56860)) * Fix: Use span instead of heading for the template titles. ([56785](https://github.com/WordPress/gutenberg/pull/56785)) #### Post Editor * Avoid to show unnecessary Tooltip for the Post Schedule button. ([56759](https://github.com/WordPress/gutenberg/pull/56759)) #### Block Editor * Increase right padding of URL field to take the Submit button into account. ( [56685](https://github.com/WordPress/gutenberg/pull/56685)) #### Site Editor * Shorter screen reader announcement after changing pages. ([56339](https://github.com/WordPress/gutenberg/pull/56339)) #### Components * Use tooltip for the Timezone only when necessary. ([56214](https://github.com/WordPress/gutenberg/pull/56214)) ### Performance * Block editor: Make all BlockEdit hooksHooks In 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. pure. ([56813](https://github.com/WordPress/gutenberg/pull/56813)) * Block editor: Remove 4 useSelect in favour of context. ([56915](https://github.com/WordPress/gutenberg/pull/56915)) * Block editor: hooks: Avoid BlockEdit filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/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. for content locking UI. ([56957](https://github.com/WordPress/gutenberg/pull/56957)) * Block editor: hooks: Share block settings. ([56852](https://github.com/WordPress/gutenberg/pull/56852)) * Keycodes: Avoid regex for capital case. ([56822](https://github.com/WordPress/gutenberg/pull/56822)) * Measure typing without inspector. ([56753](https://github.com/WordPress/gutenberg/pull/56753)) * Media upload component: Lazy mount. ([56958](https://github.com/WordPress/gutenberg/pull/56958)) * Paragraph: Store subscription for selected block only. ([56967](https://github.com/WordPress/gutenberg/pull/56967)) * Perf: Reopen inspector for remaining tests. ([56780](https://github.com/WordPress/gutenberg/pull/56780)) * useBlockProps: Combine store subscriptions. ([56847](https://github.com/WordPress/gutenberg/pull/56847)) #### Block Editor * Improve opening inserter in post editor. ([57006](https://github.com/WordPress/gutenberg/pull/57006)) * hooks: Subscribe only to relevant attributes. ([56783](https://github.com/WordPress/gutenberg/pull/56783)) #### Site Editor * Fix typing performance by not rendering sidebar. ([56927](https://github.com/WordPress/gutenberg/pull/56927)) #### Components * ToolsPanel: Fix deregister/register on type. ([56770](https://github.com/WordPress/gutenberg/pull/56770)) #### Modules API * Load the import map polyfill only when there is an import map. ([56699](https://github.com/WordPress/gutenberg/pull/56699)) #### Post Editor * Editor: Avoid double parsing content in ‘getSuggestedPostFormat’ selelector. ( [56679](https://github.com/WordPress/gutenberg/pull/56679)) ### Experiments #### Data Views * DataViews: Add story. ([56761](https://github.com/WordPress/gutenberg/pull/56761)) * DataViews: Add support for NOT IN operator in filter. ([56479](https://github.com/WordPress/gutenberg/pull/56479)) * DataViews: Centralize the view definition and rename list to table. ([56693](https://github.com/WordPress/gutenberg/pull/56693)) * DataViews: Do not export strings constants. ([56754](https://github.com/WordPress/gutenberg/pull/56754)) * DataViews: Export the view components as defaults. ([56677](https://github.com/WordPress/gutenberg/pull/56677)) * DataViews: Fix dropdown menu actions with modal. ([56760](https://github.com/WordPress/gutenberg/pull/56760)) * DataViews: Hide pagination if we have only one page. ([56948](https://github.com/WordPress/gutenberg/pull/56948)) * DataViews: Implement NOT IN operator for author filter in templates. ([56777](https://github.com/WordPress/gutenberg/pull/56777)) * DataViews: Iterate on list view. ([56746](https://github.com/WordPress/gutenberg/pull/56746)) * DataViews: Make Actions styles the same as any other column header. ([56654](https://github.com/WordPress/gutenberg/pull/56654)) * DataViews: Make mediaField not hidable. ([56643](https://github.com/WordPress/gutenberg/pull/56643)) * DataViews: Rename view components. ([56709](https://github.com/WordPress/gutenberg/pull/56709)) * DataViews: Render data async conditionally. ([56851](https://github.com/WordPress/gutenberg/pull/56851)) * DataViews: Set proper role for AddFilter’s items. ([56714](https://github.com/WordPress/gutenberg/pull/56714)) * DataViews: Set proper semantics for dropdown items. ([56676](https://github.com/WordPress/gutenberg/pull/56676)) * DataViews: Update sorting semantics. ([56717](https://github.com/WordPress/gutenberg/pull/56717)) * Dataviews: Extract to dedicated bundled package. ([56721](https://github.com/WordPress/gutenberg/pull/56721)) #### Block Validation/Deprecation * Input Field Block: Use useblockProps hook in save function. ([56507](https://github.com/WordPress/gutenberg/pull/56507)) #### Patterns * Implement partially synced patterns behind an experimental flag. ([56235](https://github.com/WordPress/gutenberg/pull/56235)) ### Documentation * Add the nested blocks chapter to the platform documentation. ([56689](https://github.com/WordPress/gutenberg/pull/56689)) * Components: Update CHANGELOG.md. ([56960](https://github.com/WordPress/gutenberg/pull/56960)) * Doc: Search Control – add Storybook link. ([56815](https://github.com/WordPress/gutenberg/pull/56815)) * Doc: Spinner – add Storybook link. ([56818](https://github.com/WordPress/gutenberg/pull/56818)) * Docs: Add storybook link for spinner component. ([56953](https://github.com/WordPress/gutenberg/pull/56953)) * Docs: Fix {% end %} tab position to show the text. ([56735](https://github.com/WordPress/gutenberg/pull/56735)) * Docs: Fundamentals of Block Development – Minor fixes – registration-of-a-block.( [56731](https://github.com/WordPress/gutenberg/pull/56731)) * Docs: Fundamentals of Block Development – add links. ([56700](https://github.com/WordPress/gutenberg/pull/56700)) * Docs: Fundamentals of Block Development —- Small fixes for “Block wrapper”. ( [56651](https://github.com/WordPress/gutenberg/pull/56651)) * Link to Dashicons. ([56872](https://github.com/WordPress/gutenberg/pull/56872)) * Platform Docs: Add trusted by section. ([56749](https://github.com/WordPress/gutenberg/pull/56749)) * Revert “Doc: Spinner – add Storybook link”. ([56913](https://github.com/WordPress/gutenberg/pull/56913)) * Update Getting Started Guide for Gutenberg 17.2. ([56674](https://github.com/WordPress/gutenberg/pull/56674)) * Update InnerBlocks defaultblock doc usage. ([56728](https://github.com/WordPress/gutenberg/pull/56728)) * Update formatting and fix grammar in the Block Editor Handbook readme. ([56798](https://github.com/WordPress/gutenberg/pull/56798)) ### Code Quality * Block editor: hooks: Avoid getEditWrapperProps. ([56912](https://github.com/WordPress/gutenberg/pull/56912)) * Block lib: Use RichText.isEmpty where forgotten. ([56726](https://github.com/WordPress/gutenberg/pull/56726)) * Block library: Reusable caption component util. ([56606](https://github.com/WordPress/gutenberg/pull/56606)) * CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. data revisions: Remove hardcoded supports constant. ([56701](https://github.com/WordPress/gutenberg/pull/56701)) * Editor: Cleanup default editor mode handling. ([56819](https://github.com/WordPress/gutenberg/pull/56819)) * Editor: Move the BlockCanvas component within the EditorCanvas component. ([56850](https://github.com/WordPress/gutenberg/pull/56850)) * Editor: Move the device type state to the editor package. ([56866](https://github.com/WordPress/gutenberg/pull/56866)) * Editor: Unify device preview styles. ([56904](https://github.com/WordPress/gutenberg/pull/56904)) * Fix PHP linter failing. ([56905](https://github.com/WordPress/gutenberg/pull/56905)) * Framework: Bundle the BlockTools component within BlockCanvas. ([56996](https://github.com/WordPress/gutenberg/pull/56996)) * Move useDebouncedInput hook to wordpress/compose package. ([56744](https://github.com/WordPress/gutenberg/pull/56744)) * Post Editor: Rely on the editor store for the template mode state. ([56716](https://github.com/WordPress/gutenberg/pull/56716)) * Refactor . ([56335](https://github.com/WordPress/gutenberg/pull/56335)) * Remove Block Tools BackCompat. ([56874](https://github.com/WordPress/gutenberg/pull/56874)) * Site and Post Editor: Unify the DocumentBar component. ([56778](https://github.com/WordPress/gutenberg/pull/56778)) * getValueFromObjectPath: Remove memize. ([56711](https://github.com/WordPress/gutenberg/pull/56711)) #### Block Editor * Don’t render undefined classname in useBlockProps hook. ([56923](https://github.com/WordPress/gutenberg/pull/56923)) * One hook to rule them all: Preparation for a block supports API. ([56862](https://github.com/WordPress/gutenberg/pull/56862)) * RichText: Pass value to store. ([43204](https://github.com/WordPress/gutenberg/pull/43204)) * hooks: Manage BlockListBlock filters in one place. ([56875](https://github.com/WordPress/gutenberg/pull/56875)) #### Global Styles * Command Palette: Use getRevisions instead of deprecated selector. ([56738](https://github.com/WordPress/gutenberg/pull/56738)) * Global styles revisions: Remove PHP unit tests that are running in Core. ([56492](https://github.com/WordPress/gutenberg/pull/56492)) #### Components * Site editor: Do not use navigator’s internal classname. ([56911](https://github.com/WordPress/gutenberg/pull/56911)) #### Data Views * DataViews: Remove TanStack. ([56873](https://github.com/WordPress/gutenberg/pull/56873)) ### Tools * Env: Migrate to Compose V2. ([51339](https://github.com/WordPress/gutenberg/pull/51339)) * Scripts: Fix CSS imports not minified. ([56516](https://github.com/WordPress/gutenberg/pull/56516)) * wp-env: Make env-cwd option work on Windows. ([56265](https://github.com/WordPress/gutenberg/pull/56265)) #### Testing * Migrate ‘editor multi entity saving’ end-to-end tests to Playwright. ([56670](https://github.com/WordPress/gutenberg/pull/56670)) * Migrate ‘inner-blocks-locking-all-embed’ end-to-end tests to Playwright. ([56673](https://github.com/WordPress/gutenberg/pull/56673)) * Migrate ‘site editor export’ end-to-end tests to Playwright. ([56675](https://github.com/WordPress/gutenberg/pull/56675)) * RN: Add watch mode for native tests. ([56788](https://github.com/WordPress/gutenberg/pull/56788)) * Scripts: Enable skipping Playwright browser installation. ([56594](https://github.com/WordPress/gutenberg/pull/56594)) * Tabs: Implement ariakit/test in unit tests. ([56835](https://github.com/WordPress/gutenberg/pull/56835)) * CustomSelectControl: Add additional unit tests. ([56575](https://github.com/WordPress/gutenberg/pull/56575)) ### Copy * Copy/fix capitalization of WordPress. ([56834](https://github.com/WordPress/gutenberg/pull/56834)) #### Site Editor * Improve text and design of the block removal warnings. ([56869](https://github.com/WordPress/gutenberg/pull/56869)) #### Global Styles * Global styles welcome guide: Add a space between translated strings. ([56839](https://github.com/WordPress/gutenberg/pull/56839)) #### Block Library * Simplify page list edit warning. ([56829](https://github.com/WordPress/gutenberg/pull/56829)) #### Patterns * End pattern page descriptions with a period. ([56828](https://github.com/WordPress/gutenberg/pull/56828)) ## First time contributors The following PRs were merged by first time contributors: * [@benoitchantre](https://github.com/benoitchantre): Scripts: Fix CSS imports not minified. ([56516](https://github.com/WordPress/gutenberg/pull/56516)) * [@kmanijak](https://github.com/kmanijak): Decode some characters if used in taxonomy name so it’s displayed correctly in Query Loop filters. ([50376](https://github.com/WordPress/gutenberg/pull/50376)) * [@lithrel](https://github.com/lithrel): Env: Migrate to Compose V2. ([51339](https://github.com/WordPress/gutenberg/pull/51339)) * [@nk-o](https://github.com/nk-o): Fix: PHP 8.1 deprecated warning strpos(). ( [56171](https://github.com/WordPress/gutenberg/pull/56171)) * [@taylorgorman](https://github.com/taylorgorman): Link to Dashicons. ([56872](https://github.com/WordPress/gutenberg/pull/56872)) * [@valerogarte](https://github.com/valerogarte):[ #55702](https://github.com/WordPress/gutenberg/issues/55702)– Control dimensions (margin and padding) of the list-item block. ([55874](https://github.com/WordPress/gutenberg/pull/55874)) ## Contributors The following contributors merged PRs in this release: [@afercia](https://github.com/afercia)[ @ajlende](https://github.com/ajlende)[ @alexstine](https://github.com/alexstine) [ @andrewhayward](https://github.com/andrewhayward)[ @andrewserong](https://github.com/andrewserong) [ @apeatling](https://github.com/apeatling)[ @atachibana](https://github.com/atachibana) [ @Aurorum](https://github.com/Aurorum)[ @benoitchantre](https://github.com/benoitchantre) [ @bph](https://github.com/bph)[ @brookewp](https://github.com/brookewp)[ @chad1008](https://github.com/chad1008) [ @ciampo](https://github.com/ciampo)[ @colorful-tones](https://github.com/colorful-tones) [ @dcalhoun](https://github.com/dcalhoun)[ @derekblank](https://github.com/derekblank) [ @draganescu](https://github.com/draganescu)[ @ellatrix](https://github.com/ellatrix) [ @fluiddot](https://github.com/fluiddot)[ @geriux](https://github.com/geriux)[ @getdave](https://github.com/getdave) [ @jameskoster](https://github.com/jameskoster)[ @jasmussen](https://github.com/jasmussen) [ @jeherve](https://github.com/jeherve)[ @jeryj](https://github.com/jeryj)[ @jffng](https://github.com/jffng) [ @jonathanbossenger](https://github.com/jonathanbossenger)[ @jorgefilipecosta](https://github.com/jorgefilipecosta) [ @jsnajdr](https://github.com/jsnajdr)[ @juanmaguitar](https://github.com/juanmaguitar) [ @kevin940726](https://github.com/kevin940726)[ @kmanijak](https://github.com/kmanijak) [ @lithrel](https://github.com/lithrel)[ @luisherranz](https://github.com/luisherranz) [ @Mamaduka](https://github.com/Mamaduka)[ @matiasbenedetto](https://github.com/matiasbenedetto) [ @mikachan](https://github.com/mikachan)[ @miminari](https://github.com/miminari) [ @mtias](https://github.com/mtias)[ @ndiego](https://github.com/ndiego)[ @nk-o](https://github.com/nk-o) [ @ntsekouras](https://github.com/ntsekouras)[ @oandregal](https://github.com/oandregal) [ @ramonjd](https://github.com/ramonjd)[ @richtabor](https://github.com/richtabor) [ @scruffian](https://github.com/scruffian)[ @SiobhyB](https://github.com/SiobhyB) [ @t-hamano](https://github.com/t-hamano)[ @talldan](https://github.com/talldan) [ @taylorgorman](https://github.com/taylorgorman)[ @tellthemachines](https://github.com/tellthemachines) [ @tyxla](https://github.com/tyxla)[ @valerogarte](https://github.com/valerogarte) [ @WunderBart](https://github.com/WunderBart)[ @youknowriad](https://github.com/youknowriad) _Many thanks to [@mikachan](https://profiles.wordpress.org/mikachan/) for helping out to publish the plugin, [@jameskoster](https://profiles.wordpress.org/jameskoster/) for providing graphics for this post, [@mikachan](https://profiles.wordpress.org/mikachan/) and [@vcanales](https://profiles.wordpress.org/vcanales/) for reviewing the draft of this post._ [#block-editor](https://make.wordpress.org/core/tag/block-editor/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#gutenberg-new](https://make.wordpress.org/core/tag/gutenberg-new/) [ ](https://profiles.wordpress.org/pbearne/) [Paul Bearne](https://profiles.wordpress.org/pbearne/) 7:21 pm _on_ December 19, 2023   # 󠀁[Proposal: Add company icons to sponsored contributors on about page](https://make.wordpress.org/core/2023/12/19/proposal-add-company-icons-to-sponsored-contributors-on-about-page/)󠁿 [[ To do this will need to ask for small icon (eg. favicon) or fetch some aria-hidden markup and hover title etc. I am suggesting this to encourage companies to support WP more and so user can see where the support is coming from. Thoughts This was prematurely published and a new/updated proposal will be coming soon and I have been ask to expand this [ ](https://profiles.wordpress.org/clarkeemily/) [Emily Clarke](https://profiles.wordpress.org/clarkeemily/) 5:00 pm _on_ December 19, 2023 Tags: [core-performance ( 145 )](https://make.wordpress.org/core/tag/core-performance/), [performance ( 411 )](https://make.wordpress.org/core/tag/performance/), [performance-chat ( 338 )](https://make.wordpress.org/core/tag/performance-chat/), [summary ( 972 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Performance Chat Summary: 19 December 2023](https://make.wordpress.org/core/2023/12/19/performance-chat-summary-19-december-2023/)󠁿 [Meeting agenda here](https://make.wordpress.org/core/2023/12/19/performance-chat-agenda-19-december-2023/) and the full chat log is available [beginning here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1703001605683389). ## Announcements * Welcome to our new members of [#core-performance](http://wordpress.slack.com/messages/core-performance/) * Call for 2024 roadmap priorities https://github.com/WordPress/performance/issues/ 903 * Highlighting this recent post on [WordPress performance impact on Core Web Vitals in 2023](https://make.wordpress.org/core/2023/12/19/wordpress-performance-impact-on-core-web-vitals-in-2023/) * Reminder there will be no SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) meeting on Tuesday December 26 ## Priority Projects ### Server Response Time [Link to roadmap projects](https://make.wordpress.org/performance/roadmap-2023/#category-server-response-time) and link to the [GitHub project board](https://github.com/orgs/WordPress/projects/112/views/1) Contributors: [@joemcgill](https://profiles.wordpress.org/joemcgill/) [@swissspidy](https://profiles.wordpress.org/swissspidy/) [@thekt12](https://profiles.wordpress.org/thekt12/) [@mukesh27](https://profiles.wordpress.org/mukesh27/) [@pereirinha](https://profiles.wordpress.org/pereirinha/) * [@thekt12](https://profiles.wordpress.org/thekt12/) several updates - Need someone from GB team to review – [#59969](https://core.trac.wordpress.org/ticket/59969) - PR is ready for review – [https://github.com/WordPress/wordpress-develop/pull/5281](https://github.com/WordPress/wordpress-develop/pull/5281) - Continuing research on – [#59719](https://core.trac.wordpress.org/ticket/59719) - Need to review (to start) – [https://core.trac.wordpress.org/ticket/60025#comment:6](https://core.trac.wordpress.org/ticket/60025#comment:6) * [@joemcgill](https://profiles.wordpress.org/joemcgill/) On the lazy-loading variations ticketticket Created for both bug reports and feature development on the bug tracker., I did hear from @mamaduka yesterday that he plans on reviewing that ticket soon, as he’s been off for the past few weeks. * [@joemcgill](https://profiles.wordpress.org/joemcgill/) Related to work we did in 6.4, I’ve been tracking some follow-up bugs that were reported due to the deprecation of `STYLESHEETPATH` and `TEMPLATEPATH` env vars, and would appreciate a second opinion. See: [https://wordpress.slack.com/archives/C02KGN5K076/p1702953637418849](https://wordpress.slack.com/archives/C02KGN5K076/p1702953637418849) - [@thekt12](https://profiles.wordpress.org/thekt12/) will check this today ### Database Optimization [Link to roadmap projects](https://make.wordpress.org/performance/roadmap-2023/#category-database-optimization) and link to the [GitHub project board](https://github.com/orgs/WordPress/projects/119/views/1) Contributors: [@mukesh27](https://profiles.wordpress.org/mukesh27/) [@thekt12](https://profiles.wordpress.org/thekt12/) * No updates this week ### JavaScriptJavaScript JavaScript 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](https://www.javascript.com/)󠁿 & CSSCSS Cascading Style Sheets. [Link to roadmap project](https://make.wordpress.org/performance/roadmap-2023/#category-javascript-css) and link to the [GitHub project board](https://github.com/orgs/WordPress/projects/114/views/1) Contributors: [@mukesh27](https://profiles.wordpress.org/mukesh27/) [@flixos90](https://profiles.wordpress.org/flixos90/) [@westonruter](https://profiles.wordpress.org/westonruter/) * [@flixos90](https://profiles.wordpress.org/flixos90/) No real update, just that I’m currently experimenting with the Interactivity APIAPI 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., specifically to use it in classic default themes to replace more manual custom JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors.. Partly to familiarize myself with the API, partly for a first prototype of something we _could_ potentially do in the future. Should have a first draft PR up for later today. Really for reference more than anything ### Images [Link to roadmap projects](https://make.wordpress.org/performance/roadmap-2023/#category-images) and link to the [GitHub project board](https://github.com/orgs/WordPress/projects/116/views/1) Contributors: [@flixos90](https://profiles.wordpress.org/flixos90/) [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) [@joemcgill](https://profiles.wordpress.org/joemcgill/) [@pereirinha](https://profiles.wordpress.org/pereirinha/) [@westonruter](https://profiles.wordpress.org/westonruter/) * [@joemcgill](https://profiles.wordpress.org/joemcgill/) Last week I put together [a small experiment](https://github.com/WordPress/performance/issues/791#issuecomment-1856330050) to see how the new auto-sizes for lazy-loaded images feature is working now that it’s being implemented in browsers. Based on that exploration, I put together [an initial module implementation](https://github.com/WordPress/performance/pull/904) that can already be used for testing. I plan to update the PR this week. - Related – I also opened [a new issue](https://github.com/WordPress/performance/issues/911) to discuss how we want to handle new modules once the unbundling project is complete. Feedback would be appreciated. ### Measurement [Link to roadmap projects](https://make.wordpress.org/performance/roadmap-2023/#category-measurement) and link to the [GitHub project board](https://github.com/orgs/WordPress/projects/120) Contributors: [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) [@joemcgill](https://profiles.wordpress.org/joemcgill/) [@mukesh27](https://profiles.wordpress.org/mukesh27/) [@swissspidy](https://profiles.wordpress.org/swissspidy/) [@flixos90](https://profiles.wordpress.org/flixos90/) * No updates this week ### Ecosystem Tools [Link to roadmap projects](https://make.wordpress.org/performance/roadmap-2023/#category-ecosystem-tools) and link to the [GitHub repo](https://github.com/WordPress/plugin-check) for PluginPlugin 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Checker Contributors: [@mukesh27](https://profiles.wordpress.org/mukesh27/) [@swissspidy](https://profiles.wordpress.org/swissspidy/) * [@mukesh27](https://profiles.wordpress.org/mukesh27/) For the Plugin Check, I have been addressing [issue 342](https://github.com/WordPress/plugin-check/issues/342) and have opened [PR 347](https://github.com/WordPress/plugin-check/pull/347), which is now ready for review and I also supported in code review process. Moreover, there is positive news that some community contributors are actively working on several issues and have raised corresponding PRs for them.  ### Creating Standalone Plugins [Link to GitHub overview issue](https://github.com/WordPress/performance/issues/656) Contributors: [@flixos90](https://profiles.wordpress.org/flixos90/) [@mukesh27](https://profiles.wordpress.org/mukesh27/) * [@mukesh27](https://profiles.wordpress.org/mukesh27/) We are on the cusp of completing [Milestone 2a issues](https://github.com/WordPress/performance/issues/656) for** Creating Standalone Plugins.** - The following PRs have been successfully merged: * [Implemented migration logic and UI from old PL modules to new standalone plugins in the PL settings screen #652](https://github.com/WordPress/performance/issues/652)– Merged  * [Enhanced the user experience during the installation _and_ activation of standalone plugins #880](https://github.com/WordPress/performance/issues/880)– Merged  * [Follow-up: Minor changes for creating standalone plugins #912](https://github.com/WordPress/performance/pull/912)– Merged  * [Implementing an admin pointer to prompt users to activate the new standalone plugins #653](https://github.com/WordPress/performance/issues/653)– Merged # Open Floor * [@desrosj](https://profiles.wordpress.org/desrosj/) I noticed that the [performance tests started failing in some older branches](https://github.com/WordPress/wordpress-develop/actions/runs/7252534058/job/19757468182) while working on some E2E test related changes. Well, it only seems to be happening for the 6.4 branchbranch A 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". currently. But I’m wondering if the needed conditions just haven’t been met for the other branches. - [@joemcgill](https://profiles.wordpress.org/joemcgill/) I’m only seeing the latest commit fail according to [this list](https://github.com/WordPress/wordpress-develop/actions/workflows/performance.yml?query=branch%3A6.4). Am I looking at the wrong thing? - [@desrosj](https://profiles.wordpress.org/desrosj/) That’s accurate. I was confusing the additional E2E failures with something (potentially) unrelated that I’ve fixed separately. [#60095](https://core.trac.wordpress.org/ticket/60095) is what I was working on. The step that is failing seems to be checking 6.1.1 for a baseline if I’m reading it correctly. - [@joemcgill](https://profiles.wordpress.org/joemcgill/) I’m going to try rerunning that one, since the same commit to the 6.3 branch worked fine. - [@desrosj](https://profiles.wordpress.org/desrosj/) - FWIW, I committed the fix for 60095 in the 6.1 branch this morning, and this workflow was from yesterday. Maybe the re-run does not include changes for the other branch because they were not there when this change was made? Started a [manual run](https://github.com/WordPress/wordpress-develop/actions/runs/7264904948) for 6.4 to try and rule that out. **Our next chat will be held on [Tuesday, January 2, 2024 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240102T1600) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/).** [#core-performance](https://make.wordpress.org/core/tag/core-performance/), [#performance](https://make.wordpress.org/core/tag/performance/), [#performance-chat](https://make.wordpress.org/core/tag/performance-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/flixos90/) [Felix Arntz](https://profiles.wordpress.org/flixos90/) 1:59 pm _on_ December 19, 2023 Tags: [analysis ( 3 )](https://make.wordpress.org/core/tag/analysis/), [core web vitals ( 2 )](https://make.wordpress.org/core/tag/core-web-vitals/), [core-performance ( 145 )](https://make.wordpress.org/core/tag/core-performance/), [performance ( 411 )](https://make.wordpress.org/core/tag/performance/)    # 󠀁[WordPress performance impact on Core Web Vitals in 2023](https://make.wordpress.org/core/2023/12/19/wordpress-performance-impact-on-core-web-vitals-in-2023/)󠁿 This post summarizes and highlights the impact that WordPress has had on [Core Web Vitals (CWV)](https://web.dev/explore/learn-core-web-vitals) in the field in 2023, providing a metric-based retrospective at the end of the year. **TL;DR:** The WordPress performance team and all WordPress contributors can be very proud of the accomplishments: **The overall CWV passing rate across all WordPress sites has improved from 28.31% to 36.44% (+8.13%) on mobile devices and from 32.55% to 40.80% (+8.25%) on desktop devices.** 🎉 These improvements led to a visible increase of CWV passing rates even for the entire web. The performance team is currently discussing additional findings to define the focus for 2024 and is looking for further proposals and contributors for next year. Note: This post is based on the [slide deck](https://docs.google.com/presentation/d/1iN2PL3yLvztEt3FYzI5eO7bLjUJL_5t-xsdGHNj7QLA/edit) used in a presentation for the [WordPress performance year-end hallway hangout](https://make.wordpress.org/core/2023/11/30/hallway-hangout-performance-end-of-year-review-2023/)( also see [recording](https://www.youtube.com/watch?v=p2BLaRrcnis)). Feel free to review the deck as well as an alternative way to consume the numbers. ## **A few notes on CWV field metrics** Before looking at the 2023 metrics in more depth, a few things should be clarified. The metrics shared in this post are exclusively _field metrics_. They are distinctively different from _lab metrics_, which are the metrics that have typically been shared in the WordPress release performance summary posts this year: * [WordPress 6.2 performance improvements post](https://make.wordpress.org/core/2023/04/05/wordpress-6-2-performance-improvements-for-all-themes/) * [WordPress 6.3 performance improvements post](https://make.wordpress.org/core/2023/08/07/wordpress-6-3-performance-improvements/) * [WordPress 6.4 performance improvements post](https://make.wordpress.org/core/2023/11/13/wordpress-6-4-performance-improvements/) Lab metrics are benchmarks conducted on demand, typically as a synthetic A/B performance comparison. They provide an indication of whether/how a specific change is _anticipated_ to impact performance. For example, for the lab metrics shared for the WordPress releases in the aforementioned posts, the load time performance of the respective new WordPress version was compared to that of the previous version, on the exact same setup, so that the only different variable is the WordPress version. Field metrics on the other hand are analytics data collected from site usage and provide an indication of how performance is _actually_ experienced by real users on real sites. For example, the [Chrome User Experience Report (CrUX)](https://developer.chrome.com/docs/crux) provides a public dataset of performance field data from opted-in Chrome users, aggregated at the site level. The [WordPress 6.3 field impact summary post](https://make.wordpress.org/core/2023/09/19/analyzing-the-core-web-vitals-performance-impact-of-wordpress-6-3-in-the-field/) shared metrics queried from that dataset, granularly broken down for just that release compared to the previous 6.2 release. When reviewing field metrics, it is important to consider the following: * Field metrics are influenced by a myriad of factors, for example the active plugins and theme, the WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. version, the hosting stack, the browser(s) used by end users, their networknetwork (versus site, blog) connection, and more. So when comparing field data between two months, for example, it is impossible to limit the comparison to just one specific aspect of those. * Field metrics do not allow direct correlation between specific enhancements and their concrete metric impact. This is closely related to the previous point: Even if you compare the performance of a dataset of sites that enabled a specific feature before and after the change, for example, there may have been numerous other changes during that time that influence the data. Effectively, it is impossible to conduct clean A/B tests in the field. * Field metrics are more meaningful the larger the dataset is. Because of them being only indicators rather than “proof”, the larger the relevant dataset the more a specific metric observation from it can be trusted. It’s also worth considering that the web’s user base is incredibly diverse, so even the audience that a specific site has matters significantly for its field performance. And yet, despite all these caveats, field metrics are the only way to validate how beneficial performance changes really are. If a performance “improvement” doesn’t impact real users, it effectively doesn’t matter even if it looked great in the lab. ### **CWV breakdown and assessment** For a brief recap on Core Web Vitals (CWV), they are a set of three specific metrics: * [Largest Contentful Paint (LCP)](https://web.dev/articles/lcp) measures how fast the page loads (load time performance). * [First Input Delay (FID)](https://web.dev/articles/fid) measures how quickly interactions work (interactivity). * [Cumulative Layout Shift (CLS)](https://web.dev/articles/cls) measures how stable page elements are (layout stability). Each of these metrics has thresholds for whether a value is considered “good”, whether it “needs improvement” or whether it is “poor”. [⌊The CWV metrics LCP ("good" threshold of 2.5s or lower), FID ("good" threshold of 100ms or lower), and CLS ("good" threshold of 0.1 or lower)⌉⌊The CWV metrics LCP ("good" threshold of 2.5s or lower), FID ("good" threshold of 100ms or lower), and CLS ("good" threshold of 0.1 or lower)⌉[ _This visualization shows the three CWV metrics and their thresholds._ These metrics can be captured for every single navigation / page load. A page load is then only considered to have “good” CWV if _all_ three metrics show a “good” value. In other words, for a single navigation the CWV assessment is simply a binary metric of “good” or “not good”. When looking at actual CWV datasets in the field, metrics are always aggregated, typically at the site / origin level. In other words, such an aggregation encompasses all navigations that happened on that site in a given time frame. In that dimension, the CWV assessment is considered “good” if 75% or more of the navigations have a“ good” CWV assessment. Last but not least, CWV can also be assessed at a larger scale, for example across all sites using a specific technology, like WordPress. In that scenario, CWV are typically measured through a “passing rate” which describes the percentage of sites that have a “good” CWV assessment. For example, if in a dataset of 1 million sites 200,000 of them have a “good” CWV assessment, the resulting passing rate is 20%. Note that not only the overarching CWV passing rate can be measured, but also the passing rates for the individual metrics (LCP, FID, CLS and others). The CWV passing rate is however the most meaningful single metric as it is a summary of all of them. But now let’s take a look at the data. Note: All metrics highlighted in this post are CrUX passing rates from the field, based on year-over-year comparisons between October 2023 and October 2022 (unless otherwise indicated). ## **WordPress CWV in 2023** As already mentioned in the “TL;DR” at the beginning of this post, CWV for WordPress have improved significantly this year: * Mobile CWV passing rate improved **8.13%** (from 28.31% to 36.44%). * Desktop CWV passing rate improved **8.25%** (from 32.55% to 40.80%). While at first glance ~8% may not sound like much, it is a quite substantial boost to the passing rates, particularly when considering their base values. Relatively speaking, the new passing rate is ~29% higher than the old one on mobile and ~25% higher on desktop. For reference: The previous year’s improvement for CWV passing rate was 6.99% on mobile and 6.25% for desktop. So while WordPress already did a great job in the previous year, this year even exceeded those accomplishments. [⌊Line chart of WordPress's mobile CWV passing rate gradually improving from below 30% to over 35%. There is a small drop between March and April 2023, annotated with" LCP algorithm slightly changed".⌉⌊Line chart of WordPress's mobile CWV passing rate gradually improving from below 30% to over 35%. There is a small drop between March and April 2023, annotated with "LCP algorithm slightly changed".⌉[ _This chart shows WordPress’s mobile CWV passing rate throughout the year. Note that the decline between March and April is not a result of a WordPress-specific problem (or any performance issue at all), but rather due to a change in how the LCP metric is being calculated, which was rolled out in that month._ Let’s take a closer look at the individual metrics that make up CWV and how they changed this year. For simplicity, only the mobile numbers are shown below. They are slightly more important than desktop results since mobile traffic overall is higher than desktop traffic. More importantly, performance improvements carry more importance for mobile devices as they are typically less powerful and are subject to worse network conditions. It is also worth noting that the corresponding desktop numbers don’t show any notable differences in trend. * Mobile LCP passing rate improved **8.89%** (from 34.48% to 43.37%). * Mobile CLS passing rate improved **4.22%** (from 74.76% to 78.98%). * Mobile FID passing rate improved **0.87%** (from 96.55% to 97.42%). As you can see, LCP saw by far the largest boost. This is an excellent outcome, as improving LCP was the main focus for the WordPress performance team this year. The rationale behind this may also be obvious when looking at the base values: The LCP passing rate of WordPress sites is the lowest performing metric, so it deserves the most attention. On the flip side, even though FID only improved by less than 1%, that is perfectly fine given its passing rate is already so high. Based on these metrics, it can furthermore be concluded that LCP was the primary driver behind the overall CWV passing rate improvements, which confirms the focus on this metric has made sense. Last but not least, the [Time to First Byte (TTFB)](https://web.dev/articles/ttfb) passing rate should be highlighted as well: While TTFB is not a Core Web Vitals metric, it is a direct part of LCP (specifically denoting its server-side load time performance portion), and it was another partial focus this year both because of its impact on LCP and because its passing rate is very low. Here is how it improved this year: * Mobile TTFB passing rate improved **3.10%** (from 18.67% to 21.77%). * Desktop TTFB passing rate improved **3.53%** (from 28.44% to 31.97%). ## **WordPress 2023 releases impact** This section focuses on the load time performance impact of the three new WordPress versions released this year, 6.2, 6.3, and 6.4. Since the focus for all of these releases was load time performance, it is sufficient to focus solely on LCP and TTFB. While the overarching WordPress metrics from the previous section were based on a broad year-over-year comparison, the metrics to assess the release impact were queried with a more granular approach: For each WordPress version, a dataset was established between two months based on only the intersection of sites that were on the previous WordPress version in the first month and on the newer WordPress version in the second month. The months were then chosen in a way to maximize the size of the dataset (e.g. a WordPress version always sees the highest usage in the month before the subsequent version is released). While that approach is still by no means an A/B comparison, it eliminates at least a good portion of noise e.g. from sites on other WordPress versions or sites that newly entered or dropped out of the dataset. ### **WordPress 6.2 LCP and TTFB** All metric comparisons are based on the intersection of WordPress 6.1 sites in March and WordPress 6.2 sites in July. [See relevant WordPress 6.2 slide.](https://docs.google.com/presentation/d/1iN2PL3yLvztEt3FYzI5eO7bLjUJL_5t-xsdGHNj7QLA/edit#slide=id.g1459556dc91_0_34) * Mobile LCP passing rate improved 0.01% (from 34.98% to 34.99%). * Mobile TTFB passing rate improved 0.65% (from 18.47% to 19.12%). * Desktop LCP passing rate improved 2.13% (from 46.85% to 48.98%). * Desktop TTFB passing rate improved 3.89% (from 25.79% to 29.68%). ### **WordPress 6.3 LCP and TTFB** All metric comparisons are based on the intersection of WordPress 6.2 sites in July and WordPress 6.3 sites in October. [See relevant WordPress 6.3 slide.](https://docs.google.com/presentation/d/1iN2PL3yLvztEt3FYzI5eO7bLjUJL_5t-xsdGHNj7QLA/edit#slide=id.g262a1a6a054_1_9) * Mobile LCP passing rate improved 4.72% (from 34.46% to 39.18%). * Mobile TTFB passing rate improved 0.78% (from 18.78% to 19.56%). * Desktop LCP passing rate improved 1.96% (from 48.55% to 50.51%). * Desktop TTFB passing rate decreased 2.15% (from 29.28% to 27.13%). ### **WordPress 6.4 LCP and TTFB** All metric comparisons are based on the intersection of WordPress 6.3 sites in October and WordPress 6.4 sites in November (since newer data is not available yet). [See relevant WordPress 6.4 slide.](https://docs.google.com/presentation/d/1iN2PL3yLvztEt3FYzI5eO7bLjUJL_5t-xsdGHNj7QLA/edit#slide=id.g262a1a6a054_1_19) * Mobile LCP passing rate improved 0.30% (from 37.40% to 37.70%) * Mobile TTFB passing rate improved 0.11% (from 18.21% to 18.32%). * Desktop LCP passing rate improved 0.13% (from 49.46% to 49.59%). * Desktop TTFB passing rate decreased 0.31% (from 25.88% to 25.57%). Remember that all of the above metrics are just indicators and an approximation of the field impact of those releases, influenced by several factors. It’s also great to keep in mind that the adoption of those versions will continue to grow. For example, as of November ~68% of all WordPress sites were using version 6.2 or newer based on the dataset. As the adoption increases further, the performance wins from those releases will continue to scale horizontally and benefit more sites. ## **WordPress 2023 impact on the web** WordPress, with its high usage, has a large footprint on the web, making a significant impact on the entire internet. When WordPress performance improves, the web’s performance improves. Therefore, last but not least, let’s look at the performance impact that WordPress has had on the web overall. A good starting point for that is to compare the 2023 CWV passing rate improvement of all WordPress sites with that of all sites _not_ using WordPress: * As mentioned before, WordPress’s mobile CWV passing rate improved 8.13%. * The non-WordPress mobile CWV passing rate improved by 3.68%. * Similarly as mentioned before, WordPress’s desktop CWV passing rate improved 8.25%. * The non-WordPress desktop CWV passing rate improved by 5.29%. From those numbers alone, it is clear that WordPress has made notably more progress in performance than the rest of the web, which is an amazing achievement. It is furthermore possible to draw some conclusions on _how much_ WordPress’s impact on the overall web’s improvements are. For reference, the overall web’s CWV passing rate improved 5.35% on mobile and 6.26% on desktop. Based on that, a simple calculation can be used, subtracting the non-WordPress CWV passing rate improvement from that of the entire web. This leads to the following results: * **1.67% of the overall web’s mobile CWV improvement of 5.35% comes directly from WordPress.** * **0.97% of the overall web’s desktop CWV improvement of 6.26% comes directly from WordPress.** While those numbers may seem small, this is literally WordPress’s impact on CWV for the entire web! It is an excellent reminder of how important WordPress’s role is for the web and how contributing to WordPress not only improves the WordPress ecosystem but also the entire web. ## **Considerations for 2024** With this recap of the 2023 CWV impact of WordPress, it is time to look ahead and plan for 2024. In particular there are two important considerations for the performance focus next year. ### **INP replaces FID as a Core Web Vitals metric** Earlier this year, a notable [change to the CWV metrics was announced](https://developers.google.com/search/blog/2023/05/introducing-inp): The more recently introduced metric [Interaction to Next Paint (INP)](https://web.dev/articles/inp) will replace First Input Delay (FID) in early 2024. Please refer to the linked articles for additional information on the metric and that change. The very short summary is that INP measures interactivity more accurately than FID, and due to its limitations FID ended up having very high passing rates throughout the web ecosystem – almost perfect as seen in the WordPress numbers before. [⌊The INP metric and its "good" threshold of 200ms or lower⌉⌊The INP metric and its "good" threshold of 200ms or lower⌉[ _This visualization shows the new INP metric and its thresholds._ Since INP measures interactivity more comprehensively than FID, it implies that passing the INP assessment is more difficult than passing the FID assessment. In other words, the INP passing rate is expected to be lower than the FID passing rate. Once INP is taken into account for CWV instead of FID, this will therefore lead to a decline in the overall CWV passing rate as well. In reality, the difference is particularly relevant on mobile devices. Here is a comparison of the FID passing rate and INP passing rate of WordPress sites, based on October 2023: * Mobile FID passing rate is 97.42%, while mobile INP passing rate is 71.48%. * Desktop FID passing rate is 99.97%, while desktop INP passing rate is 98.47%. While there is a small decline on desktop, it isn’t really worth focusing on as the value is still extremely good. But for mobile, the decline is significant. In other words, it will be important in 2024 to find ways in which WordPress can improve INP passing rates on mobile, in order to make up for the loss compared to FID. Of course this is not only relevant for WordPress, but for the entire web. Here is how the mobile CWV passing rate would change if INP was already replacing FID today (data based on October 2023): * WordPress’s mobile CWV passing rate would be 3.64% lower (32.80% instead of 36.44%). * The non-WordPress mobile CWV passing rate would be 7.39% lower (40.58% instead of 48.02%). Based on these numbers, it is at least a little comforting that WordPress will struggle with this change less than the rest of the web. Nevertheless, 3.64% CWV passing rate decline is a significant drop, so part of next year’s performance goals will be to make up for that loss, likely through a combination of INP focused improvements and a continuation of the LCP focused efforts. ### **TTFB focus was less impactful than (client-side) LCP focus** The second consideration for 2024 is not related to a metric change, but rather a potential takeaway from the 2023 metrics highlighted in this post: When looking at the WordPress release specific impact, it can be noted that the mobile LCP improvement was by far the highest in the 6.3 release (4.72%, compared to <1% for 6.2 and 6.4). The WordPress 6.3 release included a number of client-side LCP enhancements, which likely led to a large chunk of those improvements, as more granularly indicated by the [findings from the related field analysis](https://make.wordpress.org/core/2023/09/19/analyzing-the-core-web-vitals-performance-impact-of-wordpress-6-3-in-the-field/) from a few months ago. WordPress 6.4 and especially WordPress 6.2 were more focused on server-side LCP enhancements (i.e. TTFB enhancements), and based on the field results those releases did not lead to as large LCP wins. Even for TTFB, the picture isn’t entirely clear: As expected, WordPress 6.2 has a much better TTFB win than 6.3 on desktop, but on mobile devices the two releases show almost equal TTFB wins, with 6.3 even slightly higher. While those numbers are by no means evidence, they raise the question whether the TTFB focus in WordPress core is the right way to move the needle for load time performance. Potentially the influence of other factors outside of WordPress core on TTFB, such as plugins, themes, hosting stack, or network connection, are just too large for the core-specific server-side improvements to make an impact in the field. This does not imply the TTFB efforts should be dropped – but likely a shift is needed. Potentially, the TTFB issues need to be addressed through other means than directly enhancing the server response time of WordPress core itself. Further research should likely be conducted to get a better understanding of how much WordPress’s low TTFB passing rate stems from the pluginPlugin 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. ecosystem’s performance or other aspects not directly code-related such as hosting. ## **2024 planning is underway** The WordPress performance team is currently working on their roadmap for 2024. A [GitHub issue for performance focused project proposals](https://github.com/WordPress/performance/issues/903) has been opened and awaiting input. You’re invited to contribute any WordPress performance related proposals or ideas you may have on that issue. While the 2024 roadmap is currently being planned, let’s once again circle back to 2023: The amazing metrics shared here speak for themselves. Thank you to everyone who contributed to WordPress’s incredible performance impact in 2023! _Props to [@annezazu](https://profiles.wordpress.org/annezazu/) [@westonruter](https://profiles.wordpress.org/westonruter/) for review and proofreading._ [#analysis](https://make.wordpress.org/core/tag/analysis/), [#core-web-vitals](https://make.wordpress.org/core/tag/core-web-vitals/), [#core-performance](https://make.wordpress.org/core/tag/core-performance/), [#performance](https://make.wordpress.org/core/tag/performance/) [ ](https://profiles.wordpress.org/clarkeemily/) [Emily Clarke](https://profiles.wordpress.org/clarkeemily/) 10:25 am _on_ December 19, 2023 Tags: [agenda ( 1,136 )](https://make.wordpress.org/core/tag/agenda/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [performance ( 411 )](https://make.wordpress.org/core/tag/performance/), [performance-chat ( 338 )](https://make.wordpress.org/core/tag/performance-chat/) # 󠀁[Performance Chat Agenda: 19 December 2023](https://make.wordpress.org/core/2023/12/19/performance-chat-agenda-19-december-2023/)󠁿 Here is the agenda for this week’s performance team meeting scheduled for [Dec 19, 2023 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231219T1600). If you have any topics you’d like to add to this agenda, please add them in the comments below. * **Announcements** - Welcome to our new members of [#core-performance](http://wordpress.slack.com/messages/core-performance/) - Call for 2024 roadmap priorities https://github.com/WordPress/performance/ issues/903 - Reminder there will be no SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) meeting on Tuesday December 26 * **Priority projects ** - [Server response time](https://make.wordpress.org/performance/roadmap-2023/#category-server-response-time) - [Database optimization](https://make.wordpress.org/performance/roadmap-2023/#category-database-optimization) - [JavaScript & CSS](https://make.wordpress.org/performance/roadmap-2023/#category-javascript-css) * - [Images](https://make.wordpress.org/performance/roadmap-2023/#category-images) - [Measurement](https://make.wordpress.org/performance/roadmap-2023/#category-measurement) - [Ecosystem tools](https://make.wordpress.org/performance/roadmap-2023/#category-ecosystem-tools) - [Creating standalone plugins](https://github.com/WordPress/performance/issues/656) - New projects / proposals * **Open floor** --- _This meeting happens in the [#core-performance](http://wordpress.slack.com/messages/core-performance/) channel. To join the meeting, you’ll need an account on the [Make WordPress Slack](https://make.wordpress.org/chat/)_. [#agenda](https://make.wordpress.org/core/tag/agenda/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#performance](https://make.wordpress.org/core/tag/performance/), [#performance-chat](https://make.wordpress.org/core/tag/performance-chat/) [ ](https://profiles.wordpress.org/webcommsat/) [Abha Thakor](https://profiles.wordpress.org/webcommsat/) 10:34 am _on_ December 16, 2023 Tags: [dev-blog ( 10 )](https://make.wordpress.org/core/tag/dev-blog/), [summary ( 972 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev Blog editorial meeting summary, December 14, 2023](https://make.wordpress.org/core/2023/12/16/dev-blog-editorial-meeting-summary-december-14-2023/)󠁿 Summary of the WordPress Developer Blogblog (versus network, site) meeting which took place in the  [#core-dev-blog](https://wordpress.slack.com/archives/C03RL47B3S8) channel on the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). [Start](https://wordpress.slack.com/archives/C03RL47B3S8/p1702558941890859) of the meeting in Slack. Attendees: [@bph](https://profiles.wordpress.org/bph/), [@marybaum](https://profiles.wordpress.org/marybaum/), [@ndiego](https://profiles.wordpress.org/ndiego/), [@webcommsat](https://profiles.wordpress.org/webcommsat/), [@greenshady](https://profiles.wordpress.org/greenshady/), [@ironnysh](https://profiles.wordpress.org/ironnysh/). Apologies: [@milana_cap](https://profiles.wordpress.org/milana_cap/) Last meeting links: [summary from last meeting on November 2, 2023](https://make.wordpress.org/core/2023/11/17/developer-blog-editorial-meeting-summary-november-2/)– props to [@milana_cap](https://profiles.wordpress.org/milana_cap/) for facilitating and [@webcommsat](https://profiles.wordpress.org/webcommsat/) for the summary. ## **Updates on the Developer Blog site**  1. Central documentation area 2. * Following up on a previous discussion for a central area for documentation for writers, reviewers and admins, [@bph](https://profiles.wordpress.org/bph/) has opened the [Wiki space on the GitHub Repository.](https://github.com/WordPress/developer-blog-content/wiki) This will put all the little details into one place and an excellent way to organize the pieces. * In early 2024, she will provide a tracking issue for all the updates and new docs that need to be added, and a request for a few of the editorial group to assist in writing and reviewing.  3. Redesign 4. * The Developer Blog is part of the [Redesigning Developer Resources and a call for testing](https://make.wordpress.org/meta/2023/11/22/redesigning-developer-resources-and-a-call-for-testing/). * [@ndiego](https://profiles.wordpress.org/ndiego/) has addressed some MetaMeta Meta 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. feedback on the [PR](https://github.com/WordPress/wporg-developer-blog/pull/47) yesterday, and it is nearly complete. This update will standardize the Blog to match the pending updates to Developer Resources and provide a solid platform for additional iterations in the future. He highlighted this update will make easier future updates. By using a 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 consistent API and user experience. theme, future changes to the templates can be done more easily and directly. In addition, the Blog will inherit all the new functionality that has been developed for the Developer Resources site, such as, consistent spacing sizes, font sizes, local navigation, etc. Any further feedback is welcome. * The meeting thanked [@ndiego](https://profiles.wordpress.org/ndiego/), the Meta team and all involved for all their work on this. * Latest start of production expected early next week. Developer Resources will launch first, then the Blog updates. Further updates can be followed in the [#website-redesign](https://wordpress.slack.com/archives/C04U953K77A) channel on Slack.  ## Project board and status [Project Board](https://github.com/orgs/WordPress/projects/44/views/1) on the Blog repo in GitHubGitHub GitHub 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/](https://github.com/). ### New posts Six new Posts** **published since the last editorial meeting. * [What’s new for developers? (November 2023)](https://developer.wordpress.org/news/2023/11/10/whats-new-for-developers-november-2023/) by Justin Tadlock and Birgit Pauli-Haack. * [Getting started with the Command Palette API](https://developer.wordpress.org/news/2023/11/20/getting-started-with-the-command-palette-api/) by Justin Tadlock. For feedback and review: [@dansoschin](https://profiles.wordpress.org/dansoschin/), [@bph](https://profiles.wordpress.org/bph/), [@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/), and [@richtabor](https://profiles.wordpress.org/richtabor/)  * [A great read—four simple steps to your best body copy ever](https://developer.wordpress.org/news/2023/12/01/a-great-read-four-simple-steps-to-your-best-body-copy-ever/) by Mary Baum. Justin Tadlock, Abha Thakor, and Birgit Pauli-Haack for input and editing. * [Styles, patterns, and more with the Details block](https://developer.wordpress.org/news/2023/12/01/styles-patterns-and-more-with-the-details-block/) by Justin Tadlock. Mary Baum, Birgit Pauli-Haack for input and feedback. * [A walk-through tutorial on using Create Block Theme plugin](https://developer.wordpress.org/news/2023/12/05/a-walk-through-tutorial-on-using-create-block-theme-plugin/) by Ganesh Dahal. _Editors Birgit Pauli-Haack and Abha Thakor_, and Justin Tadlock for input * [What’s new for developers? (December 2023)](https://developer.wordpress.org/news/2023/12/10/whats-new-for-developers-december-2023/) which was a collaborative writing exercise with Justin Tadlock, Ryan Welcher, Nick Diego, JuanMa Garrido and Birgit Pauli-Haack. * [Tutorial on building patterns and block styles with Details/Summary block](https://developer.wordpress.org/news/2023/12/styles-patterns-and-more-with-the-details-block/) by Justin Tadlock. Feedback and reviews Mary Baum, Birgit Pauli-Haack, and Nick Diego. [@bph](https://profiles.wordpress.org/bph/) said: “A huge **thank you** to the writers, and their reviewers!! Fantastic job!” _Actions: _ * Proposed by [@webcommsat](https://profiles.wordpress.org/webcommsat/) to include co-authors, editors and detailed reviewers names in this list in future meetings/ summary to reflect their input and time. This will also help to encourage more people to volunteer their skills to review, edit and writers to work together on a post. [@marybaum](https://profiles.wordpress.org/marybaum/) and others confirmed the time commitment for a co-author or editor can be considerable, and this can be reflected in the inclusion of their WordPress.orgWordPress.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/](https://wordpress.org/) ID. The inclusion of this additional detail was agreed to be added at the meeting. In the existing checklist, the principal writer of a post adds props to those who have been involved in the props channel on Slack. * Suggestions for people who are good copy editors from other WordPress contributor teams to be shared with [@bph](https://profiles.wordpress.org/bph/) for onboarding in 2024 when some additional documentation on expectations and tools is ready. ### **Posts in progress** In this and the following sections of the meeting summary, the links go to the WordPress Developer Blog repo on GitHub. * [Working with custom slotfills](https://github.com/WordPress/developer-blog-content/issues/146) * [New developer focused workflow article about how the login and registration works in WordPress.](https://github.com/WordPress/developer-blog-content/discussions/159) * [Optimizing your WP_Query queries for better performance](https://github.com/WordPress/developer-blog-content/issues/128) * [A tutorial about the highlights of the browser and focus modes of the Navigation Block](https://github.com/WordPress/developer-blog-content/issues/149) * [What’s new for developers? (January 2024) #179](https://github.com/WordPress/developer-blog-content/issues/179) ### **To-do list** * [Using the Grid layout type for theme creators](https://github.com/WordPress/developer-blog-content/discussions/94) * [How to manage block governance](https://github.com/WordPress/developer-blog-content/issues/126) * [Tutorial on building block-based templates in classic themes](https://github.com/WordPress/developer-blog-content/issues/116) * [How to disable specific blocks in WordPress](https://github.com/WordPress/developer-blog-content/issues/148) * [Creating a custom External Template for the @wordpress/create-block package](https://github.com/WordPress/developer-blog-content/discussions/161) * [Overview of the coding standards tooling available to WordPress developers](https://github.com/WordPress/developer-blog-content/discussions/160) * [An overview of the Block Hooks feature](https://github.com/WordPress/developer-blog-content/discussions/162) In the last few months there has been a slowing down of writing and reviewing, due to contributors’ other demands, the release, and their own work commitments. Increasing the number of volunteers in these areas will help address this. Action, as above, on identifying good copy editors from other teams. _Actions: _ * As Dev Chat has now concluded for 2023 and will be back in the second week of 2024, instead of [@webcommsat](https://profiles.wordpress.org/webcommsat/) sharing the monthly call out of posts that need writers in that meeting, it was agreed to wait until the next editorial meeting on January 4, 2024.  * [@webcommsat](https://profiles.wordpress.org/webcommsat/) will include a link to the summary of the meeting in a comment on the Dev Chat summary when published. ### Future topic ideas for approval Many new ideas for topics have come through or are in the pipeline. They are not all ready to proceed. All the topics below were given a positive vote. Further scoping and drafting to follow. Any other comments can be added on the individual GitHub tickets listed. * [Create Figma designs for WordPress Block Theme #175](https://github.com/WordPress/developer-blog-content/issues/175) * [Introduction on using Gutenberg components for plugin pages #183](https://github.com/WordPress/developer-blog-content/discussions/183) * [Tutorial: Creating a mega menu with the block system](https://github.com/WordPress/developer-blog-content/discussions/182) * Discussion on idea: [#182 Tutorial: Creating a mega menu with the block system](https://github.com/WordPress/developer-blog-content/discussions/182) - This represents initial thinking on this area. There are no easy ways to create mega menus in the block system or in classic theming. - Some questions to consider: * are mega menus possible with the block system? * if so, can we build something that’s user friendly with the tools at hand? * if so, can we explain this through a tutorial? * [Adding a “screen reader text” block option via themes](https://github.com/WordPress/developer-blog-content/discussions/181) * [Tutorial: Adding Starter Page and Template Patterns](https://github.com/WordPress/developer-blog-content/discussions/180) * [Dev Blog: 2023 Year in Review](https://github.com/WordPress/developer-blog-content/discussions/176) - Ideas for the article are welcome. - [@greenshady](https://profiles.wordpress.org/greenshady/) is aiming for this to be ready as a draft in the first week of January 2024. * [A first look at the Interactivity API #141](https://github.com/WordPress/developer-blog-content/discussions/141) - A note on the Interactivity APIAPI 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., that topic was on the list since May, but only now the Interactivity API will become a public API with the 6.5 WordPress release. * [Pitfalls working with @wordpress/data, useSelect and useDispatch and how to avoid those. #184](https://github.com/WordPress/developer-blog-content/discussions/184) * [Tutorial on using create-block scaffolding to write a multi-block plugin #186](https://github.com/WordPress/developer-blog-content/discussions/186) **Discussion on advance review of the approval list:** * the list is now shared in the agenda reminder earlier on the day of the meeting; however, this may not give non-sponsored contributors or those in other timezones or unable to read the items that day the ability to comment most usefully or raise questions * the topic areas are available on the GitHub repo as live tickets and can be reviewed there at any time of the month, and comments added in advance of the Editorial meeting * the aim is to encourage some discussion of those topics and to flesh out an article and identify different angles * Actions: - agreed for a link to new topics to be shared regularly in the Dev Blog slack channel to raise awareness and interest in the topics and potential writers stepping forward - to encourage those putting ideas together to have them on the GitHub project board by a certain date (if possible) before each meeting. It may not always be possible, but in principle, encouraging this will improve the process, a more informed discussion, allow for more asynchronous contributions, and a way of encouraging engagement in the channel and discussion on GitHub.  ## Open floor 1. Idea for a potential post: [@marybaum](https://profiles.wordpress.org/marybaum/)–“ From no-code to no-hands: three ways to generate posts in a taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. [https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies). term” case study 2. * [Link to more details in Slack.](https://wordpress.slack.com/archives/C03RL47B3S8/p1702562000416349) * This will be expanded in a more detailed scope in the GitHub repo. 3. [@webcomms](https://profiles.wordpress.org/webcomms/) raised a previous discussion in the Slack channel. She, like many others in the group, receives requests from developers wanting to know what order to learn WordPress development, tips to help become or familiarize with WP development, etc. 4. * Actions: for a discussion to be created in GitHub spaces. * It fits our scope * Similar posts to be identified from the Dev Blog * This will fit well with the discussion of learning paths, the Training team is tackling.. ## Next meeting The next Developer Bog editorial group meeting will be on [January 4, 2024, at 13:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240104T1300) in the [#core-dev-blog](https://wordpress.slack.com/archives/C03RL47B3S8) channel. [#dev-blog](https://make.wordpress.org/core/tag/dev-blog/), [#summary](https://make.wordpress.org/core/tag/summary/) # Post navigation [← Older posts](https://make.wordpress.org/core/2023/page/2/?output_format=md)