Title: 2025 – Make WordPress Core --- # Yearly Archives: 2025 [ ](https://profiles.wordpress.org/b1ink0/) [Aditya Dhade](https://profiles.wordpress.org/b1ink0/) 5:07 pm _on_ December 24, 2025 Tags: [core-performance ( 144 )](https://make.wordpress.org/core/tag/core-performance/), [hosting ( 49 )](https://make.wordpress.org/core/tag/hosting/), [performance ( 410 )](https://make.wordpress.org/core/tag/performance/), [performance-chat ( 337 )](https://make.wordpress.org/core/tag/performance-chat/), [summary ( 971 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Performance Year-End Chat Summary: 23 December 2025](https://make.wordpress.org/core/2025/12/24/performance-year-end-chat-summary-23-december-2025/)󠁿 The full chat log is available beginning [here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1766505853607859). ## **View Transitions to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.** * [@westonruter](https://profiles.wordpress.org/westonruter/) kicked off the discussion by referencing plans to graduate the [View Transitions plugin](https://wordpress.org/plugins/view-transitions/) into core for WordPress 7.0, noting it pairs well with the adminadmin (and super admin) refresh and introduces theme support for configuration. - [@mikewpbullet](https://profiles.wordpress.org/mikewpbullet/) raised concerns about potential clashes with plugins or custom code and suggested a UIUI User interface checkbox or update splash screen guidance, while [@schmitzoide](https://profiles.wordpress.org/schmitzoide/) proposed a general “Activate Advanced Features” checkbox. - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) noted performance plugins could add controls. - [@westonruter](https://profiles.wordpress.org/westonruter/) clarified that sites could opt out via code toggles like filters or theme support, aligning with WordPress philosophy of decisions over options. * Update: See [#64470](https://core.trac.wordpress.org/ticket/64470) and [#64471](https://core.trac.wordpress.org/ticket/64471). ## Speculative Loading and Caching Enhancements * [@westonruter](https://profiles.wordpress.org/westonruter/) highlighted ticketticket Created for both bug reports and feature development on the bug tracker. [#64066](https://core.trac.wordpress.org/ticket/64066) to shift default eagerness from conservative to moderate when caching is detected, aiding View Transitions by reducing link click delays. - [@mikewpbullet](https://profiles.wordpress.org/mikewpbullet/) raised concerns about page caching rarely helping admin performance and noted that server- side caching via nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. [https://www.nginx.com/](https://www.nginx.com/). or Varnish often runs without WordPress plugins that Site Health could detect. - [@westonruter](https://profiles.wordpress.org/westonruter/) explained that core’s Site Health test already accounts for proxy caches beyond just plugins and remains extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. for improvement. - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) acknowledged that comprehensive coverage is impossible but emphasized WordPress’s advantage in rendering detection rules dynamically. - [@schmitzoide](https://profiles.wordpress.org/schmitzoide/) asked whether Site Health could diagnose performance issues. * [@westonruter](https://profiles.wordpress.org/westonruter/) added that Performance Lab includes additional tests for excessive blocking scripts and styles. - [@westonruter](https://profiles.wordpress.org/westonruter/) responded to [@mikewpbullet](https://profiles.wordpress.org/mikewpbullet/)‘ s earlier admin concerns with two ideas: enabling bfcache in the admin for smooth back/forward transitions [#63636](https://core.trac.wordpress.org/ticket/63636), and considering speculative loading for admin menu items on sites with object caching enabled. * [@mikewpbullet](https://profiles.wordpress.org/mikewpbullet/) raised concerns that users may not want cached admin pages when hitting back, and that object caching is unlikely to help with page load times in admin where slowness comes from 3rd party background requests. ## Admin and Dashboard Performance * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) shared that tackling the Dashboard landing page is a priority for the new year and mentioned an existing performance ticket. [@westonruter](https://profiles.wordpress.org/westonruter/) later identified ticket [#55344](https://core.trac.wordpress.org/ticket/55344) and suggested the Dashboard could leverage preload links for commonly-used resources like the edit post screen assets. - [@westonruter](https://profiles.wordpress.org/westonruter/) connected this to ticket [#57548](https://core.trac.wordpress.org/ticket/57548) about retiring script and style concatenation in wp-admin, explaining the benefit would be effective preloading but noting that concatenation might still offer better performance without a primed cache, which requires benchmarking. This discussion led to exploring Compression Dictionaries, a newer capabilitycapability A ** capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). that [@westonruter](https://profiles.wordpress.org/westonruter/) explained allows browsers to reuse intersecting portions of different concatenated bundles. - [@mikewpbullet](https://profiles.wordpress.org/mikewpbullet/) questioned the need given server-side Brotli compression already exists. - [@westonruter](https://profiles.wordpress.org/westonruter/) clarified this isn’t about PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher-based gzip but about the new [compression dictionary transport](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Compression_dictionary_transport) standard that enables reusing cached bundle portions across different pages, particularly beneficial for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes enqueue block styles on-demand based on page content, and in WordPress 6.9 this also applies to classic themes, so compression dictionaries would allow concatenating these varying bundles while enabling browsers to cache and reuse individual styles across pages with different bundles, significantly reducing CSSCSS Cascading Style Sheets. downloads for both logged-in and logged-out users. ## Roadmap and Future Planning * [@schmitzoide](https://profiles.wordpress.org/schmitzoide/) asked about the team’s roadmap. [@westonruter](https://profiles.wordpress.org/westonruter/) linked to the [2024 roadmap](https://make.wordpress.org/performance/roadmap-2024/) and explained this meeting serves to shape 2026 priorities, noting they’ll likely use milestoned TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets rather than a full roadmap post given fewer active contributors currently. - [@schmitzoide](https://profiles.wordpress.org/schmitzoide/) asked about graduating additional Performance Lab features and shared plans to propose ideas from block theme optimization work via repository tickets. [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) encouraged opening issues for any PerfNow conference ideas worth experimenting with in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.. * [@sirlouen](https://profiles.wordpress.org/sirlouen/) asked about integrating performance testing activities similar to 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/)’ s approach, including 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/) Actions tagging and handbook expansion. [@westonruter](https://profiles.wordpress.org/westonruter/) welcomed aligning testing strategies with other core teams in the new year. **Our next chat will be held on [Tuesday, December 30, 2025 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20251230T1600) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/)**. [#core-performance](https://make.wordpress.org/core/tag/core-performance/), [#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/akshayar/) [Akshaya Rane](https://profiles.wordpress.org/akshayar/) 2:12 pm _on_ December 19, 2025 Tags: [6-9 ( 87 )](https://make.wordpress.org/core/tag/6-9/), [release-process ( 28 )](https://make.wordpress.org/core/tag/release-process/), [retrospective ( 23 )](https://make.wordpress.org/core/tag/retrospective/)    # 󠀁[WordPress 6.9 Release Retrospective](https://make.wordpress.org/core/2025/12/19/wordpress-6-9-release-retrospective/)󠁿 Congratulations to all who helped make WordPress 6.9 possible! Now that the release cycle is complete, you’re invited to reflect and share your thoughts **on the release cycle, release processes, release squad, or whatever else is on your mind**. Feedback loops are critical to learning what works and what doesn’t so that the teams involved can iterate on the processes to improve for future releases. **Everyone is welcome to submit feedback about the release using this form, even contributors who did not contribute directly to the release itself**. A member of the community that casually observes a release cycle will have very different thoughts and opinions than someone who was heavily involved on a weekly or daily basis. The more viewpoints and backgrounds represented within this feedback 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) the better. So please take a moment to [complete the form](https://forms.gle/wqG4triavV2X3dqk8) or leave public feedback in the comments below. **Please note:** the survey is not anonymous, but anything submitted will be anonymized before being shared in a post summarizing the results. Your wordpress.orgWordPress. org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) username is required just case the person processing the responses needs to reach out to you for further clarification. The form and comments will be **open until January 15, 2026**. A follow-up post with the collected, anonymized results will be published shortly after. Again, thank you for your contributions to 6.9 “Gene,” and for taking the time to provide valuable feedback to help make future releases even better! _Props to @amykamala, _[@desrosj](https://profiles.wordpress.org/desrosj/)_ for the peer review_. [#6-9](https://make.wordpress.org/core/tag/6-9/), [#release-process](https://make.wordpress.org/core/tag/release-process/), [#retrospective](https://make.wordpress.org/core/tag/retrospective/) [ ](https://profiles.wordpress.org/desrosj/) [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj/) 9:43 pm _on_ December 18, 2025 Tags: [make.wordpress.org/project ( 18 )](https://make.wordpress.org/core/tag/make-wordpress-org-project/), [p2-xpost ( 209 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: Proposal: 2026 Major Release Schedule](https://make.wordpress.org/core/2025/12/18/xpost-proposal-2026-major-release-schedule/)󠁿 X-comment from [+make.wordpress.org/project](https://make.wordpress.org/project/): Comment on [Proposal: 2026 Major Release Schedule](https://make.wordpress.org/project/2025/12/18/proposal-2026-major-release-schedule/#comment-696) [ ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/) 9:32 pm _on_ December 17, 2025 Tags: [gutenberg-new ( 212 )](https://make.wordpress.org/core/tag/gutenberg-new/) # 󠀁[Gutenberg 22.3 (December 17)](https://make.wordpress.org/core/2025/12/17/gutenberg-22-3-december-17/)󠁿 _“What’s new in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)…” posts (labeled with the [#gutenberg-new](https://make.wordpress.org/core/tag/gutenberg-new/) 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.)) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, [here’s an overview](https://make.wordpress.org/core/2020/05/20/ways-to-keep-up-with-full-site-editing-fse/) of different ways to keep up with Gutenberg and the Editor._ ![](https://make.wordpress.org/core/files/2025/07/gb-21-0-whats-new-1024x512.png) What’s New In Gutenberg 22.3? Gutenberg 22.3 is here and [ready for download](https://wordpress.org/plugins/gutenberg/)! > This release brings a dedicated Fonts page for easier typography management, responsive > Grid layouts, continued progress on the Site Editor’s routing infrastructure, > and improvements to the image editing experience. 1. [Dedicated Fonts page for easier typography management](https://make.wordpress.org/core/2025/12/17/gutenberg-22-3-december-17/#dedicated-fonts-page-for-easier-typography-management) 2. [Image editing improvements](https://make.wordpress.org/core/2025/12/17/gutenberg-22-3-december-17/#image-editing-improvements) 3. [Responsive Grid block](https://make.wordpress.org/core/2025/12/17/gutenberg-22-3-december-17/#responsive-grid-block) 4. [Other highlights](https://make.wordpress.org/core/2025/12/17/gutenberg-22-3-december-17/#other-highlights) 5. [Changelog](https://make.wordpress.org/core/2025/12/17/gutenberg-22-3-december-17/#changelog) 6. [First-time contributors](https://make.wordpress.org/core/2025/12/17/gutenberg-22-3-december-17/#first-time-contributors) 7. [Contributors](https://make.wordpress.org/core/2025/12/17/gutenberg-22-3-december-17/#contributors) ## **Dedicated Fonts page for easier typography management** **[A dedicated Fonts page](https://github.com/WordPress/gutenberg/pull/73630)**  is now available under the Appearance menu for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes. Until now, font management has lived deep inside Global Styles, requiring navigation through several panels to install or preview a font. This new standalone page lets block theme users browse, install, and manage their typography collection in one dedicated space. Support for non-block themes [will come next](https://github.com/WordPress/gutenberg/pull/73876). Under the hood, this page is built on a new routing infrastructure for the Site Editor, designed to improve navigation and support new top-level pages in wp-adminadmin( and super admin). View transitions are [now wired into this routing layer](https://github.com/WordPress/gutenberg/pull/73586), providing early zoom/slide animations when navigating between pages. ## Image editing improvements The in-editor image cropper has been rebuilt on a new foundation. While the workflow remains familiar, you’ll notice improvements: aspect ratios and zoom levels now persist when rotating images, fixing a long-standing frustration. This refactor also lays the groundwork for future image-editing enhancements. ([#72414](https://github.com/WordPress/gutenberg/pull/72414), [#73277](https://github.com/WordPress/gutenberg/pull/73277)) ## Responsive Grid block The Grid block now [adapts to different screen sizes](https://github.com/WordPress/gutenberg/pull/73662) when columns are set. Layouts will adjust naturally across devices, providing a more consistent experience for visitors on mobile and desktop alike. ## Other highlights A few more highlights worth mentioning: * **Email notifications for Notes**: Collaborators can now [get notified when someone leaves a note](https://github.com/WordPress/gutenberg/pull/73645) on their content. No more checking back constantly. * **Breadcrumbs improvements**: The Breadcrumbs block now supports [alignment](https://github.com/WordPress/gutenberg/pull/73794) and handles [paged comments](https://github.com/WordPress/gutenberg/pull/73670) properly. * **Navigation overlays**: A new [overlay template part area](https://github.com/WordPress/gutenberg/pull/73359) gives you more flexibility in how navigation menus behave. * **Better offline handling**: When you lose connection, the editor now gives you [clearer, more helpful error messages](https://github.com/WordPress/gutenberg/pull/73874). ## Changelog ### Enhancements #### Block Editor * Image Cropper: Add package and basic stories. ([72414](https://github.com/WordPress/gutenberg/pull/72414)) * Implements the image-cropper package in the editor. ([73277](https://github.com/WordPress/gutenberg/pull/73277)) #### Block Library * Add support for ‘align’ to the Breadcrumbs block. ([73794](https://github.com/WordPress/gutenberg/pull/73794)) * Breadcrumbs: Support paged comments. ([73670](https://github.com/WordPress/gutenberg/pull/73670)) * Button: Migrate to text-align block support. ([73732](https://github.com/WordPress/gutenberg/pull/73732)) * Comments Pagination Numbers: Add spacing controls for margin and padding. ([67267](https://github.com/WordPress/gutenberg/pull/67267)) #### Components * Chore: Shorten timeout duration for `Snackbar` component. ([73814](https://github.com/WordPress/gutenberg/pull/73814)) * Try: 32px tall menu items. ([73429](https://github.com/WordPress/gutenberg/pull/73429)) #### Data Layer * wordpress/data: Migrate `index.js` to `index.ts`. ([73597](https://github.com/WordPress/gutenberg/pull/73597)) #### DataViews * Add min/max validation support to DataForm inputs. ([73465](https://github.com/WordPress/gutenberg/pull/73465)) * Field 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.: Display formats for `number` and `integer` types. ([73644](https://github.com/WordPress/gutenberg/pull/73644)) * Try using 24px padding for consistency across different uses. ([73334](https://github.com/WordPress/gutenberg/pull/73334)) * Update operator labels and deprecate the `isNotAll`. ([73671](https://github.com/WordPress/gutenberg/pull/73671)) #### Internationalization * Fields: Update “TrashTrash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level( administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days.” translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see [localization](https://make.wordpress.org/core/2025/?output_format=md#l10n), [internationalization](https://make.wordpress.org/core/2025/?output_format=md#i18n). to provide verb context. ([73704](https://github.com/WordPress/gutenberg/pull/73704)) #### Layout * Enable grid block to be responsive when columns are set. ([73662](https://github.com/WordPress/gutenberg/pull/73662)) * Try removing top and left grid drag handles in stable (auto) mode. ([73864](https://github.com/WordPress/gutenberg/pull/73864)) #### Media * Add media-specific fields for use with Attachment post types and DataViews/DataForm.( [73071](https://github.com/WordPress/gutenberg/pull/73071)) #### Notes * Notes: Add email notification. ([73645](https://github.com/WordPress/gutenberg/pull/73645)) #### Offline * Editor: Improve offline error notices. ([73874](https://github.com/WordPress/gutenberg/pull/73874)) #### Packages * Remove WordPress dependencies from abilities package. ([73428](https://github.com/WordPress/gutenberg/pull/73428)) #### Patterns * Add pattern name to document toolbar when editing in spotlight. ([73208](https://github.com/WordPress/gutenberg/pull/73208)) * ContentOnly: For template parts and synced patterns, ensure ‘Edit section’ button goes to the isolated editor. ([73736](https://github.com/WordPress/gutenberg/pull/73736)) #### Post Editor * Use relevance pattern matching for parent page search. ([73836](https://github.com/WordPress/gutenberg/pull/73836)) #### Site Editor * Site Editor Pages: Add “notes count” field. ([73609](https://github.com/WordPress/gutenberg/pull/73609)) #### Theme * Expand error family of tokens. ([73793](https://github.com/WordPress/gutenberg/pull/73793)) ### Bug Fixes #### Block API * Fallback to all attributes when checking for unmodified block. ([73867](https://github.com/WordPress/gutenberg/pull/73867)) #### Block Editor * Link Control: Clear entity metadata when selecting custom URLs. ([73825](https://github.com/WordPress/gutenberg/pull/73825)) * Block Styles: Fix dynamic block previews. ([73709](https://github.com/WordPress/gutenberg/pull/73709)) * Pattern insertion: Drag chip when multiple blocks of the same type in a pattern are dragged. ([73681](https://github.com/WordPress/gutenberg/pull/73681)) #### Block Library * Accordion Heading: Add default style for classic themes. ([73608](https://github.com/WordPress/gutenberg/pull/73608)) * Add i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/2025/?output_format=md#l10n). Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. support for math block error messages.( [73643](https://github.com/WordPress/gutenberg/pull/73643)) * Breadcrumbs: Improve home page and front page handling. ([73487](https://github.com/WordPress/gutenberg/pull/73487)) * Classic Block: Restore HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. editing option.( [73865](https://github.com/WordPress/gutenberg/pull/73865)) * Fix Page List block HTML rendering in editor. ([73614](https://github.com/WordPress/gutenberg/pull/73614)) * Fix Page List block button HTML rendering to escape at output. ([73641](https://github.com/WordPress/gutenberg/pull/73641)) * Fix align right issue on avatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. component. ([67494](https://github.com/WordPress/gutenberg/pull/67494)) * Post Title: Add fallback `no title` in edit mode when is readOnly. ([73750](https://github.com/WordPress/gutenberg/pull/73750)) * Post Title: Fix empty heading element when post_title is empty but get_the_title returns markup V2. ([73841](https://github.com/WordPress/gutenberg/pull/73841)) * Prevent flipping the border style when creating RTL stylesheets. ([44170](https://github.com/WordPress/gutenberg/pull/44170)) * Verse Block: Prevent text overflow off-screen when the previous block has float.( [45221](https://github.com/WordPress/gutenberg/pull/45221)) #### Block Transforms * Gallery: Fix missing captions 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. transform. ([73748](https://github.com/WordPress/gutenberg/pull/73748)) #### Command Palette * Commands: Restrict editor UIUI User interface commands to entity-edit context.( [73717](https://github.com/WordPress/gutenberg/pull/73717)) * Fix layout for long label. ([73837](https://github.com/WordPress/gutenberg/pull/73837)) * Remove context from editor commands. ([73807](https://github.com/WordPress/gutenberg/pull/73807)) #### Components * Fix Notice component action button margins. ([69430](https://github.com/WordPress/gutenberg/pull/69430)) * Reduce modal style specificity so it can be overridden more easily. ([73739](https://github.com/WordPress/gutenberg/pull/73739)) #### DataViews * Apply primary style to first column if there is no title field. ([73729](https://github.com/WordPress/gutenberg/pull/73729)) * Fields: Fix suffix button in Slug field. ([73829](https://github.com/WordPress/gutenberg/pull/73829)) * Fix sticky footer in dataviews grid view. ([73661](https://github.com/WordPress/gutenberg/pull/73661)) #### Font Library * Fix button background and focus outline styles. ([73722](https://github.com/WordPress/gutenberg/pull/73722)) #### Global Styles * Fix: Default color variations not showing in global styles. ([73742](https://github.com/WordPress/gutenberg/pull/73742)) * Global Styles UI: Remove unnecessary padding for Navigatior component. ([73810](https://github.com/WordPress/gutenberg/pull/73810)) * Global Styles UI: Restore borders for preview items. ([73741](https://github.com/WordPress/gutenberg/pull/73741)) * Global Styles UI: Revert some of the padding / markup changes from [#73334](https://core.trac.wordpress.org/ticket/73334).( [73834](https://github.com/WordPress/gutenberg/pull/73834)) * Gutenberg 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.: Override coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. classic theme styles. ([73580](https://github.com/WordPress/gutenberg/pull/73580)) #### Inspector Controls * Fix Hstack prop in PostCardPanel. ([73842](https://github.com/WordPress/gutenberg/pull/73842)) #### Notes * Notes: Avoid incrementing comment_count when notes are resolved or reopened. ( [73689](https://github.com/WordPress/gutenberg/pull/73689)) * Notes: Ensure notes never show on the comments page. ([73640](https://github.com/WordPress/gutenberg/pull/73640)) #### Paste * Raw Handling: Fix grok markdown pasting issues. ([73019](https://github.com/WordPress/gutenberg/pull/73019)) #### Patterns * contentOnly patterns: Mark patterns as contentOnly by adding metadata.patternName to the root block. ([73477](https://github.com/WordPress/gutenberg/pull/73477)) #### Templates API * Template Activation: Update template ID format test. ([73629](https://github.com/WordPress/gutenberg/pull/73629)) ### 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) #### Block Editor * Fix block toolbar icon CSSCSS Cascading Style Sheets. when using show icon label preference. ([73674](https://github.com/WordPress/gutenberg/pull/73674)) ### Performance #### Block Editor * Block Styles: Avoid re-rendering when typing. ([73701](https://github.com/WordPress/gutenberg/pull/73701)) #### Theme * Theme: Better max chroma detection for taperChroma. ([73625](https://github.com/WordPress/gutenberg/pull/73625)) ### Experiments #### Block API * PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher-only blocks: Pass all metadata from PHP registration to the client. ([73556](https://github.com/WordPress/gutenberg/pull/73556)) #### Collaboration * Real-time collaboration: Add UndoManager support for collaborative editing. ( [72407](https://github.com/WordPress/gutenberg/pull/72407)) * Real-time collaboration: Disable syncing for “synthetic” template posts. ([73526](https://github.com/WordPress/gutenberg/pull/73526)) #### Font Library * Add dedicated font library page. ([73630](https://github.com/WordPress/gutenberg/pull/73630)) #### Navigation Menus * Add Overlay template part area behind Experiment. ([73359](https://github.com/WordPress/gutenberg/pull/73359)) * Add overlay template part selector to Navigation block (behind experiment). ( [73760](https://github.com/WordPress/gutenberg/pull/73760)) #### Routing * Boot: Add conditional inspector rendering via route.inspector(). ([73703](https://github.com/WordPress/gutenberg/pull/73703)) * Routing Boot package: Add mobile rendering. ([73620](https://github.com/WordPress/gutenberg/pull/73620)) * Routing: Add page title support. ([73847](https://github.com/WordPress/gutenberg/pull/73847)) * Routing: Add view transitions to the new routing infrastructure. ([73586](https://github.com/WordPress/gutenberg/pull/73586)) #### UI Components * UI: Add border support to Box component. ([73530](https://github.com/WordPress/gutenberg/pull/73530)) * UI: Add Stack component leveraging gap spacing design tokens. ([73308](https://github.com/WordPress/gutenberg/pull/73308)) * UI: Update Stack component to support only gap tokens. ([73852](https://github.com/WordPress/gutenberg/pull/73852)) ### Documentation #### Block API * Block 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. schema: Add visibility key to supports definition. ([73612](https://github.com/WordPress/gutenberg/pull/73612)) * Docs: Add “Migrating Blocks for 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. Editor Compatibility” page. ([73778](https://github.com/WordPress/gutenberg/pull/73778)) * Docs: Add missing periods to example descriptions in block-attributes.md. ([73666](https://github.com/WordPress/gutenberg/pull/73666)) * Update Default block example code. ([65229](https://github.com/WordPress/gutenberg/pull/65229)) #### Components * Docs: Add JSDoc for getUserLabel in users autocompleter. ([73651](https://github.com/WordPress/gutenberg/pull/73651)) #### DataViews * DataViews docs: Add missing props. ([73611](https://github.com/WordPress/gutenberg/pull/73611)) * DataViews stories: Update empty story. ([73619](https://github.com/WordPress/gutenberg/pull/73619)) #### General * Fix a typo in the documentation. ([73658](https://github.com/WordPress/gutenberg/pull/73658)) #### Packages * Docs: Update package documentation with general guidelines. ([73633](https://github.com/WordPress/gutenberg/pull/73633)) #### Storybook * Storybook: Add keywords to icon stories. ([73524](https://github.com/WordPress/gutenberg/pull/73524)) ### Code Quality #### Block bindings * Block Bindings: Componentize. ([73579](https://github.com/WordPress/gutenberg/pull/73579)) #### Block Editor * Fix ESLint warnings for the ‘useInsertionPoint’ hook. ([73868](https://github.com/WordPress/gutenberg/pull/73868)) * Fix block edit component hook dependencies. ([73302](https://github.com/WordPress/gutenberg/pull/73302)) * Remove unused ‘__unstableBlockNameContext’. ([73783](https://github.com/WordPress/gutenberg/pull/73783)) * Remove usage of Emotion. ([73799](https://github.com/WordPress/gutenberg/pull/73799)) * Simplify ‘useSelect’ deps in ‘InserterDraggableBlocks’. ([73687](https://github.com/WordPress/gutenberg/pull/73687)) #### Collaboration * Notes: Simplify editing mode change position tracking. ([73696](https://github.com/WordPress/gutenberg/pull/73696)) #### Components * AlignmentMatrixControl: Fixup style names and nesting. ([73757](https://github.com/WordPress/gutenberg/pull/73757)) * AlignmentMatrixControl: Migrate Emotion to style.module. ([73714](https://github.com/WordPress/gutenberg/pull/73714)) * AnglePickerColor: Migrate Emotion to style.module. ([73786](https://github.com/WordPress/gutenberg/pull/73786)) * FormTokenField, FlatTermSelector: Hard deprecate bottom margin. ([73846](https://github.com/WordPress/gutenberg/pull/73846)) #### DataViews * Field API: Move validation to the field type. ([73642](https://github.com/WordPress/gutenberg/pull/73642)) * Remove extra wrapper for GridItem. ([73665](https://github.com/WordPress/gutenberg/pull/73665)) #### Font Library * Move Font Collection fetching to core-data entities. ([73635](https://github.com/WordPress/gutenberg/pull/73635)) * Move font family fetching and types to core-data. ([73637](https://github.com/WordPress/gutenberg/pull/73637)) * Simplify cache invalidation. ([73639](https://github.com/WordPress/gutenberg/pull/73639)) #### Global Styles * Fix ‘useSelect’ warning. ([73728](https://github.com/WordPress/gutenberg/pull/73728)) * Fix browser warnings in Global Styles. ([73279](https://github.com/WordPress/gutenberg/pull/73279)) * WP_Theme_JSON: use self:: For class private static methods. ([73566](https://github.com/WordPress/gutenberg/pull/73566)) #### Patterns * ContentOnlyControls: Refactor ad hoc fields to use setValue instead of updateBlockAttributes.( [73680](https://github.com/WordPress/gutenberg/pull/73680)) #### Site Editor * Fix ‘useNavigateToPreviousEntityRecord’ internal deps. ([73740](https://github.com/WordPress/gutenberg/pull/73740)) #### Style Book * Fix ESLint warnings. ([73882](https://github.com/WordPress/gutenberg/pull/73882)) #### Theme * Theme: Repurpose Figma token plugin to extract JSON override files for modes.( [73860](https://github.com/WordPress/gutenberg/pull/73860)) * Theme: Restructure theme tokens to embed prefix, flattened modifiers. ([73859](https://github.com/WordPress/gutenberg/pull/73859)) * Theme: Use valid DTCG color format for primitive values. ([73858](https://github.com/WordPress/gutenberg/pull/73858)) #### Write mode * Block Editor: Restore ToolSelector component for backward compatibility. ([73592](https://github.com/WordPress/gutenberg/pull/73592)) ### Tools #### Build Tooling * Attachments controller: Use 6.7 compat method. ([73634](https://github.com/WordPress/gutenberg/pull/73634)) * Fix package side effects for esbuild. ([73795](https://github.com/WordPress/gutenberg/pull/73795)) * Linting: Disable the wordpress dependency group lint rule. ([73616](https://github.com/WordPress/gutenberg/pull/73616)) * 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.: Add Carlos Bravo to mailmap. ([73840](https://github.com/WordPress/gutenberg/pull/73840)) * Meta: Introduce .mailmap for transforming author names. ([72412](https://github.com/WordPress/gutenberg/pull/72412)) * Scripts: Update license checker to ignore 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. package entries. ([73528](https://github.com/WordPress/gutenberg/pull/73528)) * Storybook: Skip transpilation of build-modules files. ([73780](https://github.com/WordPress/gutenberg/pull/73780)) * wp-build: Fix invalid package references for peer dependencies. ([73676](https://github.com/WordPress/gutenberg/pull/73676)) * wp-ui: Add legacy export fields to package.json. ([73850](https://github.com/WordPress/gutenberg/pull/73850)) * Fix CI static analysis on Windows. ([73911](https://github.com/WordPress/gutenberg/pull/73911)) #### Testing * Remove custom import resolvers and package subpath syntax rules. ([72978](https://github.com/WordPress/gutenberg/pull/72978)) * Tests: Emulate form blocks experiments in integration tests. ([73705](https://github.com/WordPress/gutenberg/pull/73705)) * Tests: Update assertion for ‘Global styles 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.’ end-to-end test. ([73685](https://github.com/WordPress/gutenberg/pull/73685)) * Upgrade Playwright to v1.57. ([73686](https://github.com/WordPress/gutenberg/pull/73686)) #### Patterns * Content only and patterns: Detach edit fields from the content only experience.( [73605](https://github.com/WordPress/gutenberg/pull/73605)) ## First-time contributors The following PRs were merged by first-time contributors: * [@badasswp](https://profiles.wordpress.org/badasswp/): Chore: Shorten timeout duration for `Snackbar` component. ([73814](https://github.com/WordPress/gutenberg/pull/73814)) * [@dhasilva](https://profiles.wordpress.org/dhasilva/): DataViews: Apply primary style to first column if there is no title field. ([73729](https://github.com/WordPress/gutenberg/pull/73729)) * [@manhphuc](https://profiles.wordpress.org/manhphuc/): Docs: Add missing periods to example descriptions in block-attributes.md. ([73666](https://github.com/WordPress/gutenberg/pull/73666)) * [@metodiew](https://profiles.wordpress.org/metodiew/): Fix a typo in the documentation.( [73658](https://github.com/WordPress/gutenberg/pull/73658)) ## Contributors The following contributors merged PRs in this release: [@aduth](https://profiles.wordpress.org/aduth/) [@Aljullu](https://profiles.wordpress.org/aljullu/) [@andrewserong](https://profiles.wordpress.org/andrewserong/) [@annezazu](https://profiles.wordpress.org/annezazu/) [@badasswp](https://profiles.wordpress.org/badasswp/) [@cbravobernal](https://profiles.wordpress.org/cbravobernal/)@ chriszarate [@dhasilva](https://profiles.wordpress.org/dhasilva/) [@dmsnell](https://profiles.wordpress.org/dmsnell/) [@getdave](https://profiles.wordpress.org/getdave/) [@gigitux](https://profiles.wordpress.org/gigitux/) [@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/) @Infinite-Null [@ingeniumed](https://profiles.wordpress.org/ingeniumed/) [@jameskoster](https://profiles.wordpress.org/jameskoster/)@ jasmussen [@jeryj](https://profiles.wordpress.org/jeryj/) @jonathanbossenger [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) [@jsnajdr](https://profiles.wordpress.org/jsnajdr/) [@juanfra](https://profiles.wordpress.org/juanfra/)@ lezama [@Mamaduka](https://profiles.wordpress.org/mamaduka/) [@manhphuc](https://profiles.wordpress.org/manhphuc/)@ Mayank-Tripathi32 [@metodiew](https://profiles.wordpress.org/metodiew/) [@mikachan](https://profiles.wordpress.org/mikachan/) [@mirka](https://profiles.wordpress.org/mirka/) [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) [@oandregal](https://profiles.wordpress.org/oandregal/) [@ockham](https://profiles.wordpress.org/ockham/) [@priethor](https://profiles.wordpress.org/priethor/) @ramonjd [@ryelle](https://profiles.wordpress.org/ryelle/) [@scruffian](https://profiles.wordpress.org/scruffian/) @shimotmk [@SirLouen](https://profiles.wordpress.org/sirlouen/)@ t-hamano @tellthemachines [@tyxla](https://profiles.wordpress.org/tyxla/) @Utsav- Ladani [@yogeshbhutkar](https://profiles.wordpress.org/yogeshbhutkar/) [@youknowriad](https://profiles.wordpress.org/youknowriad/) --- _Props to [@youknowriad](https://profiles.wordpress.org/youknowriad/) for the peer review._ [ ](https://profiles.wordpress.org/benjamin_zekavica/) [Benjamin Zekavica](https://profiles.wordpress.org/benjamin_zekavica/) 8:59 pm _on_ December 17, 2025 Tags: [7.0 ( 74 )](https://make.wordpress.org/core/tag/7-0/), [core ( 733 )](https://make.wordpress.org/core/tag/core/), [dev chat ( 911 )](https://make.wordpress.org/core/tag/dev-chat/) # 󠀁[Summary, Dev Chat, December 17, 2025](https://make.wordpress.org/core/2025/12/17/summary-dev-chat-december-17-2025/)󠁿 [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1765983894537809) 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 [@desrosj](https://profiles.wordpress.org/desrosj/) 🔗 [Agenda post](https://make.wordpress.org/core/2025/12/16/dev-chat-agenda-december-17-2025/). 1. [Announcements 📢](https://make.wordpress.org/core/2025/12/17/summary-dev-chat-december-17-2025/#announcements-1) 2. a. [Gutenberg 22.3 has been released!](https://make.wordpress.org/core/2025/12/17/summary-dev-chat-december-17-2025/#gutenberg-22-3-has-been-released) b. [WordCamp Asia 2026 Contributor Day: Call for table leads](https://make.wordpress.org/core/2025/12/17/summary-dev-chat-december-17-2025/#wordcamp-asia-2026-contributor-day-call-for-table-leads) c. [WordPress 6.9 Hotfixes](https://make.wordpress.org/core/2025/12/17/summary-dev-chat-december-17-2025/#wordpress-6-8-3-is-now-available) d. [Planning for WordPress 7.0](https://make.wordpress.org/core/2025/12/17/summary-dev-chat-december-17-2025/#planning-for-wordpress-7-0) e. [Real-time collaboration: Early user feedback](https://make.wordpress.org/core/2025/12/17/summary-dev-chat-december-17-2025/#real-time-collaboration-early-user-feedback) 3. [Discussions 💬](https://make.wordpress.org/core/2025/12/17/summary-dev-chat-december-17-2025/#discussions) 4. a. [Dev Chats Over the Holidays](https://make.wordpress.org/core/2025/12/17/summary-dev-chat-december-17-2025/#wordcamp-asia-2026-contributor-day-call-for-table-leads) **Note: This was the final Dev Chat of 2025.** The next Dev Chat will take place on **January 7, 2026**. Bug scrub meetings may still take place in the meantime. Thanks everyone, and see you in the new year. ## Announcements 📢 ### 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/)󠁿 22.3 has been released! Gutenberg 22.3 is now [available for download](https://wordpress.org/plugins/gutenberg/)! ### WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. 󠀁[Learn more](https://central.wordcamp.org/about/)󠁿. Asia 2026 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://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/)󠁿: Call for table leads Contributors interested in helping with the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team during the [WordCamp Asia 2026](https://asia.wordcamp.org/2026/) Contributor Day can contact [@krupajnanda](https://profiles.wordpress.org/krupajnanda/). ### WordPress 6.9 Hotfixes Since the WordPress 6.9 release, several issues have been reported, temporary workarounds are available as plugins and will be included in a maintenance release **planned for January 2026** at the earliest, with full details in the [linked post](https://make.wordpress.org/core/2025/12/12/wordpress-6-9-hotfixes/). ### Planning for WordPress 7.0 With 6.9 released, attention is already shifting toward WordPress 7.0, including early ideas, focus areas, and ways to contribute, all outlined in the [follow-up post](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/). ### Real-time collaboration: Early user feedback Real-time collaboration for WordPress 7.0 has been in WordPress VIP betaBeta A pre- release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. testing since October 2025, with early feedback covered in [this post](https://make.wordpress.org/core/2025/12/16/real-time-collaboration-early-user-feedback/). ## Discussions 💬 ### Dev Chats Over the Holidays During today’s meeting, it was decided to skip the next two Dev Chat meetings, making today’s meeting the final Dev Chat of the year. Bug scrub meetings may still take place during this time. The next Dev Chat is scheduled for **January 7, 2026.** [#7-0](https://make.wordpress.org/core/tag/7-0/), [#core](https://make.wordpress.org/core/tag/core/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/benjamin_zekavica/) [Benjamin Zekavica](https://profiles.wordpress.org/benjamin_zekavica/) 11:21 pm _on_ December 16, 2025 Tags: [7.0 ( 74 )](https://make.wordpress.org/core/tag/7-0/), [agenda ( 1,134 )](https://make.wordpress.org/core/tag/agenda/), [core ( 733 )](https://make.wordpress.org/core/tag/core/), [dev chat ( 911 )](https://make.wordpress.org/core/tag/dev-chat/)    # 󠀁[Dev Chat Agenda – December 17, 2025](https://make.wordpress.org/core/2025/12/16/dev-chat-agenda-december-17-2025/)󠁿 The next WordPress Developers Chat will take place on [Wednesday, December 17, 2025, at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20251217T1500) 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. The various curated agenda sections below refer to additional items. 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 or bring them up during the dev chat. ## Announcements 📢 ### WordPress 6.9 Hotfixes Since the WordPress 6.9 release, several issues have been reported, temporary workarounds are available as plugins and will be included in a maintenance release **planned for January 2026** at the earliest, with full details in the [linked post](https://make.wordpress.org/core/2025/12/12/wordpress-6-9-hotfixes/). ### Planning for WordPress 7.0 With 6.9 released, attention is already shifting toward WordPress 7.0, including early ideas, focus areas, and ways to contribute, all outlined in the [follow-up post](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/). ### Real-time collaboration: Early user feedback Real-time collaboration for WordPress 7.0 has been in WordPress VIP betaBeta A pre- release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. testing since October 2025, with early feedback covered in [this post](https://make.wordpress.org/core/2025/12/16/real-time-collaboration-early-user-feedback/). ## Discussions 💬 _The discussion section of the agenda is for discussing 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. 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._ ### WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. 󠀁[Learn more](https://central.wordcamp.org/about/)󠁿. Asia 2026 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://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/)󠁿: Call for table leads [@krupajnanda](https://profiles.wordpress.org/krupajnanda/) asked whether contributors would be available to volunteer as table leads for the [WordCamp Asia 2026](https://asia.wordcamp.org/2026/) Contributor Day. **No further topics have been submitted for this discussion round yet.**If you have something in mind, feel free to leave a comment below this post. ## Open floor  🎙️ Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized. Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async. [#7-0](https://make.wordpress.org/core/tag/7-0/), [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core](https://make.wordpress.org/core/tag/core/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/b1ink0/) [Aditya Dhade](https://profiles.wordpress.org/b1ink0/) 5:53 pm _on_ December 16, 2025 Tags: [core-performance ( 144 )](https://make.wordpress.org/core/tag/core-performance/), [hosting ( 49 )](https://make.wordpress.org/core/tag/hosting/), [performance ( 410 )](https://make.wordpress.org/core/tag/performance/), [performance-chat ( 337 )](https://make.wordpress.org/core/tag/performance-chat/), [summary ( 971 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Performance Chat Summary: 16 December 2025](https://make.wordpress.org/core/2025/12/16/performance-chat-summary-16-december-2025/)󠁿 The full chat log is available beginning [here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1765900825826809). ## **WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets** * [@westonruter](https://profiles.wordpress.org/westonruter/) shared that he is still working through fixes for a CSSCSS Cascading Style Sheets. issue introduced in WordPress 6.9 related to loading 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. styles on demand in PR [#10601](https://github.com/WordPress/wordpress-develop/pull/10601). ## **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)** * [@westonruter](https://profiles.wordpress.org/westonruter/) noted that several PRs needs to be reviewed. * [@b1ink0](https://profiles.wordpress.org/b1ink0/) asked for feedback regarding the planned sunsetting of the Web Worker Offloading plugin issue [#2284](https://github.com/WordPress/performance/issues/2284). ## **Open Floor** * [@westonruter](https://profiles.wordpress.org/westonruter/) shared that Safari now supports measuring the LCP metric, which he said will meaningfully improve URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org Metric collection for Optimization Detective - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) wondered whether the team could begin running the performance coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. e2e tests against Safari now that the browser includes this capabilitycapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability).. * [@westonruter](https://profiles.wordpress.org/westonruter/) added that he is interested in exploring Compression Dictionaries after learning they can be implemented in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher with relatively little effort [referenced article](https://www.linkedin.com/posts/erwinhofman_web-performance-html-activity-7405986083219415042-g212). * [@b1ink0](https://profiles.wordpress.org/b1ink0/) shared information regarding the final 2025 meeting to discuss the 2026 roadmap, scheduled for December 23, 2025. **Our next chat will be held on [Tuesday, December 30, 2025 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20251230T1600) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/)**. [#core-performance](https://make.wordpress.org/core/tag/core-performance/), [#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/smithjw1/) [Jacob Smith](https://profiles.wordpress.org/smithjw1/) 4:56 pm _on_ December 16, 2025 Tags: [collaboration ( 3 )](https://make.wordpress.org/core/tag/collaboration/), [phase 3 ( 18 )](https://make.wordpress.org/core/tag/phase-3/)    # 󠀁[Real-time collaboration: Early user feedback](https://make.wordpress.org/core/2025/12/16/real-time-collaboration-early-user-feedback/)󠁿 Real-time collaboration—the ability for multiple users to edit the same post simultaneously, similar to Google Docs—is being developed for [WordPress 7.0](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/), scheduled for release in 2026. Beginning in October 2025, [WordPress VIP](https://wpvip.com/) customers have had access to a betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. version of real-time collaboration to begin stress-testing the experience across different environments and use cases, informing the work as early as possible. The beta has provided valuable insights into how real-time collaboration performs with production WordPress sites and real editorial workflows. The response has been enthusiastic, with several organizations already enabling the feature in production. If you haven’t seen it already, here’s a demo of the feature in action. ## **About the research** This post summarizes feedback gathered from 45 beta participants between October and early December 2025. While the issues are being tracked individually under the [[Type] Real Time Collaboration](https://github.com/WordPress/gutenberg/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BFeature%5D%20Real-time%20Collaboration%22) label, this summary centralizes the information for easier review and broader transparency. The insights come from: * Direct conversations with technical leads and editorial teams at participating organizations. * Recorded testing sessions and demonstrations. * Written feedback submitted through beta feedback channels. * Observations of production and staging deployments. Participating organizations span industries including news and media, higher education, research institutions, and enterprise publishing; all are larger organizations with multi-person editorial teams. ## **Key insight: It just works with modern WordPress** The most consistent feedback: **real-time collaboration works seamlessly when sites are built for modern WordPress**. Organizations using 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 with native WordPress blocks and custom blocks developed using best practices reported smooth experiences with minimal issues. One technical lead at a major research institution noted their team has invested in a deep understanding of 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/) and, as a result, “… have not run into any issues.” Their editorial team described the feature as delivering “an amazing workflow change,” eliminating the frustration of kicking colleagues out of posts to make quick edits. Multiple teams tested the limits by: * Adding dozens of blocks simultaneously. * Copying large amounts of existing content in parallel. * Having entire teams edit the same post together (one team specifically noted “ this is so fun”). In these stress tests with native blocks and modern custom blocks, real-time collaboration held up remarkably well. ## **Other insights** ### **The value of Notes** The newly released [Notes](https://make.wordpress.org/core/2025/11/15/notes-feature-in-wordpress-6-9/) feature generated significant enthusiasm.  One communications team called it “revolutionary.” Teams particularly value the ability to leave contextual feedback directly in the editor without disrupting the editorial flow.  This feedback confirms that collaborative editing is a suite of tools that make it easier for you to create in WordPress from your very first keystroke, not a single feature. ### **Flexible workflows** Different organizations expressed distinct preferences for how collaboration should work within their editorial processes: * **Some teams want flexibility**: Publishers aggregating content from distributed teams appreciate the ability for multiple editors to work simultaneously across different sections of a post. * **Others prefer predictability**: Organizations with established “check-in, check- out” workflows expressed interest in mode controls that would allow them to programmatically determine editing permissions based on user roles and post status.  One organization specifically noted their less technical users might feel “uncomfortable with the shift to a fully collaborative environment, fearing they might step on each other’s toes.” Teams want the ability to adapt the collaboration model to their existing editorial culture rather than completely restructuring workflows. ### **Attribution** Multiple organizations emphasized the need for better attribution tracking. Today, when a user saves a revision, you know they made all changes. With real-time collaboration, multiple users can make changes to the same version. Contributors are working to address this feedback by adding “contributor” metadata for versions. You can follow that work in this [GitHub issue](https://github.com/WordPress/gutenberg/issues/73943). ### **Where things go wrong** The most significant compatibility issues emerged with **blocks storing data in post 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. rather than block attributes**, particularly when that post meta isn’t updated using modern methods. Real-time collaboration works with any post meta that is [registered](https://developer.wordpress.org/reference/functions/register_post_meta/) with `show_in_rest` set to true. Metadata registered this way will participate in the data store that powers real-time collaboration. Legacy metaboxes update meta using other means. This will be an important area to address for WordPress 7.0. 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. authors will want to know what work, if any, is required to ensure their code supports real-time collaboration. ### **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)** The current beta does not meet the accessibility standards expected for WordPress. Providing functional affordances in a real-time environment is challenging, but it is a challenge to be met. This is an area where help is needed from the Accessibility team. You can report any accessibility issues you encounter on this [GitHub tracking issue](https://github.com/WordPress/gutenberg/issues/73942). ## **Going forward** Experimental work in Gutenberg is tracked in a [branch](https://github.com/WordPress/gutenberg/tree/wpvip/rtc-plugin), and it is also being merged upstream to provide [undo support](https://github.com/WordPress/gutenberg/pull/72407) and [post meta syncing](https://github.com/WordPress/gutenberg/pull/72332). If you want to test the beta for real-time collaboration today, you can follow the instructions in this [GitHub repository](https://github.com/Automattic/vip-real-time-collaboration) to set up an environment. You can test locally by editing content in two different browser windows.  Stay tuned for broader dedicated calls for testing and more summaries like this. The aim now is to get everything into Gutenberg trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. to make it easier for more testing in different environments. If you have feedback or questions, please comment here. Issues can be added with the `[Feature] Real-time Collaboration` label [on GitHub](https://github.com/WordPress/gutenberg/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BFeature%5D%20Real-time%20Collaboration%22). Props to [@annezazu](https://profiles.wordpress.org/annezazu/) for reviewing this post. [#collaboration](https://make.wordpress.org/core/tag/collaboration/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/) [ ](https://profiles.wordpress.org/jorbin/) [Aaron Jorbin](https://profiles.wordpress.org/jorbin/) 7:22 pm _on_ December 12, 2025 Tags: [6-9 ( 87 )](https://make.wordpress.org/core/tag/6-9/) # 󠀁[WordPress 6.9 Hotfixes](https://make.wordpress.org/core/2025/12/12/wordpress-6-9-hotfixes/)󠁿 Since being released on December 2, WordPress 6.9 has been [downloaded over nine million times](https://wordpress.org/download/counter/). Shipping is the first step, and core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. [https://core.trac.wordpress.org](https://core.trac.wordpress.org) have been monitoring 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. reports, forum posts, and social networks to see the effects of the release. Issues are analyzed to understand how widespread they are, the impact they have on sites, and if there is a viable workaround available. This is combined with analyzing potential release dates, coordination with other projects that may be necessary, and the riskiness of fixes to decide on a release date for a maintenance release. Please note, only a small subset of sites are facing these issues. For WordPress 6.9, this analysis has led to the decision that a maintenance release will be best in January at the earliest. Some of the reported bugs can be fixed using small code snippets, but not everyone is comfortable editing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher files on their site. To reduce the burden on site administrators who are affected by these reported bugs, these snippets have also been made available as plugins. It is recommended to test your site before installing one of these plugins. ## CSSCSS Cascading Style Sheets. Issues from Loading 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. Styles on Demand WordPress 6.9’s new ability to [load block styles on demand in classic themes](https://make.wordpress.org/core/2025/11/18/wordpress-6-9-frontend-performance-field-guide/#load-block-styles-on-demand-in-classic-themes) has led to some instances where some sites running a classic theme are seeing content styled in unexpected ways due to `wp-block-library` styles being omitted when they were previously included by default. There can also be differences in file loading leading to unexpected changes in the CSS Cascade. See [#64354](https://core.trac.wordpress.org/ticket/64354) for more information and to follow as a permanent fix is developed. The [Load Combined Core Block Assets Plugin](https://wordpress.org/plugins/load-combined-core-block-assets/) by coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. [@westonruter](https://profiles.wordpress.org/westonruter/) is available to help here. ## E-Mails Not Being Sent Some changes aimed at [improving the reliability of email](https://make.wordpress.org/core/2025/11/18/more-reliable-email-in-wordpress-6-9/) have uncovered bugs with some configurations of the underlying libraries and applications used to send email. This means that is some circumstances, WordPress installs that had been able to send emails no longer can. See [#64368](https://core.trac.wordpress.org/ticket/64368) for more information and to follow as a permanent fix is developed. The [Hotfix](https://wordpress.org/plugins/hotfix/) 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., maintained by multiple core committers, has been updated to include a workaround. ## Adjacent Post Navigation Additionally, [a change to adjacent post navigation](https://make.wordpress.org/core/2025/12/10/adjacent-post-navigation-changes-in-wordpress-6-9-and-compatibility-issues/) is leading to some sites seeing infinite loops when modifying the `get_{$adjacent} _post_where` filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.. This change was not previously publicized, but the linked dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes. In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. is now published and highlighted in the [6.9 field guide](https://make.wordpress.org/core/2025/11/25/wordpress-6-9-field-guide/). Please ensure you are using the most up-to-date version of plugins and themes when updating to WordPress 6.9. --- Thank you to the contributors who have tested and reported issues they have seen along. Futher, thank you to the developers who have followed up on these reports and are continuing to work to find solutions that help WordPress users in both the short and long term. As a community project, WordPress would not be able to function without the volunteers and individuals sponsored to work on WordPress Core. If you see an issue, please report it to either [trac](https://core.trac.wordpress.org/newticket) or the [gutenberg repository](https://github.com/WordPress/gutenberg/issues/new/choose) depending on where the issue occurs. Props [@desrosj](https://profiles.wordpress.org/desrosj/) and [@westonruter](https://profiles.wordpress.org/westonruter/) for assisting with drafting this post. [#6-9](https://make.wordpress.org/core/tag/6-9/) [ ](https://profiles.wordpress.org/matveb/) [Matias Ventura](https://profiles.wordpress.org/matveb/) 4:44 pm _on_ December 11, 2025 Tags: [7.0 ( 74 )](https://make.wordpress.org/core/tag/7-0/), [phase 3 ( 18 )](https://make.wordpress.org/core/tag/phase-3/)    # 󠀁[Planning for 7.0](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/)󠁿 With 6.9 [out in the world](https://wordpress.org/download/releases/6-9/), our collective attention has already turned to 7.0. Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. [https://core.trac.wordpress.org](https://core.trac.wordpress.org), together with Matt and Mary, had a call to discuss ideas and projects. There was shared excitement about this release, even if it’s _just_ another number. This post acts as a gathering point for contributors to share what they are starting to work on and to find known areas they can contribute to. There will be another more tactical follow up with release schedule and responsibilities, this one is about the initial scope. **How to interact with this post** Please do not use this as a spot to request folks to work on features. 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/) and TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are the best places to share feedback, talk about impact, and advocate for issues.  Please use this post to share what you are working on, including areas you’d like to help with that may be listed here, as well as areas that you are working on that are not. Items with TBD indicate areas where contributors are needed so please comment below if you’re keen to work on those pieces. If you were planning to work in an area listed below and don’t see your name, please be sure to comment as well and it’ll be updated. It’s intentional that this post is meant to be a place to shore up who is working on what out in the open at this early stage. Also note this is neither comprehensive nor yet a commitment that all of these things will be part of 7.0, since many are in early stages and may not make this release. Items marked with ✅ mean the work is already merged 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/) or trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. **Table of Contents** * [Collaboration ](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#collaboration) * [Admin](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#admin) * [APIs](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#apis) * [Navigation Block](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#navigation-block) * [Customization](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#customization) * [Blocks](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#blocks) * [Media](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#media) ## Collaboration  The project is getting deeper into Phase 3: Collaboration. Notes was a highlight feature in WP6.9 and there’s several improvements already planned to make it even more powerful and resilient. **Real time collaboration** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/52593) * Key considerations: - There’s been a lot of progress in defining the UIUI User interface and the diffing mechanics for reconciling changes. It’s in very good shape and needs to be reviewed and tested diligently, especially around compatibility with third-party blocks and plugins. - This feature has a stronger dependency on server support and infrastructure than usual WordPress features, so there needs to be a definition of what’s the baseline experience shipping in WordPress (for example, peer-to-peer with 1 or 2 connections) and how it can be augmented, either by WP.org, hosting providers, or plugins. * Contributors: [@acicovic](https://profiles.wordpress.org/acicovic/), [@aduth](https://profiles.wordpress.org/aduth/), [@alecgeatches](https://profiles.wordpress.org/alecgeatches/), [@czarate](https://profiles.wordpress.org/czarate/), [@ingeniumed](https://profiles.wordpress.org/ingeniumed/), [@jsnajdr](https://profiles.wordpress.org/jsnajdr/),@ maxschmelingkc, [@paulkevan](https://profiles.wordpress.org/paulkevan/), [@shekharnwagh](https://profiles.wordpress.org/shekharnwagh/), [@youknowriad](https://profiles.wordpress.org/youknowriad/) **Notes i2** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73260) * Key considerations: - Support partial selection inside 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. rich text fields. - A “suggestions” mode and interface that allows Notes to refer to specific content within a block and apply the suggestions. - Support for multi-block notes. - Add rich text support in the comments. - Develop a dashboard 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. for recent notes. - More notification options (responses, follow a note, mentions). * Contributors: [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/), [@mamaduka](https://profiles.wordpress.org/mamaduka/) --- ## Adminadmin (and super admin) **Improving screens across wp-admin** * Link: TBD * Key considerations: - [Explore CSS improvements](https://core.trac.wordpress.org/ticket/64308) that can modernize the look and feel. For example, consider making the “modern” admin color scheme the default. - Admin bar and editor “site hub” improvements. Make the W menu item filterable. Possibly start work as an experiment in Gutenberg. - Consider a “This time last year” widget for bloggers. - Bring grid layout customization to dashboard experience or other screens. ( Possible widgets at the top of comments, etc). * Contributors: TBD, [@fabiankaegy](https://profiles.wordpress.org/fabiankaegy/), [@karmatosed](https://profiles.wordpress.org/karmatosed/), [@mcsf](https://profiles.wordpress.org/mcsf/) **DataViews and DataForms iterations** * Link: [7.0 iteration issue](https://github.com/WordPress/gutenberg/issues/73076) * Key considerations: - DataForms/QuickEdit/Document inspector design iterations. - Hierarchical post visualization. - Make DataViews screens extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. in the site editor (templates, pages, etc). * Contributors: [@oandregal](https://profiles.wordpress.org/oandregal/) **Design System** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/71196) * Key considerations: - Components are already being worked on in wordpress/ui. - **✅ **Theming system with design tokens using wordpress/theme. - Start replacing key parts of the editor UI with improved components (tabs, flyout menus). * Contributors: [@0mirka00](https://profiles.wordpress.org/0mirka00/), [@aduth](https://profiles.wordpress.org/aduth/), [@jsnajdr](https://profiles.wordpress.org/jsnajdr/), [@mciampini](https://profiles.wordpress.org/mciampini/), [@wildworks](https://profiles.wordpress.org/wildworks/) **Font library admin section** * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/57904) * Key considerations: - **✅ **Support for block themes. - Support for hybrid/classic themes. * Contributors: [@youknowriad](https://profiles.wordpress.org/youknowriad/) **RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. ** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/52138) * Key tasks: - Rethink the revisions interface to be more modern, intuitive, and work with blocks. - Show visual diffs.  - Bonus: potentially tie in with collaborative editing, suggestions, and undo management. * Contributors: [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) **Customizable Keyboard Shortcuts** * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/3218) * Key considerations: - Build with design system components. * Contributors: TBD --- ## APIs **Abilities & Workflows 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.** * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/70710) * Key considerations: - Hybrid abilities. - **✅ **The client side package. - Driven by Fields API definitions.  - Querying and filtering functionality for the abilities. - Implement some of the abilities [outlined in WordPress Core Abilities](https://github.com/WordPress/ai/issues/40). - Command palette and UI: * Differentiation between commands. * Ability to support two stages of a command. * Contributors: [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) [@gziolo](https://profiles.wordpress.org/gziolo/) [@senadir](https://profiles.wordpress.org/senadir/) [@youknowriad](https://profiles.wordpress.org/youknowriad/) **Upgrade to 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/) 19** * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/71336) * Key considerations: - There’s a path for the block editor in the mobile apps that should remove this dependency blockerblocker A bug which is so severe that it blocks a release.. - Ecosystem impact. * Contributors: [@aduth](https://profiles.wordpress.org/aduth/) [@jsnajdr](https://profiles.wordpress.org/jsnajdr/) [@mamaduka](https://profiles.wordpress.org/mamaduka/) [@ralucastn](https://profiles.wordpress.org/ralucastn/) [@tyxla](https://profiles.wordpress.org/tyxla/) **Block API: Add validation levels** * Links: [Github issue](https://github.com/WordPress/gutenberg/issues/21703) with [initial PR** **](https://github.com/WordPress/gutenberg/pull/73116) * Key considerations: - The scope of this issue is to drastically reduce the amount of times a user sees a “this block is broken” message. - Impact on block API. * Contributors: [@matveb](https://profiles.wordpress.org/matveb/) [@mcsf](https://profiles.wordpress.org/mcsf/) [@youknowriad](https://profiles.wordpress.org/youknowriad/) **Enforced iframed editor** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73138). - Backwards compatibility, extended testing. - **✅ **MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. guide. * Contributors: [@ellatrix](https://profiles.wordpress.org/ellatrix/), [@wildworks](https://profiles.wordpress.org/wildworks/) **WP client AI API** * Link: [GitHub project](https://github.com/WordPress/wp-ai-client) * Key considerations: - An AI client and API for WordPress to communicate with any generative AI models of various capabilitiescapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts ( the “edit_posts” capability), but not permission to edit other users’ posts( the “edit_others_posts” capability). using a uniform API. - Integration with Abilities API. - Strictly no providers included in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. - Decide nomenclature. - Ideally, the minimum PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version has to be bumped from PHP 7.2. * Contributors: [@flixos90](https://profiles.wordpress.org/flixos90/) [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) **Creating blocks and patterns on the server** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/71792) * Key considerations: - Most of the tools for a pretty straightforward PHP-only representation of blocks and patterns, including bindings, are ready. - Declarative block attributes and form components. - Pattern creation and syntax that allows easy construction of blocks and bindings. * Contributors: [@priethor](https://profiles.wordpress.org/priethor/), TBD **wordpress/build and routing (site editor)** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/70862); [Scripts issue](https://github.com/WordPress/gutenberg/issues/72032) * Key considerations. - Add extensibility to site editor routing. - Dependency on standalone font library. - Refactor the site editor to allow 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. authors to add their pages there. - **✅ **Opinionated build tool for plugins. - Update Gutenberg – Core backportbackport A port is when code from one branch( or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. flow. * Contributors: [@youknowriad](https://profiles.wordpress.org/youknowriad/)  **Shortblocks** * Links: [Bits as dynamic tokens](https://make.wordpress.org/core/2024/06/08/proposal-bits-as-dynamic-tokens/); [Bits: Introduce the ability to store and render bits](https://github.com/WordPress/wordpress-develop/pull/6390), [Rich text: try BITS with block binding API](https://github.com/WordPress/gutenberg/pull/60735), [Introduce parser for dynamic token system](https://github.com/WordPress/gutenberg/pull/42015). * Key considerations: - Decide name for the feature (shortblocks, inline blocks, bits). - Determine best syntax. - Connect with bindings UI. - Support for rich text autocomplete. * Contributors: [@dmsnell](https://profiles.wordpress.org/dmsnell/), [@ellatrix](https://profiles.wordpress.org/ellatrix/), [@jonsurrell](https://profiles.wordpress.org/jonsurrell/) **Block bindings iterations** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73467) * Key considerations: - [Open up “Pattern Overrides” and therefore intern block bindings to custom dynamic blocks](https://href.li/?https://github.com/WordPress/gutenberg/issues/64870). - [Filter available source items for a given attribute by format](https://href.li/?https://github.com/WordPress/gutenberg/issues/72446). - Align with Fields API as a requirement.  * Contributors: [@bernhard-reiter](https://profiles.wordpress.org/bernhard-reiter/) --- ## Navigation Block A series of improvements were identified to simplify the navigation workflow and make the experience of managing menus more intuitive and straightforward. **Simpler navigation editing** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/65699) * Key considerations: - [Better insertion](https://github.com/WordPress/gutenberg/issues/73647). - [Pattern editing and ContentOnly interactivity](https://github.com/WordPress/gutenberg/issues/71517). - Better presentation of “bound” page items. * Contributors: [@get_dave](https://profiles.wordpress.org/get_dave/), [@jeryj](https://profiles.wordpress.org/jeryj/) **Ability to customise “mobile” overlay ** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73084) * Key considerations: - Implemented as a template part. - Ability to customize when the overlay appears (breakpoint settings) just for navigation overlay. * Contributors: [@get_dave](https://profiles.wordpress.org/get_dave/), [@jeryj](https://profiles.wordpress.org/jeryj/) --- ## Customization Over the past couple years we’ve been iterating on a series of related systems with the hope of arriving at a more streamlined editing experience of composite blocks and design patterns. We have some solid directions sketched out that are looking promising. **Explore more intuitive page navigation in the site editor** * Link: TBD * Key considerations: - Modify the title bar to display a pages dropdown instead of empty command palette. List the pages used in the primary menu with a link to “browse all pages”. [Exploration](https://github.com/WordPress/gutenberg/pull/73631). - Add next/previous page links in zoomed-out view, similar to a carousel. See a preview in a zoomed out state with arrows next to preview or title bar. [Exploration](https://github.com/WordPress/gutenberg/pull/73628). * Contributors: [@ellatrix](https://profiles.wordpress.org/ellatrix/) **Pattern Editing (aka ContentOnly)** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/71517) * Key considerations: - Ensure proper discoverability to enter/exit. - Ensure it works well with synced patterns.  * Contributors: [@aaronrobertshaw](https://profiles.wordpress.org/aaronrobertshaw/), [@andrewserong](https://profiles.wordpress.org/andrewserong/), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/), [@ramonopoly](https://profiles.wordpress.org/ramonopoly/) [@talldanwp](https://profiles.wordpress.org/talldanwp/). **Improve template management** * Link: [GitHub PR](https://github.com/WordPress/gutenberg/pull/67125) * Key considerations: - Direction and UXUX User experience is still TBD and needs more exploration. - [Retain access to template parts across theme switches](https://github.com/WordPress/gutenberg/issues/72452). * Contributors: [@ellatrix](https://profiles.wordpress.org/ellatrix/) [@scruffian](https://profiles.wordpress.org/scruffian/). **Responsive editing mode** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/19909) * Key considerations: - Toggle to engage responsive editing mode. - Block visibility i2: [add ability to hide blocks based on screen size](https://github.com/WordPress/gutenberg/issues/72502). - Allow style changes to be saved and retrieved for different breakpoints. - Allow customization of hardcoded breakpoints. * Contributors: [@matveb](https://profiles.wordpress.org/matveb/) [@ramonopoly](https://profiles.wordpress.org/ramonopoly/) **Block supports and design tools:  ** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73772) * Key considerations: - Add text line indent support. [GitHub PR](https://github.com/WordPress/gutenberg/pull/73114). - Add [gradient support to text color options](https://github.com/WordPress/gutenberg/issues/30982). - [Add height block support to dimension ](https://github.com/WordPress/gutenberg/pull/71914). - Styles support for text shadow. [GitHub PR](https://github.com/WordPress/gutenberg/pull/73320). - Support for text alignment [with justify support](https://github.com/WordPress/gutenberg/issues/50319). - [Allow Video backgrounds to be ‘Fixed’](https://github.com/WordPress/gutenberg/issues/52585). - [Balanced line wrap](https://github.com/WordPress/gutenberg/issues/52387). - Text columns. [GitHub issue](https://github.com/WordPress/gutenberg/issues/27118); [GitHub issue](https://github.com/WordPress/gutenberg/issues/25459). - Support aspect ratio [on wide and full images](https://github.com/WordPress/gutenberg/issues/53652). * Contributors: TBD, [@aaronrobertshaw](https://profiles.wordpress.org/aaronrobertshaw/) [@matveb](https://profiles.wordpress.org/matveb/) [@youknowriad](https://profiles.wordpress.org/youknowriad/) [@wildworks](https://profiles.wordpress.org/wildworks/) --- ## Blocks Keeping the momentum [on adding new blocks](https://github.com/WordPress/gutenberg/issues/71026) and new block tools to expand the palette and expressiveness offered to theme builders and users. There’s also some refinements to some fundamental aspects of blocks to make them more resilient and more consistent. **Group block attributes** * Link: [GitHub Issue](https://github.com/WordPress/gutenberg/issues/73845) * Key considerations: - Adding groups to InspectorControls (like BlockControls). - Add support for list representation to block API based on nav block work. - Implement content representation for media and rich text attributes. (Connected with contentOnly, bindings, and partially synced patterns work.) * Contributors: TBD **✅ Cover block: video embeds** * Link: [GitHub Issue](https://github.com/WordPress/gutenberg/issues/28860); [GitHub PR](https://github.com/WordPress/gutenberg/pull/73023) * Contributors: [@matveb](https://profiles.wordpress.org/matveb/)  **Modernize Code editor + Code block** * Link: [GitHub link](https://github.com/WordPress/gutenberg/issues/10423) * Contributors: [@jonsurrell](https://profiles.wordpress.org/jonsurrell/), [@westonruter](https://profiles.wordpress.org/westonruter/) **Lazy load the Classic block** * Link: TBD * Key considerations: - The main aim is performance—avoid loading TinyMCE by default if not needed. - If possible, address [moving the freeform block to a separate package](https://github.com/WordPress/gutenberg/pull/70603#top) in this work too. * Contributors: [@tyxla](https://profiles.wordpress.org/tyxla/) **Leverage iAPI for instant search block & submit comments without full page refresh** * Links: [Instant Search](https://href.li/?https://github.com/WordPress/gutenberg/pull/67181), [submit comments without requiring a full-page refresh](https://href.li/?https://github.com/WordPress/gutenberg/pull/53737). * Contributors: TBD **Writing flow + drag and drop improvements** * Link: [GitHub issue](https://href.li/?https://github.com/WordPress/gutenberg/issues/63255) * Key considerations: - Get to a place where the drag handle from the toolbar can be entirely removed due to improved drag and drop functionality. - Making multi selection work on touch devices. - [Improvements to inline insertion](https://github.com/WordPress/gutenberg/issues/73581) and inline images. * Contributors: [@ellatrix](https://profiles.wordpress.org/ellatrix/) **✅ Tabs block ** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73230) * Contributors: [@mikachan](https://profiles.wordpress.org/mikachan/) **Release the Table of Contents block ** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/42229) * Contributors: TBD  **Playlist block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/805) * Contributors: [@scruffian](https://profiles.wordpress.org/scruffian/) **Slider block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/43369), [GitHub issue](https://github.com/WordPress/gutenberg/issues/25501), [GitHub issue](https://github.com/WordPress/gutenberg/issues/25502) * Contributors: [@lstraczynski](https://profiles.wordpress.org/lstraczynski/), [@karolmanijak](https://profiles.wordpress.org/karolmanijak/) **Dialog block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/pull/71618) * Contributors: TBD **✅ Breadcrumb block** * Link: [GitHub Issue](https://github.com/WordPress/gutenberg/issues/72498) * Team: [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) **Add more dynamic URLs via block bindings to Buttons block and Image block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/18345#issuecomment-3400461363), [API shape](https://github.com/WordPress/gutenberg/issues/72426) * Team: TBD **Icon block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/16484) * Key considerations: - Ship with a default set made out of some wordpress/icons. - Allow extenders to register their own sets. * Contributors: [@mcsf](https://profiles.wordpress.org/mcsf/) [@welcher](https://profiles.wordpress.org/welcher/) **Gallery block: add lightbox support with the ability to switch between images** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/56310), [GitHub PR](https://github.com/WordPress/gutenberg/pull/62906#issuecomment-3535417814) * Contributor: [@wildworks](https://profiles.wordpress.org/wildworks/) **Introduce heading levels as Heading block variations** * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/42181); [https://github.com/WordPress/gutenberg/issues/42181](https://github.com/WordPress/gutenberg/issues/42181) * Key considerations: - Show up in search and slash inserter. - Easy toggling in 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. inspector and transforms. * Contributor: [@matveb](https://profiles.wordpress.org/matveb/) **Aim to stabilize grid block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73773) * Contributor: [@isabel_brison](https://profiles.wordpress.org/isabel_brison/) --- ## Media **Client side media work** * Link: [GitHub issue ](https://github.com/WordPress/gutenberg/issues/61447) * Contributors: [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/), [@ramonopoly](https://profiles.wordpress.org/ramonopoly/) **Media editor** * Link: [Iteration issue](https://github.com/WordPress/gutenberg/issues/73771) * Contributors: [@aaronrobertshaw](https://profiles.wordpress.org/aaronrobertshaw/), [@andrewserong](https://profiles.wordpress.org/andrewserong/), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/), [@ramonopoly](https://profiles.wordpress.org/ramonopoly/), [@talldanwp](https://profiles.wordpress.org/talldanwp/) --- Designers looking across all these projects: [@fcoveram](https://profiles.wordpress.org/fcoveram/), [@joen](https://profiles.wordpress.org/joen/), [@jameskoster](https://profiles.wordpress.org/jameskoster/), [@mattmiklic](https://profiles.wordpress.org/mattmiklic/). [#7-0](https://make.wordpress.org/core/tag/7-0/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/) # Post navigation [← Older posts](https://make.wordpress.org/core/2025/page/2/?output_format=md)