Title: 2024 – Make WordPress Core --- # Yearly Archives: 2024 [ ](https://profiles.wordpress.org/joemcgill/) [Joe McGill](https://profiles.wordpress.org/joemcgill/) 5:09 pm _on_ December 23, 2024 Tags: [6-8 ( 91 )](https://make.wordpress.org/core/tag/6-8/), [core ( 730 )](https://make.wordpress.org/core/tag/core/), [dev chat ( 908 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 970 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Summary, Dev Chat, December 18, 2024](https://make.wordpress.org/core/2024/12/23/summary-dev-chat-december-18-2024/)󠁿 This meeting was the final Dev Chat for 2024. [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1734552045775529) of the meeting in 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/), facilitated by [@mikachan](https://profiles.wordpress.org/mikachan/). 🔗 [Agenda post](https://make.wordpress.org/core/2024/12/17/agenda-dev-chat-dec-18-2024/). ## Announcements The [Nominations for 2025’s Core Team Reps](https://make.wordpress.org/core/2024/12/17/nominations-for-core-team-reps-2025-edition/) are now open! Please nominate people in the comments of that post. Self-nominations are welcome. The deadline is January 31, 2025. Also, 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/) 19.9 was released prior to the start of the meeting. See, [What’s new in Gutenberg 19.9?](https://make.wordpress.org/core/2024/12/18/whats-new-in-gutenberg-19-9-19-december/) ## Forthcoming releases ### Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8 The WordPress 6.8 [call for volunteers](https://make.wordpress.org/core/2024/11/21/wordpress-6-8-call-for-volunteers/) closed on Dec 6. There will be more information about the release squad to follow soon based on these volunteers. ### Next maintenance release: 6.7.2 There is currently no release date planned for WordPress 6.7.2. You can review [the next minor release milestone](https://core.trac.wordpress.org/tickets/minor). The 6.7.2 milestone was scrubbed during the week and the Gutenberg board is scrubbed [with only a few PRs](https://wordpress.slack.com/archives/C07BTF54N68/p1734910548729679) that need to be merged. ## Discussion There were no discussion topics for this meeting. ## Open Floor [@luminuu](https://profiles.wordpress.org/luminuu/) raised the following on the agenda post: > how much work would it be to allow pseudo-styles on 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. style variations, > for example on buttons? Talking about this issue: [https://github.com/WordPress/gutenberg/issues/55359](https://github.com/WordPress/gutenberg/issues/55359) [@mikachan](https://profiles.wordpress.org/mikachan/) noted a similar issue being worked on for the stylebook: [https://github.com/WordPress/gutenberg/issues/38277](https://github.com/WordPress/gutenberg/issues/38277). [#6-8](https://make.wordpress.org/core/tag/6-8/), [#core](https://make.wordpress.org/core/tag/core/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/peterwilsoncc/) [Peter Wilson](https://profiles.wordpress.org/peterwilsoncc/) 9:20 pm _on_ December 19, 2024 Tags: [release ( 32 )](https://make.wordpress.org/core/tag/release/) # 󠀁[Change of Coordinator title in Release Squads](https://make.wordpress.org/core/2024/12/19/change-of-coordinator-title-in-release-squads/)󠁿 For the past several years, WordPress has been using a[ consistent set of titles for release squad members](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/). Going forward the Release Coordinator role will become Release Coordination as the latter easier to translate reliably and neutrally in languages with gendered nouns. The “… Lead” roles will remain unchanged. This change is a result of a discussion on ticketticket Created for both bug reports and feature development on the bug tracker. [#62386](https://core.trac.wordpress.org/ticket/62386) to explore adding missing release squad titles to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. This will allow every release squad member to be celebrated accurately with their corresponding title on the credits page within the WordPress dashboard and through the [WordPress.org](http://WordPress.org) Credits 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.. Props [@desrosj](https://profiles.wordpress.org/desrosj/) and [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) for reviewing this post. [#release](https://make.wordpress.org/core/tag/release/) [ ](https://profiles.wordpress.org/ramonopoly/) [ramonopoly](https://profiles.wordpress.org/ramonopoly/) 8:28 am _on_ December 18, 2024 Tags: [block-editor ( 135 )](https://make.wordpress.org/core/tag/block-editor/), [core-editor ( 751 )](https://make.wordpress.org/core/tag/core-editor/), [gutenberg ( 542 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-new ( 211 )](https://make.wordpress.org/core/tag/gutenberg-new/)    # 󠀁[What’s new in Gutenberg 19.9? (19 December)](https://make.wordpress.org/core/2024/12/18/whats-new-in-gutenberg-19-9-19-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 ([#gutenberg-new](https://make.wordpress.org/core/tag/gutenberg-new/)) appear on a biweekly basis after every Gutenberg release, and showcase the latest features and improvements.  Interested in learning more? [Here’s an overview](https://make.wordpress.org/core/2020/05/20/ways-to-keep-up-with-full-site-editing-fse/) of how you can keep up with news and events related to Gutenberg and the 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. Editor. --- [[ [Gutenberg 19.9](https://github.com/WordPress/gutenberg/releases/tag/v19.9.0) is out of the oven and ready to [download](https://wordpress.org/plugins/gutenberg/). The last release of 2024 introduces the Style Book to classic themes, a new Query Total block, a swathe of component library enhancements, and code quality improvements. **Table of contents** 1. [Style Book in classic themes](https://make.wordpress.org/core/2024/?output_format=md#style-book-in-classic-themes) 2. [Introducing the Query Total block](https://make.wordpress.org/core/2024/?output_format=md#introducing-the-query-total-block) 3. [More Highlights](https://make.wordpress.org/core/2024/?output_format=md#more-highlights) 4. [Changelog](https://make.wordpress.org/core/2024/?output_format=md#changelog) 5. [First-time contributors](https://make.wordpress.org/core/2024/?output_format=md#first-time-contributors) 6. [Contributors](https://make.wordpress.org/core/2024/?output_format=md#contributors) ## Style Book in classic themes The Style Book [now appears in supported classic themes](https://github.com/WordPress/gutenberg/pull/66851) under** Appearance > Design > Styles** in the adminadmin (and super admin) menu. Support is available for classic themes that either support editor styles via `add_theme_support(' editor-styles' )` or have a theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. file.  The Style Book provides a comprehensive overview of your site’s colors, typography, and block styles in an organized layout. Each block example and style group is labeled, making it easy to preview and understand your theme’s current design settings. Think of it as if your theme threw a party, and all the design elements showed up wearing name tags. 😀 For classic themes that support the Style Book, site patterns have been relocated to **Appearance > Design > Patterns**, consolidating all design-related functionality from the Site Editor into one place. Previously, patterns were listed under **Appearance > Patterns**.  Testing is an important step for this feature before it’s introduced to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. If you have the time, please help identify potential issues, and suggest areas for improvement by [logging your feedback](https://github.com/WordPress/gutenberg/issues/68036) 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/). Testing instructions can be found on the [original PR](https://github.com/WordPress/gutenberg/pull/66851). Thank you! ## Introducing the Query Total block You know how many results are in your queries, but do your site’s readers? The new [Query Total block](https://github.com/WordPress/gutenberg/pull/67629) is here to help. [[ When added within a 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) block, the Query Total block displays the number of results the query has returned, or, alternatively, the current range in a set of paginated results. ## More Highlights Gutenberg 19.9 introduces phpMyAdmin to wp-env as a launch option. phpMyAdmin will automatically connect to the running mysqlMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. [https://www.mysql.com](https://www.mysql.com/) database service, allowing you to inspect and manage the local WordPress database as you develop. ([#67588](https://github.com/WordPress/gutenberg/pull/67588)). Featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. backgrounds in the Cover block now come with resolution controls so that you can change their sizes ([#67273](https://github.com/WordPress/gutenberg/pull/67273)). Reset colors for blocks and global styles in the editor with a single click thanks to the inline reset button added to all color controls ([#67116](https://github.com/WordPress/gutenberg/pull/67116)). Looking to replace your Query block’s design? Query block patterns have been relocated from a modal to a dropdown. It’s still in the block toolbar, now under “Change design”( [#66993](https://github.com/WordPress/gutenberg/pull/66993)). You can now also set your site’s home page from within the Site Editor via the page actions menu ([#65426](https://github.com/WordPress/gutenberg/pull/65426)). This is the equivalent of updating the Reading Settings in **“Settings > Reading”**. Under “Pages” in the editor, find the page you’d like to set as your homepage, click on the action menu, and select ‘Set as homepage’. ## Changelog ### Enhancements * Feature: Add `navigation.isLoading` state to core/router store. ([67680](https://github.com/WordPress/gutenberg/pull/67680)) * Update the title, description, and order of Experiments page. ([67762](https://github.com/WordPress/gutenberg/pull/67762)) * wp-env: Add phpMyAdmin support. ([67588](https://github.com/WordPress/gutenberg/pull/67588)) #### Components * Added enableAlpha prop to CustomGradientPicker and GradientPicker components.( [66974](https://github.com/WordPress/gutenberg/pull/66974)) * BorderBoxControl: Reduce gap value when unlinked. ([67049](https://github.com/WordPress/gutenberg/pull/67049)) * DateTime: Add default date/time to stories. ([67678](https://github.com/WordPress/gutenberg/pull/67678)) * Deprecate `COLORS.white`. ([67649](https://github.com/WordPress/gutenberg/pull/67649)) * Disabled: Suppress `contentEditable` warning in story. ([67679](https://github.com/WordPress/gutenberg/pull/67679)) * Document layout in Storybook. ([67628](https://github.com/WordPress/gutenberg/pull/67628)) * DropdownMenu: Increase option height to 40px. ([67435](https://github.com/WordPress/gutenberg/pull/67435)) * DuotonePicker: Simplify Button styles. ([66641](https://github.com/WordPress/gutenberg/pull/66641)) * Menu: Throw when subcomponents are not rendered inside top level Menu. ([67411](https://github.com/WordPress/gutenberg/pull/67411)) * Popover: Use `anchor` instead of `anchorRef` in story. ([67674](https://github.com/WordPress/gutenberg/pull/67674)) * Storybook: Remove unnecessary feature flags. ([67576](https://github.com/WordPress/gutenberg/pull/67576)) * Storybook: Update `ArgsTable` to `Controls` in preview. ([67582](https://github.com/WordPress/gutenberg/pull/67582)) * Storybook: Update control types from `null` to `undefined`. ([67581](https://github.com/WordPress/gutenberg/pull/67581)) * Storybook: Use manager-api instead of addons package. ([67578](https://github.com/WordPress/gutenberg/pull/67578)) * Update @ariakit/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/) to 0.4.13. ([65907](https://github.com/WordPress/gutenberg/pull/65907)) * Update @ariakit/react to 0.4.15 and @ariakit/test to 0.4.7. ([67404](https://github.com/WordPress/gutenberg/pull/67404)) #### Block Library * Cover Block: Image size option for featured image. ([67273](https://github.com/WordPress/gutenberg/pull/67273)) * Feature: Allow Post Template block to get deeply nested within Query Block. ( [67657](https://github.com/WordPress/gutenberg/pull/67657)) * Image Block: Change how the Image’s overlay styles are applied. ([67788](https://github.com/WordPress/gutenberg/pull/67788)) * Navigation: Enable all non-interactive formats. ([67585](https://github.com/WordPress/gutenberg/pull/67585)) * Query block: Move patterns modal to dropdown on block toolbar. ([66993](https://github.com/WordPress/gutenberg/pull/66993)) * Separator block: Allow divs to be used as separators. ([67530](https://github.com/WordPress/gutenberg/pull/67530)) * New Block: Add Query Total block for displaying total query results or ranges.( [67629](https://github.com/WordPress/gutenberg/pull/67629)) * Block Library: Update the relationship of `No results` block to `ancestor`. ( [48348](https://github.com/WordPress/gutenberg/pull/48348)) #### DataViews * Add 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. to the quick edit when bulk editing. ([67390](https://github.com/WordPress/gutenberg/pull/67390)) * Data views: Expand configuration drop down on mobile. ([67715](https://github.com/WordPress/gutenberg/pull/67715)) * Quick Edit: Add Template field. ([66591](https://github.com/WordPress/gutenberg/pull/66591)) * Refactor actions to render modal outside of the menu. ([67664](https://github.com/WordPress/gutenberg/pull/67664)) * Renders `DataForm` component only when data has been fetched. ([67694](https://github.com/WordPress/gutenberg/pull/67694)) * Unify layout configuration. ([67477](https://github.com/WordPress/gutenberg/pull/67477)) * Update bulk header with actions. ([67743](https://github.com/WordPress/gutenberg/pull/67743)) #### Style Book * Add stylebook screen for classic themes. ([66851](https://github.com/WordPress/gutenberg/pull/66851)) * Scroll to top at styles root. ([67605](https://github.com/WordPress/gutenberg/pull/67605)) * Stylebook: Render overview colors in 4 columns. ([67597](https://github.com/WordPress/gutenberg/pull/67597)) * Update style book headings to new design. ([67546](https://github.com/WordPress/gutenberg/pull/67546)) #### Post Editor * Inline Commenting: Added new 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. as extension of the canvas. ([67347](https://github.com/WordPress/gutenberg/pull/67347)) * Inline Commenting: Re-order the comments in sidebar in which blocks are listed.( [66927](https://github.com/WordPress/gutenberg/pull/66927)) * Inline commenting: UXUX User experience Enhancements for Comments. ([67385](https://github.com/WordPress/gutenberg/pull/67385)) #### Site Editor * Data Views: Add action for pages to set site homepage. ([65426](https://github.com/WordPress/gutenberg/pull/65426)) * Sidebar: Update appearance of active items. ([67318](https://github.com/WordPress/gutenberg/pull/67318)) * Style the selected template pattern. ([65917](https://github.com/WordPress/gutenberg/pull/65917)) #### Data Layer * Data: Expose ‘useSelect’ warning to third-party consumers. ([67735](https://github.com/WordPress/gutenberg/pull/67735)) * Data: Include more details when shallow equality fails in ‘useSelect’. ([67713](https://github.com/WordPress/gutenberg/pull/67713)) #### Global Styles * Controls in grid should match between sidebar panel and editor. ([67602](https://github.com/WordPress/gutenberg/pull/67602)) * Shadows: Improve design and a11yAccessibility 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) of remove button. ([67705](https://github.com/WordPress/gutenberg/pull/67705)) #### Block Editor * Prefer exact matches in Link Search results sorting. ([67367](https://github.com/WordPress/gutenberg/pull/67367)) * Try direct drag (outside text editable). ([67305](https://github.com/WordPress/gutenberg/pull/67305)) #### Zoom Out * Keep only copy, duplicate and delete in the zoom out more block toolbar menu item. ([67279](https://github.com/WordPress/gutenberg/pull/67279)) #### Font Library * FontCollection: Update pagination controls. ([67143](https://github.com/WordPress/gutenberg/pull/67143)) #### Colors * Add reset button to color control. ([67116](https://github.com/WordPress/gutenberg/pull/67116)) ### Bug Fixes * Exclude Set instance methods from polyfills. ([67230](https://github.com/WordPress/gutenberg/pull/67230)) * Preload: Fix settings fields order. ([67450](https://github.com/WordPress/gutenberg/pull/67450)) * Scripts: Make React Fast Refresh work with multiple blocks. ([64924](https://github.com/WordPress/gutenberg/pull/64924)) * WP Scripts: Update webpack dependencies related to styling. ([67572](https://github.com/WordPress/gutenberg/pull/67572)) #### Site Editor * Allow access to quick edit. ([67469](https://github.com/WordPress/gutenberg/pull/67469)) * Edit Site: Fix sidebar template author navigation. ([67382](https://github.com/WordPress/gutenberg/pull/67382)) * Fix Site editor navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. items alignment visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/2024/?output_format=md#blocker). Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.. ([67321](https://github.com/WordPress/gutenberg/pull/67321)) * Fix sidebar item animation regression. ([67771](https://github.com/WordPress/gutenberg/pull/67771)) * Fix sidebar plugins. ([67557](https://github.com/WordPress/gutenberg/pull/67557)) * Fix the templates route on mobile. ([67547](https://github.com/WordPress/gutenberg/pull/67547)) * Fix: Fixed site-editor crashing when added front-page template and clicking more option. ([67500](https://github.com/WordPress/gutenberg/pull/67500)) * Fix: Fixed styling tab not opening on themes without style variations on mobile& desktop. ([67537](https://github.com/WordPress/gutenberg/pull/67537)) * Preload: Parse post ID from p (path). ([67465](https://github.com/WordPress/gutenberg/pull/67465)) * Remove default page slug. ([67673](https://github.com/WordPress/gutenberg/pull/67673)) * Router: Fix addition and removal of empty classnames. ([67378](https://github.com/WordPress/gutenberg/pull/67378)) * Wrap each router area in ‘ErrorBoundary’. ([64245](https://github.com/WordPress/gutenberg/pull/64245)) * useEditorTitle: Fix wrong request without ID. ([67475](https://github.com/WordPress/gutenberg/pull/67475)) #### Block Editor * Animate `useScaleCanvas()` only when toggling zoomed out mode. ([67481](https://github.com/WordPress/gutenberg/pull/67481)) * Drag and drop: Fix drop zones on block drag. ([67317](https://github.com/WordPress/gutenberg/pull/67317)) * Drag and drop: Fix firefox compat logic. ([67439](https://github.com/WordPress/gutenberg/pull/67439)) * Fix JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. error in the ‘useTabNav’ hook. ([67102](https://github.com/WordPress/gutenberg/pull/67102)) * FontFamilyControl: Restore margin bottom. ([67424](https://github.com/WordPress/gutenberg/pull/67424)) * Inserter: Hide child blocks from the inserter when needed. ([67734](https://github.com/WordPress/gutenberg/pull/67734)) * Inserter: Patterns: Remove loading indicator. ([67072](https://github.com/WordPress/gutenberg/pull/67072)) * Inserter: Should receive focus on open. ([67754](https://github.com/WordPress/gutenberg/pull/67754)) * Remove words count in the multi-selection inspector. ([67624](https://github.com/WordPress/gutenberg/pull/67624)) * Storybook: Fix `BlockPatternsList` fixtures. ([67672](https://github.com/WordPress/gutenberg/pull/67672)) * Drag and drop: Fix misplaced drop indicator. ([67434](https://github.com/WordPress/gutenberg/pull/67434)) * Drag and drop: Fix scroll disorientation after drop. ([67405](https://github.com/WordPress/gutenberg/pull/67405)) * Drag and drop: Restore moving animation. ([67417](https://github.com/WordPress/gutenberg/pull/67417)) #### Block Library * Align Submenu block and Nav Link block by including description and wrapping span. ([67198](https://github.com/WordPress/gutenberg/pull/67198)) * CommentsPagination: Set font-size to inherit for pagination items. ([67296](https://github.com/WordPress/gutenberg/pull/67296)) * Fix latest post block spacing issue. ([66442](https://github.com/WordPress/gutenberg/pull/66442)) * Fix: Caption with Link in Wide-Width and Full-Width Images Appears on two lines.( [67392](https://github.com/WordPress/gutenberg/pull/67392)) * Fix: Don’t show `aria-label` when its value is empty. ([67381](https://github.com/WordPress/gutenberg/pull/67381)) * Navigation Block: Fix issue with double-clicking “Create a new menu” causing duplicate menus. ([67488](https://github.com/WordPress/gutenberg/pull/67488)) * Pullquote block having design issue when text-decoration is choosen strikethrough.( [66707](https://github.com/WordPress/gutenberg/pull/66707)) * Remove inline-block display from image anchor in style.scss. ([67368](https://github.com/WordPress/gutenberg/pull/67368)) * Search block: Add space between attributes when using “Button only” option. ( [61399](https://github.com/WordPress/gutenberg/pull/61399)) * Updated ‘Set featured image’ text in dropdown. ([67775](https://github.com/WordPress/gutenberg/pull/67775)) #### DataViews * Avoid double click handler on primary fields. ([67393](https://github.com/WordPress/gutenberg/pull/67393)) * Better handling of missing onClickItem prop. ([67402](https://github.com/WordPress/gutenberg/pull/67402)) * Fix filters lost when switching layouts. ([67740](https://github.com/WordPress/gutenberg/pull/67740)) * Fix hidden List layout actions dropdown. ([67778](https://github.com/WordPress/gutenberg/pull/67778)) * Fix reordering fields in list and grid layouts. ([67777](https://github.com/WordPress/gutenberg/pull/67777)) * Fix: Duplicate template part refers to original name instead of duplicated name.( [67329](https://github.com/WordPress/gutenberg/pull/67329)) * Preserve filters when switching layouts in templates dataviews. ([67744](https://github.com/WordPress/gutenberg/pull/67744)) * QuickEdit: Prevent site-editor from crashing when slug is not an object. ([67577](https://github.com/WordPress/gutenberg/pull/67577)) * Site Editor: Fix featured image not appearing in pages dataviews. ([67562](https://github.com/WordPress/gutenberg/pull/67562)) #### Components * CustomSelectControl: Update Value from Fresh State. ([67733](https://github.com/WordPress/gutenberg/pull/67733)) * Fix the ‘ClipboardButton’ effect cleanup. ([67399](https://github.com/WordPress/gutenberg/pull/67399)) * Navigation: Fix active item hover color. ([67732](https://github.com/WordPress/gutenberg/pull/67732)) * Scrollable: Fix story by declaring field as readonly. ([67683](https://github.com/WordPress/gutenberg/pull/67683)) * Storybook: Fix control types. ([67646](https://github.com/WordPress/gutenberg/pull/67646)) * Storybook: Fix storybook blocks imports. ([67684](https://github.com/WordPress/gutenberg/pull/67684)) * Storybook: Fix table markup in Design Language – Radius documentation. ([67686](https://github.com/WordPress/gutenberg/pull/67686)) * Theme: Fix contrast in nested story. ([67681](https://github.com/WordPress/gutenberg/pull/67681)) #### Post Editor * Fix 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. boxes saving when they’re not present. ([67254](https://github.com/WordPress/gutenberg/pull/67254)) * Fix hiding and showing of meta boxes. ([67504](https://github.com/WordPress/gutenberg/pull/67504)) * Fix: Header layout spacing in Firefox. ([67074](https://github.com/WordPress/gutenberg/pull/67074)) * Make sure Document Bar doesn’t go missing. ([67322](https://github.com/WordPress/gutenberg/pull/67322)) * Update pre-publish panel wording to accurately describe the review process. ( [67328](https://github.com/WordPress/gutenberg/pull/67328)) #### Zoom Out * Fix for inserter. ([67495](https://github.com/WordPress/gutenberg/pull/67495)) * Fix useZoomOut inserter behavior. ([67591](https://github.com/WordPress/gutenberg/pull/67591)) * Fix zoom animation scrollbar. ([67536](https://github.com/WordPress/gutenberg/pull/67536)) * UseScaleCanvas performance improvements. ([67496](https://github.com/WordPress/gutenberg/pull/67496)) #### Write mode * Fix color of disabled buttons in dark toolbar. ([67348](https://github.com/WordPress/gutenberg/pull/67348)) * Fix synced pattern editing in write mode and refactor block editing mode to reducer.( [67026](https://github.com/WordPress/gutenberg/pull/67026)) * Fix: Remove parent block selector while in Write mode. ([67395](https://github.com/WordPress/gutenberg/pull/67395)) * Fix: Write Mode mode persists as enabled in widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. editor. ([67587](https://github.com/WordPress/gutenberg/pull/67587)) #### Global Styles * Edit site: Remove empty preview border and redirect to editor in global styles navigation. ([67548](https://github.com/WordPress/gutenberg/pull/67548)) * Fix: Styles section does not moves stylebook to typography. ([67423](https://github.com/WordPress/gutenberg/pull/67423)) * Global Styles Preview: Don’t use iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. component. ([67682](https://github.com/WordPress/gutenberg/pull/67682)) #### Style Book * Fix critical error when blocks are not registered. ([67703](https://github.com/WordPress/gutenberg/pull/67703)) #### Design Tools * Global Styles: Fix handling of booleans when stabilizing block supports. ([67552](https://github.com/WordPress/gutenberg/pull/67552)) #### Block bindings * Revert “Extensibility: Make Block Bindings work with `editor.BlockEdit` hook”.( [67516](https://github.com/WordPress/gutenberg/pull/67516)) #### Patterns * Site Editor: Fix the patterns route on mobile. ([67467](https://github.com/WordPress/gutenberg/pull/67467)) #### Focus Mode * Site Editor: Fix focus mode navigation. ([67458](https://github.com/WordPress/gutenberg/pull/67458)) #### List View * Fix List View not updating when switching editor modes. ([67379](https://github.com/WordPress/gutenberg/pull/67379)) #### Extensibility * Make Block Bindings work with `editor.BlockEdit` hook. ([67370](https://github.com/WordPress/gutenberg/pull/67370)) #### Synced Patterns * Remove use of `contentOnly` block editing mode for synced patterns. ([67364](https://github.com/WordPress/gutenberg/pull/67364)) #### Widgets Editor * Block Bindings: Remove client core sources registration in widgets. ([67349](https://github.com/WordPress/gutenberg/pull/67349)) #### REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) 󠀁[https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)󠁿 * Support search_columns argument in the user endpoint. ([67330](https://github.com/WordPress/gutenberg/pull/67330)) ### 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) * [Dataviews] Fix: Space does not triggers the media button on grid view. ([67791](https://github.com/WordPress/gutenberg/pull/67791)) #### Block Editor * BlockSwitcher: Refactor to use Button layout properly. ([67502](https://github.com/WordPress/gutenberg/pull/67502)) * Remove one occurrence of incorrect usage of ItemGroup. ([67427](https://github.com/WordPress/gutenberg/pull/67427)) #### DataViews * [a11y] Fix: Media button on the page view grid does not have an accessible name.( [67690](https://github.com/WordPress/gutenberg/pull/67690)) #### Components * Fix incorrect usage of ItemGroup in the Image block filters panel. ([67513](https://github.com/WordPress/gutenberg/pull/67513)) #### Post Editor * Fix EntitiesSavedStates panel dialog props. ([67351](https://github.com/WordPress/gutenberg/pull/67351)) ### Performance * Fix re-renders caused by `getEntityRecordsPermissions` after [#67667](https://github.com/WordPress/gutenberg/pull/67667).( [67770](https://github.com/WordPress/gutenberg/pull/67770)) * Preload: Fix end-to-end test. ([67497](https://github.com/WordPress/gutenberg/pull/67497)) * Site Editor: Pages: Preload template lookup. ([66654](https://github.com/WordPress/gutenberg/pull/66654)) * [mini] Preload: Add post type. ([67518](https://github.com/WordPress/gutenberg/pull/67518)) ### Experiments * Move `duplicateTemplatePart` action to the `@wordpress/fields` package. ([65390](https://github.com/WordPress/gutenberg/pull/65390)) ### Documentation * Button: Revise documentation. ([66617](https://github.com/WordPress/gutenberg/pull/66617)) * Docs: Fix Playwright Page Object Model link. ([67652](https://github.com/WordPress/gutenberg/pull/67652)) * Docs: Include the strategy for setting `engines` for WordPress packages. ([67727](https://github.com/WordPress/gutenberg/pull/67727)) * Docs: Remove invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also _notabug_) that indicates the ticket is not a bug, is a support request, or is generally invalid. key projects links on the documentation. ([67491](https://github.com/WordPress/gutenberg/pull/67491)) * Improve documentation for fields package. ([67580](https://github.com/WordPress/gutenberg/pull/67580)) * Refine `getServerState()` & `getServerContext()` documentation. ([67499](https://github.com/WordPress/gutenberg/pull/67499)) * Storybook: Add WritingModeControl story. ([67343](https://github.com/WordPress/gutenberg/pull/67343)) * Storybook: Add stories for AlignmentToolbar and AlignmentControl components. ( [67046](https://github.com/WordPress/gutenberg/pull/67046)) * Storybook: Add stories for HeadingLevelDropdown component. ([67294](https://github.com/WordPress/gutenberg/pull/67294)) * Storybook: Revert “Preview: ArgsTable => Controls ([#67582](https://github.com/WordPress/gutenberg/pull/67582))”.( [67656](https://github.com/WordPress/gutenberg/pull/67656)) * Storybook: Support keyword search in Icon Library. ([67442](https://github.com/WordPress/gutenberg/pull/67442)) * Switch Several Links to httpsHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. in Document Files. ([67706](https://github.com/WordPress/gutenberg/pull/67706)) * Update README.md. ([67711](https://github.com/WordPress/gutenberg/pull/67711)) * Update extending-the-query-loop-block.md. ([67529](https://github.com/WordPress/gutenberg/pull/67529)) * Update global stylesheet docblocks with `custom-css` parameter. ([67716](https://github.com/WordPress/gutenberg/pull/67716)) * Updated old URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org in Documentation. ([67446](https://github.com/WordPress/gutenberg/pull/67446)) ### Code Quality * Convert lock unlock to generics. ([66682](https://github.com/WordPress/gutenberg/pull/66682)) * CreateTemplatePartModal: Avoid identity warning in useSelect. ([67786](https://github.com/WordPress/gutenberg/pull/67786)) * CreateTemplatePartModal: Replace `ts-ignore` with `ts-expect-error`. ([67709](https://github.com/WordPress/gutenberg/pull/67709)) * Fix misc type compilation errors in editor and block editor packages. ([67410](https://github.com/WordPress/gutenberg/pull/67410)) * Fix: Invalid JSDoc for optional string parameter and return value. ([67489](https://github.com/WordPress/gutenberg/pull/67489)) * Fix: Remove unused test code on tools panel. ([67589](https://github.com/WordPress/gutenberg/pull/67589)) * Removed trailing space in “Color randomizer “. ([67457](https://github.com/WordPress/gutenberg/pull/67457)) * Update misc types and revert WPCompleter export from components. ([67599](https://github.com/WordPress/gutenberg/pull/67599)) #### Components * BoxControl: Deprecate 36px default size. ([66704](https://github.com/WordPress/gutenberg/pull/66704)) * BoxControl: Passive deprecate `onMouseOver`/`onMouseOut`. ([67332](https://github.com/WordPress/gutenberg/pull/67332)) * BoxControl: Refactor and unify the different sides implementation. ([67626](https://github.com/WordPress/gutenberg/pull/67626)) * CustomSelectControl: Deprecate 36px default size. ([67441](https://github.com/WordPress/gutenberg/pull/67441)) * FormFileUpload: Deprecate 36px default size. ([67438](https://github.com/WordPress/gutenberg/pull/67438)) * FormTokenField: Deprecate 36px default size. ([67454](https://github.com/WordPress/gutenberg/pull/67454)) * NumberControl: Deprecate 36px default size. ([66730](https://github.com/WordPress/gutenberg/pull/66730)) * RangeControl: Update the default marks styles to match the padding/margin control.( [67611](https://github.com/WordPress/gutenberg/pull/67611)) * Remove `__unstableMotionContext` from `@wordpress/components`. ([67623](https://github.com/WordPress/gutenberg/pull/67623)) * SlotFill: Remove explicit rerender from portal version. ([67471](https://github.com/WordPress/gutenberg/pull/67471)) * Tabs: Overhaul unit tests. ([66140](https://github.com/WordPress/gutenberg/pull/66140)) * ToolbarButton: Set size to “compact”. ([67440](https://github.com/WordPress/gutenberg/pull/67440)) * UnitControl : Deprecate 36px default size. ([66791](https://github.com/WordPress/gutenberg/pull/66791)) #### Block Editor * Group ‘onRemove’ callback with other public APIs. ([67551](https://github.com/WordPress/gutenberg/pull/67551)) * InspectorControlsSlot: Remove unused framer motion context forwarding. ([67522](https://github.com/WordPress/gutenberg/pull/67522)) * LetteringSpacingControl: Deprecate 36px default size. ([67429](https://github.com/WordPress/gutenberg/pull/67429)) * Reduce the ‘isZoomOut’ selector calls in the block toolbar. ([67594](https://github.com/WordPress/gutenberg/pull/67594)) * Remove ‘React.Children’ legacy 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. in ‘Warning’ component. ([67675](https://github.com/WordPress/gutenberg/pull/67675)) * Replace remaining custom deep cloning with ‘structuredClone’. ([67707](https://github.com/WordPress/gutenberg/pull/67707)) * Stabilize `LinkControl` Component. ([56384](https://github.com/WordPress/gutenberg/pull/56384)) #### Site Editor * Remove .components-item-group selector in edit-site components[2]. ([67575](https://github.com/WordPress/gutenberg/pull/67575)) * Site Editor Sidebar: Remove `hasGlobalStyleVariations` condition for the Styles nav item. ([67545](https://github.com/WordPress/gutenberg/pull/67545)) * Unify layout with posts dataviews. ([67162](https://github.com/WordPress/gutenberg/pull/67162)) * Use path based routing instead of query args and site-editor.php routes. ([67199](https://github.com/WordPress/gutenberg/pull/67199)) #### Post Editor * Editor: Refactor ‘PostPublishPanelPostpublish’ to function component. ([67398](https://github.com/WordPress/gutenberg/pull/67398)) * Editor: Use 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. instead of HOC in ‘PostPublishButtonOrToggle’. ([67413](https://github.com/WordPress/gutenberg/pull/67413)) * Remove PostSlugCheck and PostSlug unused components. ([67414](https://github.com/WordPress/gutenberg/pull/67414)) #### DataViews * Create a single component for rendering the actions list. ([67558](https://github.com/WordPress/gutenberg/pull/67558)) * Fix: Dataviews remove primary field concept from some classes. ([67689](https://github.com/WordPress/gutenberg/pull/67689)) #### Data Layer * TypeScript: Convert factory utils in data package to TS. ([67667](https://github.com/WordPress/gutenberg/pull/67667)) #### Shortcodes * Add types for shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. package. ([67416](https://github.com/WordPress/gutenberg/pull/67416)) #### Block bindings * Remove fallback for `context.postType` in post meta. ([67345](https://github.com/WordPress/gutenberg/pull/67345)) #### Block hooks * Navigation block: Remove more obsolete Block Hooks helpers. ([67193](https://github.com/WordPress/gutenberg/pull/67193)) ### Tools * PR template: Add before/after table. ([62739](https://github.com/WordPress/gutenberg/pull/62739)) #### Build Tooling * Build: Stop generating unused legacy scripts for core blocks. ([65268](https://github.com/WordPress/gutenberg/pull/65268)) * CI: Skip native jobs. ([67799](https://github.com/WordPress/gutenberg/pull/67799)) * DataViews build-wp: Don’t bundle singleton WordPress packages. ([67590](https://github.com/WordPress/gutenberg/pull/67590)) * DataViews build-wp: Don’t bundle the date package. ([67612](https://github.com/WordPress/gutenberg/pull/67612)) * Keycodes: Improve tree shaking by annotating exports as pure. ([67615](https://github.com/WordPress/gutenberg/pull/67615)) * Upgrade TypeScript to 5.7 and fix types. ([67461](https://github.com/WordPress/gutenberg/pull/67461)) * Combine the release steps to ensure that releases are tagged. ([65591](https://github.com/WordPress/gutenberg/pull/65591)) #### Testing * e2e-test-utils-playwright: Increase timeout of site-editor selector. ([66672](https://github.com/WordPress/gutenberg/pull/66672)) ### Security #### npm Packages * Update npm dependencies to fix issues reported by audit. ([67708](https://github.com/WordPress/gutenberg/pull/67708)) ### Various #### Extensibility * Add ability to show drop cap setting in paragraph block by default. ([45994](https://github.com/WordPress/gutenberg/pull/45994)) * DataViews: Move template and pattern title fields. ([67449](https://github.com/WordPress/gutenberg/pull/67449)) * DataViews: Update `usePostFields` to accept postType. ([67380](https://github.com/WordPress/gutenberg/pull/67380)) #### 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. * Only override REST server for older WP versions. ([67779](https://github.com/WordPress/gutenberg/pull/67779)) #### NUX * Welcome guide headline update. ([67654](https://github.com/WordPress/gutenberg/pull/67654)) #### Block Locking * Simplify description and option names in the Lock modal dialog. ([67437](https://github.com/WordPress/gutenberg/pull/67437)) ## First-time contributors A colossal kudos to all the first-time contributors who submitted the following PRs: * [@alexflorisca](https://github.com/alexflorisca): e2e-test-utils-playwright: Increase timeout of site-editor selector. ([66672](https://github.com/WordPress/gutenberg/pull/66672)) * [@benazeer-ben](https://github.com/benazeer-ben): Site editor: Style the selected template pattern. ([65917](https://github.com/WordPress/gutenberg/pull/65917)) * [@creador-dev](https://github.com/creador-dev): Navigation Block: Fix issue with double-clicking “Create a new menu” causing duplicate menus. ([67488](https://github.com/WordPress/gutenberg/pull/67488)) * [@dknauss](https://github.com/dknauss): Update README.md. ([67711](https://github.com/WordPress/gutenberg/pull/67711)) * [@im3dabasia](https://github.com/im3dabasia): Removed trailing space in “Color randomizer “. ([67457](https://github.com/WordPress/gutenberg/pull/67457)) * [@Mayank-Tripathi32](https://github.com/Mayank-Tripathi32): Fix: Header layout spacing in Firefox. ([67074](https://github.com/WordPress/gutenberg/pull/67074)) * [@subodhr258](https://github.com/subodhr258): CustomSelectControl: Update Value from Fresh State. ([67733](https://github.com/WordPress/gutenberg/pull/67733)) * [@wwdes](https://github.com/wwdes): Added enableAlpha prop to CustomGradientPicker and GradientPicker components. ([66974](https://github.com/WordPress/gutenberg/pull/66974)) ## Contributors Finally, thanks to everyone who gave their time, code, reviews and ideas to Gutenberg 19.9: [@aaronrobertshaw](https://github.com/aaronrobertshaw)[](https://profiles.wordpress.org/aaronrobertshaw) [@afercia](https://github.com/afercia)[](https://profiles.wordpress.org/afercia) [@ajlende](https://github.com/ajlende)[](https://profiles.wordpress.org/ajlende) [@akasunil](https://github.com/akasunil)[](https://profiles.wordpress.org/sunil25393) [@AKSHAT2802](https://github.com/AKSHAT2802)[](https://profiles.wordpress.org/akshat2802) [@benazeer-ben](https://github.com/benazeer-ben)[](https://profiles.wordpress.org/benazeer) [@benniledl](https://github.com/benniledl)[](https://profiles.wordpress.org/benniledl) [@carolinan](https://github.com/carolinan)[](https://profiles.wordpress.org/poena) [@cbravobernal](https://github.com/cbravobernal)[](https://profiles.wordpress.org/cbravobernal) [@desrosj](https://github.com/desrosj)[](https://profiles.wordpress.org/desrosj) [@dhruvang21](https://github.com/dhruvang21)[](https://profiles.wordpress.org/dhruvang21) [@dougwollison](https://github.com/dougwollison)[](https://profiles.wordpress.org/dougwollison) [@ellatrix](https://github.com/ellatrix)[](https://profiles.wordpress.org/ellatrix) [@getdave](https://github.com/getdave)[](https://profiles.wordpress.org/get_dave) [@gigitux](https://github.com/gigitux)[](https://profiles.wordpress.org/gigitux) [@gziolo](https://github.com/gziolo)[](https://profiles.wordpress.org/gziolo) [@hbhalodia](https://github.com/hbhalodia) [](https://profiles.wordpress.org/hbhalodia) [@himanshupathak95](https://github.com/himanshupathak95) [](https://profiles.wordpress.org/abcd95) [@Infinite-Null](https://github.com/Infinite-Null) [](https://profiles.wordpress.org/ankitkumarshah) [@jeryj](https://github.com/jeryj) [](https://profiles.wordpress.org/jeryj) [@jsnajdr](https://github.com/jsnajdr)[](https://profiles.wordpress.org/jsnajdr) [@juanfra](https://github.com/juanfra)[](https://profiles.wordpress.org/juanfra) [@louwie17](https://github.com/louwie17)[](https://profiles.wordpress.org/louwie17) [@Mamaduka](https://github.com/Mamaduka)[](https://profiles.wordpress.org/mamaduka) [@manzoorwanijk](https://github.com/manzoorwanijk)[](https://profiles.wordpress.org/manzoorwanijk) [@matiasbenedetto](https://github.com/matiasbenedetto)[](https://profiles.wordpress.org/mmaattiiaass) [@mcsf](https://github.com/mcsf)[](https://profiles.wordpress.org/mcsf) [@michalczaplinski](https://github.com/michalczaplinski) [](https://profiles.wordpress.org/czapla) [@miminari](https://github.com/miminari) [](https://profiles.wordpress.org/mimitips) [@mirka](https://github.com/mirka)[](https://profiles.wordpress.org/0mirka00) [@ndiego](https://github.com/ndiego)[](https://profiles.wordpress.org/ndiego) [@ntsekouras](https://github.com/ntsekouras) [](https://profiles.wordpress.org/ntsekouras) [@oandregal](https://github.com/oandregal) [](https://profiles.wordpress.org/oandregal) [@ockham](https://github.com/ockham) [](https://profiles.wordpress.org/bernhard-reiter) [@PARTHVATALIYA](https://github.com/PARTHVATALIYA) [](https://profiles.wordpress.org/parthvataliya) [@ramonjd](https://github.com/ramonjd) [](https://profiles.wordpress.org/ramonopoly) [@SainathPoojary](https://github.com/SainathPoojary) [](https://profiles.wordpress.org/sainathpoojary) [@SantosGuillamot](https://github.com/SantosGuillamot) [](https://profiles.wordpress.org/santosguillamot) [@sarthaknagoshe2002](https://github.com/sarthaknagoshe2002) [](https://profiles.wordpress.org/sarthaknagoshe2002) [@snehapatil2001](https://github.com/snehapatil2001) [](https://profiles.wordpress.org/snehapatil02) [@Soean](https://github.com/Soean) [](https://profiles.wordpress.org/soean) [@Sukhendu2002](https://github.com/Sukhendu2002) [](https://profiles.wordpress.org/sukhendu2002) [@t-hamano](https://github.com/t-hamano) [](https://profiles.wordpress.org/wildworks) [@talldan](https://github.com/talldan) [](https://profiles.wordpress.org/talldanwp) [@tellthemachines](https://github.com/tellthemachines) [](https://profiles.wordpress.org/isabel_brison) [@TylerB24890](https://github.com/TylerB24890) [](https://profiles.wordpress.org/tyb) [@tyxla](https://github.com/tyxla)[](https://profiles.wordpress.org/tyxla) [@up1512001](https://github.com/up1512001)[](https://profiles.wordpress.org/up1512001) [@vipul0425](https://github.com/vipul0425)[](https://profiles.wordpress.org/vipulgupta003) [@yogeshbhutkar](https://github.com/yogeshbhutkar)[](https://profiles.wordpress.org/yogeshbhutkar) [@youknowriad](https://github.com/youknowriad) See you next year for Gutenberg 20.0! 🎉 Thanks to [@annezazu](https://profiles.wordpress.org/annezazu/), [@bernhard-reiter](https://profiles.wordpress.org/bernhard-reiter/), [@joen](https://profiles.wordpress.org/joen/), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/) and [@ndiego](https://profiles.wordpress.org/ndiego/) who helped with this release. [#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/mikachan/) [Sarah Norris](https://profiles.wordpress.org/mikachan/) 5:27 pm _on_ December 17, 2024 Tags: [6-8 ( 91 )](https://make.wordpress.org/core/tag/6-8/), [agenda ( 1,130 )](https://make.wordpress.org/core/tag/agenda/), [dev chat ( 908 )](https://make.wordpress.org/core/tag/dev-chat/) # 󠀁[Agenda, Dev Chat, Dec 18, 2024](https://make.wordpress.org/core/2024/12/17/agenda-dev-chat-dec-18-2024/)󠁿 The next WordPress Developers Chat will take place on [Wednesday at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20241218T2000) in the [core](https://wordpress.slack.com/messages/core/) channel on [Make WordPress Slack](https://make.wordpress.org/chat/). This will be the last Dev Chat of 2024 and we will resume the meetings again on January 8, 2025. The live meeting will focus on the discussion for upcoming releases, and have an open floor section. Additional items will be referred to in the various curated agenda sections below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda. 1. [Announcements](https://make.wordpress.org/core/2024/12/17/agenda-dev-chat-dec-18-2024/#announcements) 2. [Forthcoming releases](https://make.wordpress.org/core/2024/12/17/agenda-dev-chat-dec-18-2024/#forthcoming-releases) 3. a. [Next major release: 6.8](https://make.wordpress.org/core/2024/12/17/agenda-dev-chat-dec-18-2024/#next-major-release-6-8) b. [Next maintenance release: 6.7.2](https://make.wordpress.org/core/2024/12/17/agenda-dev-chat-dec-18-2024/#next-maintenance-release-6-7-2) c. [Next Gutenberg release: 19.9](https://make.wordpress.org/core/2024/12/17/agenda-dev-chat-dec-18-2024/#next-gutenberg-release-19-9) 4. [Discussions](https://make.wordpress.org/core/2024/12/17/agenda-dev-chat-dec-18-2024/#discussions) 5. [Highlighted Posts](https://make.wordpress.org/core/2024/12/17/agenda-dev-chat-dec-18-2024/#highlighted-posts) 6. [Editor Updates](https://make.wordpress.org/core/2024/12/17/agenda-dev-chat-dec-18-2024/#editor-updates) 7. [Open floor](https://make.wordpress.org/core/2024/12/17/agenda-dev-chat-dec-18-2024/#tickets-for-assistance) ## Announcements The [Nominations for 2025’s Core Team Reps](https://make.wordpress.org/core/2024/12/17/nominations-for-core-team-reps-2025-edition/) are now open! Please nominate people in the comments of that post. Self-nominations are welcome. The deadline is January 31, 2025. ## Forthcoming releases ### Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8 We are currently in the [WordPress 6.8 release cycle](https://make.wordpress.org/core/6-8/). The [call for volunteers for the 6.8 release squad](https://make.wordpress.org/core/2024/11/21/wordpress-6-8-call-for-volunteers/) closed on Dec 6 and the release squad will be put together soon based on these volunteers. ### Next maintenance release: 6.7.2 There is currently no release date planned for WordPress 6.7.2. Review the [next minor release milestone](https://core.trac.wordpress.org/tickets/minor). ### Next 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/)󠁿 release: 19.9 The next Gutenberg release will be 19.9, scheduled for December 18. It will include [the following issues](https://github.com/WordPress/gutenberg/milestone/248?closed=1). ## Discussions The discussion section of the agenda is to provide a place to discuss important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. _If you want to nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion._ ## Highlighted Posts * [Nominations for Core Team Reps: 2025 Edition](https://make.wordpress.org/core/2024/12/17/nominations-for-core-team-reps-2025-edition/) ## Editor Updates Props to [@annezazu](https://profiles.wordpress.org/annezazu/) for putting this list of updates together: * Please share [Feedback on adoption approach for exposing the Style Book for Classic themes](https://github.com/WordPress/gutenberg/issues/68036#top). This needs community feedback early well ahead of WordPress 6.8 so we can find the right approach for opt in/out for the Style book for classic themes. * 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. Bindings: [iteration issue has been opened for WordPress 6.8](https://github.com/WordPress/gutenberg/issues/67520#top). * Block 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.: a PR was merged that [brings block hooks to post content](https://github.com/WordPress/gutenberg/pull/67272), expanding the initial version that applied just to templates. * Components: new issue opened to [unify all the different box control components that we have in the code base.](https://github.com/WordPress/gutenberg/issues/67625) * Responsive controls: Please chime in on [Columns: add min and max width settings for responsive control ](https://github.com/WordPress/gutenberg/issues/40870) to share feedback about what you’d like to see here. In particular, it would be helpful to have some folks explain how you would achieve this with regular CSSCSS Cascading Style Sheets. to get a clearer idea of what settings/block supports need to be implemented. * [Standardize Block Inspector Settings to use ToolsPanel ](https://github.com/WordPress/gutenberg/issues/67813#top) is underway with loads of new issues opened to better unify how we group controls, opting to use `ToolsPanel` over the prior `PanelBody.` * Style book: PR opened to [add button interactive states in the Style book](https://github.com/WordPress/gutenberg/pull/67541#top), progressively expanding how valuable the Style book is! And a new icon is being explored by design in [Revisit the Style Book icon](https://github.com/WordPress/gutenberg/issues/67980#top). * Zoom out: [Replace Starter Content modal with inserter panel PR](https://github.com/WordPress/gutenberg/pull/66836) continues to progress, utilizing zoom out for new page creation. You can keep up to date with the major Editor features that are currently in progress by viewing these [Iteration issues](https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+label%3A%22%5BType%5D+Iteration%22+sort%3Aupdated-desc). ## Open floor Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized. Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting for discussion or if you will be async. _Thank you and props to _[@joemcgill](https://profiles.wordpress.org/joemcgill/) and [@annezazu](https://profiles.wordpress.org/annezazu/)_ for contributing to this agenda_. [#6-8](https://make.wordpress.org/core/tag/6-8/), [#agenda](https://make.wordpress.org/core/tag/agenda/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/mikachan/) [Sarah Norris](https://profiles.wordpress.org/mikachan/) 5:02 pm _on_ December 17, 2024 Tags: [team reps ( 21 )](https://make.wordpress.org/core/tag/team-reps/) # 󠀁[Nominations for Core Team Reps: 2025 Edition](https://make.wordpress.org/core/2024/12/17/nominations-for-core-team-reps-2025-edition/)󠁿 Nominations are now closed. Thank you to everyone who responded. This post kicks off the formal election process with a call for nominations for the 2025 CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps. For 2024, Joe McGill ([@joemcgill](https://profiles.wordpress.org/joemcgill/)) and Sarah Norris ([@mikachan](https://profiles.wordpress.org/mikachan/)) have served as the elected Core Team Reps. ## The Roles In the WordPress open-source project, each team has on average one or two representatives, abbreviated as reps. For the historians out there, the roles go [way back to 2012](https://make.wordpress.org/updates/team-reps/). Historically with the Core team, the team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. duration was around a year, though some reps stuck around longer if there was a particularly good fit. Anyone who serves as a “team rep” is responsible for communicating on behalf of the Core team to the other contributor groups via [weekly updates](https://make.wordpress.org/updates/), as well as occasional cross-team chats. Reps are also consulted on Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of [https://make.wordpress.org/](https://make.wordpress.org/) There are many teams that people can participate in, each with a different focus. [https://2017.us.wordcamp.org/contributor-day/](https://2017.us.wordcamp.org/contributor-day/) [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/), where they help to find someone within the Core team who will be at an event who can lead a Core table. [Full details on the Team Rep role can be found on the Team Update site.](https://make.wordpress.org/updates/team-reps/) **It is not called “team lead” for a reason.**  It’s an administrative role. While people elected as team reps will generally come from the pool of folks that people think of as experienced leaders, the team rep role is designed to change hands regularly. This role has a time commitment of at least one or two hours a week. The main tasks include: * Posting the weekly Dev Chat agenda, hosting the chats, and summarizing them ( which can include writing and encouraging others to contribute to the summaries). [More details on coordinating devchat are available in the Core handbook](https://make.wordpress.org/core/handbook/tutorials/coordinating-devchat/). * Keeping up with the current releases (mainly WordPress major and minors and 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/) bi-weekly releases) and communicating updates. * Keeping a watch on the moving parts of the team to report for quarterly updates( [example](https://make.wordpress.org/updates/2018/04/24/quarterly-updates-q1-2018/)). ## How the election works Please **nominate** people in the comments of this post. Self-nominations are welcome. The deadline is [January 31, 2025 at 23:59 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250131T2359). If there are fewer than 2 nominees who have accepted their nominations, the deadline will be extended. Once the nomination period expires, a poll will be opened for **voting**. It will stay open for two weeks. The new reps will start their role in February 2025. **_Disclaimer:_ if you are nominated, please don’t feel like you have to agree to say yes. The election poll will only include the names of the people who have agreed to be nominated. So feel free to reply with a “Thank you, but no thank you”.** If you have any questions, please feel free to ask in the comments or speak to the current team reps. Finally, for reference, these are the [2020](https://make.wordpress.org/core/2020/04/29/nominations-for-core-team-reps/), [2021](https://make.wordpress.org/core/2021/10/26/nominations-for-core-team-reps-2022/), [2022](https://make.wordpress.org/core/2021/10/26/nominations-for-core-team-reps-2022/), [2023](https://make.wordpress.org/core/2022/11/14/nominations-for-core-team-reps-2023-edition/), and [2024](https://make.wordpress.org/core/2023/12/04/nominations-for-core-team-reps-2024-edition/) nomination posts. _Thanks to _[@joemcgill](https://profiles.wordpress.org/joemcgill/)_ for reviewing this post. [#team-reps](https://make.wordpress.org/core/tag/team-reps/) [ ](https://profiles.wordpress.org/joemcgill/) [Joe McGill](https://profiles.wordpress.org/joemcgill/) 9:57 am _on_ December 12, 2024 Tags: [6-8 ( 91 )](https://make.wordpress.org/core/tag/6-8/), [core ( 730 )](https://make.wordpress.org/core/tag/core/), [dev chat ( 908 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 970 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Summary, Dev Chat, December 11, 2024](https://make.wordpress.org/core/2024/12/12/summary-dev-chat-december-11-2024/)󠁿 [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1733947226861869) of the meeting in 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/), facilitated by [@mikachan](https://profiles.wordpress.org/mikachan/). 🔗 [Agenda post](https://make.wordpress.org/core/2024/12/10/agenda-dev-chat-dec-11-2024/). ## Announcements There were no announcements today, but [@mikachan](https://profiles.wordpress.org/mikachan/) posted a reminder that [WordCamp Asia 2025](https://asia.wordcamp.org/2025) is looking for volunteers for Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of [https://make.wordpress.org/](https://make.wordpress.org/) There are many teams that people can participate in, each with a different focus. [https://2017.us.wordcamp.org/contributor-day/](https://2017.us.wordcamp.org/contributor-day/) [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/), especially to lead CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./Core Editor/Core Performance tables. Please reach out to [@Jhimross](https://wordpress.slack.com/team/UAR5P5GVA) if you’d like to volunteer. ## Forthcoming releases ### Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8 We are currently in the [WordPress 6.8 release cycle](https://make.wordpress.org/core/6-8/). The [call for volunteers for the 6.8 release squad](https://make.wordpress.org/core/2024/11/21/wordpress-6-8-call-for-volunteers/) closed on Dec 6 and the release squad will be put together soon based on these volunteers. ### Next maintenance release: 6.7.2 There is currently no release date planned for WordPress 6.7.2. Review the [next minor release milestone](https://core.trac.wordpress.org/tickets/minor). [@joemcgill](https://profiles.wordpress.org/joemcgill/) agreed to follow up about another 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. scrub before the end of the year. ### Next 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/)󠁿 release: 19.9 The next Gutenberg release will be 19.9, scheduled for December 18. It will include [the following issues](https://github.com/WordPress/gutenberg/milestone/248?closed=1). ## Discussion There were two topics for discussion today * Any feedback or questions on the [Consent API proposal](https://make.wordpress.org/core/2024/12/04/lets-reconsider-adopting-the-wp-consent-api/) * An open discussion about [WordPress and TypeScript](https://github.com/WordPress/gutenberg/discussions/67781) ### Consent 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. Proposal [@joemcgill](https://profiles.wordpress.org/joemcgill/) noted that we’ve already gotten a lot of good feedback and asked [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) how long we should leave the proposal open for comment. [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/): > “Given the coming holiday season, would it make sense to leave it open through > the end of the year? The feedback has been really positive, but additional feedback > from orgs/plugins working with consent would be valuable.” [@joemcgill](https://profiles.wordpress.org/joemcgill/): > If the consensus is that this should be a core feature, then ensuring the team > who is going to shepherd this into a future release is properly supported would > be key. Either way, I think there is value in considering the other question in > the proposal—which is whether this should become a canonical 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. that is officially supported by the community. > I think we can follow up with @4thhubbard about how we want to handle these kinds > of requests as there really hasn’t been an established policy that I’m aware of. [@mikachan](https://profiles.wordpress.org/mikachan/): > Through the end of the year sounds fine to me. We can make sure we follow-up ( > including in dev chats) towards the start of next year ### WordPress and Typescript [@mikachan](https://profiles.wordpress.org/mikachan/): > We adopted TypeScript in WordPress more than 3 years ago and our usage has evolved > over time. It’s time to update our approach/guidelines. @youknowriad has [opened a discussion](https://github.com/WordPress/gutenberg/discussions/67781) > to gather thoughts before publishing a P2P2 A [free theme for WordPress](http://p2theme.com/), > known for front-end posting, used by WordPress for development updates and project > management. See our [main development blog](https://make.wordpress.org/core/) > and [other workgroup blogs](https://make.wordpress.org/).. Next steps are to continue collecting feedback and revisiting in a future Dev Chat, if needed. ## Open Floor * [@mamaduka](https://profiles.wordpress.org/mamaduka/) asked for more eyes on [#59425](https://core.trac.wordpress.org/ticket/59425), which was recently reported in Gutenberg as well. - [@joemcgill](https://profiles.wordpress.org/joemcgill/) shared this in the [#core-restapi channel](https://wordpress.slack.com/archives/C02RQC26G/p1733950063382799). * [@jonsurrell](https://profiles.wordpress.org/jonsurrell/) shared [this call for feedback](https://wordpress.slack.com/archives/C05NFB818PQ/p1733943536862819) on [this PR](https://github.com/WordPress/wordpress-develop/pull/7857) for adding CSSCSS Cascading Style Sheets. selector-based tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) navigation to HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. and Tag Processors ([#62653](https://core.trac.wordpress.org/ticket/62653)) - All feedback is welcome, but specifically, he’s looking for high-level feedback, especially from WordPress veterans. Does the implementation feel appropriate for WordPress? Are there things that are discouraged in Core? * [@joemcgill](https://profiles.wordpress.org/joemcgill/) raised the need to prepare for nominations for Core Team Reps for 2025 and suggested publishing a call for nominations in the next week with the hopes of collecting responses in Jan and being able to do a transition by Feb. [@mikachan](https://profiles.wordpress.org/mikachan/) and [@joemcgill](https://profiles.wordpress.org/joemcgill/) will take responsibility for following up on this. _Props to [@mikachan](https://profiles.wordpress.org/mikachan/) for reviewing._ [#6-8](https://make.wordpress.org/core/tag/6-8/), [#core](https://make.wordpress.org/core/tag/core/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/clarkeemily/) [Emily Clarke](https://profiles.wordpress.org/clarkeemily/) 5:36 pm _on_ December 10, 2024 Tags: [core-performance ( 143 )](https://make.wordpress.org/core/tag/core-performance/), [hosting ( 48 )](https://make.wordpress.org/core/tag/hosting/), [performance ( 409 )](https://make.wordpress.org/core/tag/performance/), [performance-chat ( 336 )](https://make.wordpress.org/core/tag/performance-chat/), [summary ( 970 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Performance Chat Summary: 10 December 2024](https://make.wordpress.org/core/2024/12/10/performance-chat-summary-10-december-2024/)󠁿 [Meeting agenda here](https://make.wordpress.org/core/2024/12/10/performance-chat-agenda-10-december-2024/) and the full chat log is available [beginning here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1733846407801789). # Announcements * Welcome to our new members of [#core-performance](http://wordpress.slack.com/messages/core-performance/) * The Performance team have posted the [WordPress 6.7 Performance Improvements](https://make.wordpress.org/core/2024/12/10/wordpress-6-7-performance-improvements/) results * The next Performance Lab release will be on **December 16** * Our performance chat time slot next week will be for our [Hallway Hangout: Performance End of Year Review 2024](https://make.wordpress.org/core/2024/12/06/hallway-hangout-performance-end-of-year-review-2024/) taking place **December 17**, 2024 at 16:00 UTC we welcome as many people there as possible! * The performance 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. scrub on **December 18**, 2024 at 16:00 UTC will also be an end of year wrap up session * Upcoming Performance Weekly Chats in December - No meeting on Tuesday December 24 - No meeting on Tuesday December 31 - Meetings will **resume** again on Tuesday January 7, 2025 # Priority Items * WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets - Current release (6.8) [15 Trac tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&status=reviewing&focuses=~performance&milestone=6.8&groupdesc=1&group=resolution&col=id&col=summary&col=status&col=milestone&col=owner&col=type&col=priority&col=keywords&order=priority) - Future releases * Performance Lab 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. (and other performance plugins) - [Next milestone](https://github.com/WordPress/performance/milestones) * Active priority projects - [Project board](https://github.com/orgs/WordPress/projects/199/views/4) ## WordPress Performance Trac Tickets * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) ticketticket Created for both bug reports and feature development on the bug tracker. [#62658](https://core.trac.wordpress.org/ticket/62658) is nearly ready to commit * [@joemcgill](https://profiles.wordpress.org/joemcgill/) we’ve got [5 marked for `early`](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&status=reviewing&keywords=~early&focuses=~performance&milestone=6.8&groupdesc=1&group=resolution&col=id&col=summary&col=status&col=milestone&col=owner&col=type&col=priority&col=keywords&order=priority) that would be good to scrub later today if there’s time, since we skipped last week * [@pbearne](https://profiles.wordpress.org/pbearne/) does not yet have a fix for [#42743](https://core.trac.wordpress.org/ticket/42743). The issue is that I can’t separate 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. widgets from the others the way it hackedhacked in is the problem - [@joemcgill](https://profiles.wordpress.org/joemcgill/) Has that challenge been documented anywhere? Happy to read up on it and try to give feedback, or perhaps there is someone else that is familiar with the issue that could help? - [@pbearne](https://profiles.wordpress.org/pbearne/) The block widgets are load a single widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget- ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. as part of the option. Happy to have others look at this * [@mukesh27](https://profiles.wordpress.org/mukesh27/) for [#58001](https://core.trac.wordpress.org/ticket/58001) suggested we can review the PR and iterate early in the 6.8 cycle - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) Not had time to look into this one again. I would love if someone else could pick this one up, as it most just needs unit tests now. IMO ## Performance Lab Plugin (and other Performance Plugins) * [Performance Lab plugin](https://wordpress.org/plugins/performance-lab/) and the following performance plugins: - [Enhanced Responsive Images](https://wordpress.org/plugins/auto-sizes/) - [Embed Optimizer](https://wordpress.org/plugins/embed-optimizer/) - [Image Prioritizer](https://wordpress.org/plugins/image-prioritizer/) - [Image Placeholders](https://wordpress.org/plugins/dominant-color-images/) - [Modern Image Formats](https://wordpress.org/plugins/webp-uploads/) - [Optimization Detective (Developer Preview)](https://wordpress.org/plugins/optimization-detective/) - [Performant Translations](https://wordpress.org/plugins/performant-translations/) - [Speculative Loading](https://wordpress.org/plugins/speculation-rules/) - [Web Worker Offloading](https://wordpress.org/plugins/web-worker-offloading/) * [@westonruter](https://profiles.wordpress.org/westonruter/) waiting on some code review support for **Optimization Detective** PRs: [https://github.com/WordPress/performance/milestone/88](https://github.com/WordPress/performance/milestone/88) * [@joemcgill](https://profiles.wordpress.org/joemcgill/) these and the related** [Image Prioritizer](https://github.com/WordPress/performance/milestone/85)**  milestone issues are being handled by [@westonruter](https://profiles.wordpress.org/westonruter/) [@flixos90](https://profiles.wordpress.org/flixos90/) and [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) but please shout if you you all need any support this week * [@mukesh27](https://profiles.wordpress.org/mukesh27/) the **Modern Image Formats** plugin PR [Convert WebP to AVIF on upload](https://github.com/WordPress/performance/pull/1724) is ready for review * [@joemcgill](https://profiles.wordpress.org/joemcgill/) looks like this PR from [@pbearne](https://profiles.wordpress.org/pbearne/) on an update on** Image Placeholders** is getting close: [https://github.com/WordPress/performance/pull/1719](https://github.com/WordPress/performance/pull/1719). Would be great to get this into the final release of the year * [@joemcgill](https://profiles.wordpress.org/joemcgill/) has a few tweaks to make to [https://github.com/WordPress/performance/pull/1701](https://github.com/WordPress/performance/pull/1701) for **Enhanced Responsive Images** that I hope to wrap up today and then hopefully we can include another round of updates in this release as well ## Active Priority Projects * [Improving the calculation of image sizes attributes](https://github.com/WordPress/performance/issues/760)( Joe/Mukesh) * [Enable client side modern image generation](https://github.com/WordPress/performance/issues/17)( Pascal) ### Improving the calculation of image size attributes * [@mukesh27](https://profiles.wordpress.org/mukesh27/) has outlined various use cases for the column block width option in [https://github.com/WordPress/performance/issues/1511#issuecomment-2531279775](https://github.com/WordPress/performance/issues/1511#issuecomment-2531279775) ### Enable Client Side Modern Image Generation * No updates this week # Open Floor * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) to discuss [#57496](https://core.trac.wordpress.org/ticket/57496) - Has added tests to the above. I need code review. Can this be added to WP 6.8? - [@joemcgill](https://profiles.wordpress.org/joemcgill/) I don’t see any reason why it can’t be milestoned if it’s close. [@pbearne](https://profiles.wordpress.org/pbearne/) you had self assigned ownership, but am wondering who needs to shepherd this into the release? - [@pbearne](https://profiles.wordpress.org/pbearne/) the code is ready it just need a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. to help - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) I am happy to commit this and action feedback. It doesn’t really need much more, I think it is basically done. **Our next chat will be held on [Tuesday, December 10, 2024 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20241210T1600) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/)** in the form of our [Hallway Hangout: Performance End of Year Review 2024](https://make.wordpress.org/core/2024/12/06/hallway-hangout-performance-end-of-year-review-2024/) [#core-performance](https://make.wordpress.org/core/tag/core-performance/), [#hosting](https://make.wordpress.org/core/tag/hosting/), [#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/mikachan/) [Sarah Norris](https://profiles.wordpress.org/mikachan/) 5:02 pm _on_ December 10, 2024 Tags: [6-8 ( 91 )](https://make.wordpress.org/core/tag/6-8/), [agenda ( 1,130 )](https://make.wordpress.org/core/tag/agenda/), [dev chat ( 908 )](https://make.wordpress.org/core/tag/dev-chat/) # 󠀁[Agenda, Dev Chat, Dec 11, 2024](https://make.wordpress.org/core/2024/12/10/agenda-dev-chat-dec-11-2024/)󠁿 The next WordPress Developers Chat will take place on [Wednesday at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20241211T2000) in the [core](https://wordpress.slack.com/messages/core/) channel on [Make WordPress Slack](https://make.wordpress.org/chat/). The live meeting will focus on the discussion for upcoming releases, and have an open floor section. Additional items will be referred to in the various curated agenda sections below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda. 1. [Announcements](https://make.wordpress.org/core/2024/12/10/agenda-dev-chat-dec-11-2024/#announcements) 2. [Forthcoming releases](https://make.wordpress.org/core/2024/12/10/agenda-dev-chat-dec-11-2024/#forthcoming-releases) 3. a. [Next major release: 6.8](https://make.wordpress.org/core/2024/12/10/agenda-dev-chat-dec-11-2024/#next-major-release-6-8) b. [Next maintenance release: 6.7.2](https://make.wordpress.org/core/2024/12/10/agenda-dev-chat-dec-11-2024/#next-maintenance-release-6-7-2) c. [Next Gutenberg release: 19.9](https://make.wordpress.org/core/2024/12/10/agenda-dev-chat-dec-11-2024/#next-gutenberg-release-19-9) 4. [Discussions](https://make.wordpress.org/core/2024/12/10/agenda-dev-chat-dec-11-2024/#discussions) 5. [Highlighted Posts](https://make.wordpress.org/core/2024/12/10/agenda-dev-chat-dec-11-2024/#highlighted-posts) 6. [Editor Updates](https://make.wordpress.org/core/2024/12/10/agenda-dev-chat-dec-11-2024/#editor-updates) 7. [Open floor](https://make.wordpress.org/core/2024/12/10/agenda-dev-chat-dec-11-2024/#tickets-for-assistance) ## Announcements There are no major announcements from the past week. ## Forthcoming releases ### Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8 We are currently in the [WordPress 6.8 release cycle](https://make.wordpress.org/core/6-8/). The [call for volunteers for the 6.8 release squad](https://make.wordpress.org/core/2024/11/21/wordpress-6-8-call-for-volunteers/) closed on Dec 6 and the release squad will be put together soon based on these volunteers. ### Next maintenance release: 6.7.2 There is currently no release date planned for WordPress 6.7.2. Review the [next minor release milestone](https://core.trac.wordpress.org/tickets/minor). ### Next 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/)󠁿 release: 19.9 The next Gutenberg release will be 19.9, scheduled for December 18. It will include [the following issues](https://github.com/WordPress/gutenberg/milestone/248?closed=1). ## Discussions The discussion section of the agenda is to provide a place to discuss important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. * Any feedback or questions on the [Consent API proposal](https://make.wordpress.org/core/2024/12/04/lets-reconsider-adopting-the-wp-consent-api/) * [@jhimross](https://profiles.wordpress.org/jhimross/) has reminded us that [WordCamp Asia 2025](https://asia.wordcamp.org/2025) is looking for volunteers for Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of [https://make.wordpress.org/](https://make.wordpress.org/) There are many teams that people can participate in, each with a different focus. [https://2017.us.wordcamp.org/contributor-day/](https://2017.us.wordcamp.org/contributor-day/) [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/), especially to lead Core/Core Editor/Core Performance tables. Please reach out 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/) if you’d like to volunteer. _If you want to nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion._ ## Highlighted Posts * [WordPress 6.7 Release Retrospective](https://make.wordpress.org/core/2024/12/06/wordpress-6-7-release-retrospective/) * [Hallway Hangout: Performance End of Year Review 2024](https://make.wordpress.org/core/2024/12/06/hallway-hangout-performance-end-of-year-review-2024/) * [Let’s reconsider adopting the WP Consent API](https://make.wordpress.org/core/2024/12/04/lets-reconsider-adopting-the-wp-consent-api/) ## Editor Updates * We adopted TypeScript in WordPress more than 3 years ago and our usage has evolved over time. It’s time to update our approach/guidelines there. [@youknowriad](https://profiles.wordpress.org/youknowriad/) has [opened a discussion](https://github.com/WordPress/gutenberg/discussions/67781) to gather thoughts before publishing a P2P2 A [free theme for WordPress](http://p2theme.com/), known for front-end posting, used by WordPress for development updates and project management. See our [main development blog](https://make.wordpress.org/core/) and [other workgroup blogs](https://make.wordpress.org/).. You can keep up to date with the major Editor features that are currently in progress by viewing these [Iteration issues](https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+label%3A%22%5BType%5D+Iteration%22+sort%3Aupdated-desc). ## Open floor Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized. Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting for discussion or if you will be async. _Props to _[@joemcgill](https://profiles.wordpress.org/joemcgill/)_ for contributing to this agenda_. [#6-8](https://make.wordpress.org/core/tag/6-8/), [#agenda](https://make.wordpress.org/core/tag/agenda/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/clarkeemily/) [Emily Clarke](https://profiles.wordpress.org/clarkeemily/) 9:51 am _on_ December 10, 2024 Tags: [agenda ( 1,130 )](https://make.wordpress.org/core/tag/agenda/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [performance ( 409 )](https://make.wordpress.org/core/tag/performance/), [performance-chat ( 336 )](https://make.wordpress.org/core/tag/performance-chat/) # 󠀁[Performance Chat Agenda: 10 December 2024](https://make.wordpress.org/core/2024/12/10/performance-chat-agenda-10-december-2024/)󠁿 Here is the agenda for this week’s performance team meeting scheduled for [December 10, 2024 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20241210T1600). * **Announcements** - Welcome to our new members of [#core-performance](http://wordpress.slack.com/messages/core-performance/) - The Performance team have posted the [WordPress 6.7 Performance Improvements](https://make.wordpress.org/core/2024/12/10/wordpress-6-7-performance-improvements/) results - The next Performance Lab release will be on **December 16** - Our performance chat time slot next week will be for our [Hallway Hangout: Performance End of Year Review 2024](https://make.wordpress.org/core/2024/12/06/hallway-hangout-performance-end-of-year-review-2024/) taking place **December 17**, 2024 at 16:00 UTC we welcome as many people there as possible! - The performance 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. scrub on ** December 18**, 2024 at 16:00 UTC will also be an end of year wrap up session - Upcoming Performance Weekly Chats in December: * No meeting on Tuesday December 24 * No meeting on Tuesday December 31 * Meetings will **resume** again on Tuesday January 7, 2025 * **Priority items** - WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets * Current release (6.8) [Trac tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&status=reviewing&focuses=~performance&milestone=6.8&groupdesc=1&group=resolution&col=id&col=summary&col=status&col=milestone&col=owner&col=type&col=priority&col=keywords&order=priority) * Future release - Performance Lab 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. (and other performance plugins) including: * Enhanced Responsive Images * Embed Optimizer * Image Prioritizer * Image Placeholders * Modern Image Formats * Optimization Detective * Performant Translations * Speculative Loading * Web Worker Offloading - Active priority projects * [Improving the calculation of image sizes attributes](https://github.com/WordPress/performance/issues/760)( Joe) * [Enable client side modern image generation](https://github.com/WordPress/performance/issues/17)( Pascal) * **Open floor** If you have any topics you’d like to add to this agenda, please add them in the comments below. --- _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/mukesh27/) [Mukesh Panchal](https://profiles.wordpress.org/mukesh27/) 5:30 am _on_ December 10, 2024 Tags: [6-7 ( 75 )](https://make.wordpress.org/core/tag/6-7/), [core ( 730 )](https://make.wordpress.org/core/tag/core/), [core-performance ( 143 )](https://make.wordpress.org/core/tag/core-performance/), [performance ( 409 )](https://make.wordpress.org/core/tag/performance/)    # 󠀁[WordPress 6.7 Performance Improvements](https://make.wordpress.org/core/2024/12/10/wordpress-6-7-performance-improvements/)󠁿 _This post is the latest in a series of updates focused on the performance improvements of major releases (see _[_6.6_](https://make.wordpress.org/core/2024/07/29/wordpress-6-6-performance-improvements/)_,_ [_6.5_](https://make.wordpress.org/core/2024/04/23/wordpress-6-5-performance-improvements/)_,_ [_6.4_](https://make.wordpress.org/core/2023/11/13/wordpress-6-4-performance-improvements/)_,_ [_6.3_](https://make.wordpress.org/core/2023/08/07/wordpress-6-3-performance-improvements/)_, and _[_6.2_](https://make.wordpress.org/core/2023/04/05/wordpress-6-2-performance-improvements-for-all-themes/)_)._ [WordPress 6.7, “Rollins”](https://wordpress.org/news/2024/11/rollins/) is the last major version of WordPress released in 2024. This release delivers important performance updates, including faster pattern loading, optimized previews in the data views component, improved PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8+ support and removal of deprecated code, auto sizes for lazy-loaded images, and more efficient tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) processing in the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. 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.. Explore the [WordPress 6.7 Field Guide](https://make.wordpress.org/core/2024/10/23/wordpress-6-7-field-guide/). Learn about the changes in this release with detailed developer notes. Further details on the methodology behind these measurements are provided later in this article, along with an explanation of possible regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/2024/?output_format=md#blocker). Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. sources. ## Key improvements ### Media: Auto sizes for lazy loaded images In [#61847](https://core.trac.wordpress.org/ticket/61847),  support was added for` sizes=”auto”` for lazy-loaded images. This feature, which was [recently added to the HTML specification](https://github.com/whatwg/html/pull/8008), allows the  browser to use the rendered layout width of the image when selecting a source from the `srcset` list, since lazy loaded images don’t load until after the layout is known. It maintains backward compatibility while boosting performance, particularly for responsive and dynamic layouts. [Explore the details in the official dev note.](https://make.wordpress.org/core/2024/10/18/auto-sizes-for-lazy-loaded-images-in-wordpress-6-7/) ### Media: Caching `_wp_image_editor_choose` results for improved performance In [#61532](https://core.trac.wordpress.org/ticket/61532), WordPress now caches the results of `_wp_image_editor_choose`, storing the `WP_Image_Editor` implementation that supports queried options. This avoids redundant and costly compatibility checks, such as multiple calls to `WP_Image_Editor_Imagick::supports_mime_type()`, often triggered during tasks like setting up `wp_plupload_default_settings()`. The cache, stored for one day, speeds up editor loading times and introduces a new global caching group, `image_editor`, to manage future optimizations for image editor performance. ### Media: Improve speed of AVIF image generation In [#61758](https://core.trac.wordpress.org/ticket/61758), the change results in the AVIF encoder working faster by raising `heic:speed` to 7 from the default of 5. AVIF generation time is reduced by up to 20% with minimal impact on image size. ### Editor: New 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. type registration APIs to improve performance In [#62002](https://core.trac.wordpress.org/ticket/62002), new block type registration APIs were introduced, offering a more efficient way to manage block metadata and improve performance across the board. These APIs allow developers to register blocks more flexibly, reducing server-side processing and enhancing editor load times. With these changes, WordPress lays the groundwork for faster, more scalable block- based experiences while maintaining backward compatibility. [Explore the details in the official dev note](https://make.wordpress.org/core/2024/10/17/new-block-type-registration-apis-to-improve-performance-in-wordpress-6-7/). ### Editor: Caching Global Styles for Blocks In [#59595](https://core.trac.wordpress.org/ticket/59595), profiling WordPress 6.4 revealed that the `WP_Theme_JSON::compute_style_properties` method could account for 6-11% of server time during page generation. To address this, the editor now caches the generated CSSCSS Cascading Style Sheets. for block nodes derived from merged Theme JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. data. By saving the computed styles in a transient, WordPress avoids repeated and resource-intensive operations, significantly improving performance and reducing server load. This change is a key optimization for sites leveraging block themes and `theme.json`. ### Themes: Improve performance of applying background image styles in theme.json. In [#61858](https://core.trac.wordpress.org/ticket/61858), the cost of using `WP_Theme_JSON:: get_block_nodes()` for this in its original shape was high enough to lead to a performance regression. Therefore this changeset introduces a new option on the method that allows to bypass all logic except for retrieving the node paths, which is much faster and everything that this functionality needs. ### Miscellaneous Editor improvements: In addition to the previously listed editor improvements, this release includes the following list of changes that improves the editor experience itself: * [Reusable blocks: fix performance of __experimentalGetAllowedPatterns](https://github.com/WordPress/gutenberg/pull/64871#top)( helps when there are thousands of patterns). * [Performance: Fetch permissions for visible patterns only](https://github.com/WordPress/gutenberg/pull/64606#top) * [DataViews: Optimize the templates dataviews by extracting the fields definition](https://github.com/WordPress/gutenberg/pull/63929#top)& [DataViews: Optimize the patterns dataviews by extracting the fields definition](https://github.com/WordPress/gutenberg/pull/63927#top)( not sold on these based on the PR descriptions). * [Section Styles: improve performance and conceptual consistency](https://github.com/WordPress/gutenberg/pull/62712#top) ### Additional performance focused changes In total, there were [23 performance related improvements](https://core.trac.wordpress.org/query?status=closed&focuses=~performance&milestone=6.7&group=milestone&col=id&col=summary&col=status&col=focuses&col=owner&col=type&col=priority&order=priority) included in this release, split evenly between new enhancements (12) and 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 (11). ## Performance metrics In our analysis, block themes (Twenty Twenty-Four was tested) experienced a modest regression in performance. The median Largest Contentful Pain (LCP) time increased by ~6ms or ~3.5% in tests, and the median Time To First Byte (TTFB) shows a 2ms ( 2%) regression. Classic themes show a slight improvement (Twenty Twenty-One was tested). The median Largest Contentful Pain (LCP) and Time To First Byte (TTFB) time shows a slight 0.2ms or 0.2% improvement in tests. ## **How release performance is measured** The performance measurements used for the overview are based on benchmarks conducted using an [automated workflow](https://github.com/mukeshpanchal27/compare-wp-performance) 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/) action runners. Benchmarks were taken from the homepage of the Twenty Twenty-one, Twenty Twenty-three, and Twenty Twenty-four themes, comparing WordPress 6.7 with WordPress 6.6.2 (the latest version of WP 6.6 available when 6.7 was released). Performance metrics were collected from 100 runs for both CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Web Vitals (CWV) and [Server-Timing headers](https://make.wordpress.org/performance/handbook/measuring-performance/benchmarking-php-performance-with-server-timing/) provided by the Performance Lab 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. using [CLI scripts from the WPP Research repo](https://github.com/GoogleChromeLabs/wpp-research/tree/main/cli). ### Benchmark Data * Twenty Twenty-one - [Web Vitals](https://docs.google.com/spreadsheets/d/1gQ_-P_fwj4dHpXrhv6eyjsizPYX85SL7JJOrzEDp9eA/edit?usp=sharing) - [Server-Timing](https://docs.google.com/spreadsheets/d/1gQ_-P_fwj4dHpXrhv6eyjsizPYX85SL7JJOrzEDp9eA/edit?gid=596732474#gid=596732474) * Twenty Twenty-three - [Web Vitals](https://docs.google.com/spreadsheets/d/1gQ_-P_fwj4dHpXrhv6eyjsizPYX85SL7JJOrzEDp9eA/edit?gid=473703093#gid=473703093) - [Server-Timing](https://docs.google.com/spreadsheets/d/1gQ_-P_fwj4dHpXrhv6eyjsizPYX85SL7JJOrzEDp9eA/edit?gid=1867254656#gid=1867254656) * Twenty Twenty-four - [Web Vitals](https://docs.google.com/spreadsheets/d/1gQ_-P_fwj4dHpXrhv6eyjsizPYX85SL7JJOrzEDp9eA/edit?gid=706621267#gid=706621267) - [Server-Timing](https://docs.google.com/spreadsheets/d/1gQ_-P_fwj4dHpXrhv6eyjsizPYX85SL7JJOrzEDp9eA/edit?gid=1553386068#gid=1553386068) ## Follow up from this release WordPress 6.7 shows a regression in performance. While some overhead typically accompanies new features, these declines point to areas where the performance team continues to investigate where these regressions came from and how they can be addressed in the upcoming releases. Each release, the Performance Team looks for opportunities to improve the performance of WordPress for the following releases, which includes identifying ways we can improve the tooling and processes we use to support the performance practice. For example, we’re collecting opportunities to improve our performance testing in [this GitHub issue](https://github.com/WordPress/performance/issues/1093). [Performance Lab](https://wordpress.org/plugins/performance-lab/) – the plugin(s) we use to test out new performance features for core – continues to add new features such as [Image Prioritizer](https://wordpress.org/plugins/image-prioritizer/) , [Embed Optimizer](https://wordpress.org/plugins/embed-optimizer/), [Speculative Loading](https://wordpress.org/plugins/speculation-rules/), [Performant Translations](https://wordpress.org/plugins/performant-translations/), [Modern Image Formats](https://wordpress.org/plugins/webp-uploads/), [Enhanced Responsive Images](https://wordpress.org/plugins/auto-sizes/), and [Web Worker Offloading](https://wordpress.org/plugins/web-worker-offloading/). You can also follow progress on other performance-related work being planned for the WordPress 6.8 release [in Trac](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&status=reviewing&focuses=~performance&milestone=6.8&groupdesc=1&group=resolution&col=id&col=summary&col=status&col=milestone&col=owner&col=type&col=priority&col=keywords&order=priority). A full list of the Performance Team’s priorities for the year is available on the [2024 Roadmap page](https://make.wordpress.org/performance/roadmap-2024/). Additionally, the 2025 Roadmap will be published early in Q1 2025 in the team’s handbook. Come join us in making WordPress as performant as possible. Props to [@joemcgill](https://profiles.wordpress.org/joemcgill/), [@flixos90](https://profiles.wordpress.org/flixos90/), [@westonruter](https://profiles.wordpress.org/westonruter/), and [@fabiankaegy](https://profiles.wordpress.org/fabiankaegy/) for contributing to this post. [#6-7](https://make.wordpress.org/core/tag/6-7/), [#core](https://make.wordpress.org/core/tag/core/), [#core-performance](https://make.wordpress.org/core/tag/core-performance/), [#performance](https://make.wordpress.org/core/tag/performance/) # Post navigation [← Older posts](https://make.wordpress.org/core/2024/page/2/?output_format=md)