Title: Make WordPress Core – Page 3 – WordPress Development Updates --- [ ](https://profiles.wordpress.org/desrosj/) [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj/) 8:54 pm _on_ April 29, 2026 Tags: [make.wordpress.org/hosting ( 7 )](https://make.wordpress.org/core/tag/make-wordpress-org-hosting/), [p2-xpost ( 207 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: Urgent: Testing request to Web hosts for collaborative editing by May 4th](https://make.wordpress.org/core/2026/04/29/xpost-urgent-testing-request-to-web-hosts-for-collaborative-editing-by-may-4th/)󠁿 X-comment from [+make.wordpress.org/hosting](https://make.wordpress.org/hosting/): Comment on [Urgent: Testing request to Web hosts for collaborative editing by May 4th](https://make.wordpress.org/hosting/2026/04/29/urgent-testing-request-to-web-hosts-for-collaborative-editing-by-may-4th/#comment-749) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F04%2F29%2Fxpost-urgent-testing-request-to-web-hosts-for-collaborative-editing-by-may-4th%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/amykamala/) [Amy Kamala](https://profiles.wordpress.org/amykamala/) 6:51 am _on_ April 29, 2026 Tags: [7.0 ( 68 )](https://make.wordpress.org/core/tag/7-0/), [agenda ( 1,128 )](https://make.wordpress.org/core/tag/agenda/), [core ( 727 )](https://make.wordpress.org/core/tag/core/), [core-privacy ( 53 )](https://make.wordpress.org/core/tag/core-privacy/), [dev chat ( 905 )](https://make.wordpress.org/core/tag/dev-chat/) # 󠀁[Dev Chat Agenda – April 29, 2026](https://make.wordpress.org/core/2026/04/29/dev-chat-agenda-april-29-2026/)󠁿 The next WordPress Developers Chat will take place on [Wednesday, April 29, 2026, at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260429T1500) 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 7.0 * [RC3 (“new Beta 1”) is scheduled for Friday, May 8th](https://make.wordpress.org/core/2026/04/22/wordpress-7-0-release-party-updated-schedule/) * Testing and feedback needed from web hosts ### **General** * Introducing the [Presence API Feature Plugin](https://make.wordpress.org/core/2026/04/27/presence-api-feature-plugin/) ## 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._ * WordPress 7.0 is currently on track for May 20th. Temperature check: How are folks feeling? ## 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. _Props to [@kirasong](https://profiles.wordpress.org/kirasong/) for proofreading and review_ [#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/), [#core-privacy](https://make.wordpress.org/core/tag/core-privacy/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F04%2F29%2Fdev-chat-agenda-april-29-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/joefusco/) [Joe Fusco](https://profiles.wordpress.org/joefusco/) 2:52 pm _on_ April 27, 2026 Tags: [performance ( 408 )](https://make.wordpress.org/core/tag/performance/), presence-api    # 󠀁[Presence API Feature Plugin](https://make.wordpress.org/core/2026/04/27/presence-api-feature-plugin/)󠁿 The [Presence API](https://github.com/WordPress/presence-api) is an experimental feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See [Features as Plugins](https://make.wordpress.org/core/handbook/about/release-cycle/features-as-plugins/) that provides a system-wide awareness layer — who is logged in, what adminadmin ( and super admin) screens they are on, and which posts they are editing. > This idea of presence I think is really cool and seeing where people are… you > log into your WordPress, I see oh Matias is moderating some comments, Lynn is > on the dashboard maybe reading some news… that idea of like you log in and you > can kind of see the neighborhood of like who else is also there. > [Matt Mullenweg, WordPress 7.0 planning session](https://youtu.be/F-xMPY9WqG4?si=YK0rIUM2nuYy7x45&t=2435) ## Problems this aims to solve * There is currently no way to see who else is logged into the WordPress admin at the same time. * Posts being actively edited by another user are only surfaced when a lock collision occurs, by which point work may already overlap. * The post list provides no indication of which posts have active editors until a user tries to open one. Here’s what that looks like in practice: **Try it yourself in WordPress Playground:** [5-user blueprint](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/WordPress/presence-api/main/blueprint.json). The blueprint creates 5 editor accounts with live presence spread across admin screens and posts, so the widgets, admin bar, and post list are populated the moment Playground boots — no second browser or incognito window needed. **See it at scale:** [40-user blueprint](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/WordPress/presence-api/main/blueprint-40.json). Same setup, 40 seeded editors — useful for seeing how the widgets, admin bar, and post list handle density. ## What 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. provides * Dashboard widgets: “Who’s Online” and “Active Posts” * Admin bar online indicator with 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. stack for on-screen presence * Post list “Editors” column * Users list “Online” 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. * REST endpoints and WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) commands * Post-lock bridge (coexists with existing _edit_lock behavior) All features are gated on the `edit_posts` 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).. Full technical details are in the [GitHub repository](https://github.com/WordPress/presence-api). ## Background During WordPress 7.0 development, discussion in [#64696](https://core.trac.wordpress.org/ticket/64696) identified that storing high-frequency ephemeral data in shared tables causes persistent cache invalidation site-wide. This feature plugin was built to test that workload independently using a dedicated ephemeral data table with a 60-second TTL. Data flows through the existing [Heartbeat API](https://developer.wordpress.org/plugins/javascript/heartbeat-api/). The plugin [was presented](https://wordpress.slack.com/archives/C02RQBWTW/p1775058108549209) at a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat and [subsequently transferred](https://wordpress.slack.com/archives/C02RQBWTW/p1775060126084079) to the WordPress 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/) organization. It was submitted to the 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/) plugin directory on April 6, 2026. ## Feedback welcome This plugin is experimental. Feedback on the following is especially helpful: * Are the UIUI User interface surfaces (widgets, admin bar, post list) useful as presented? * Are there admin screens or workflows where presence would be valuable? Discussion and development: [#feature-presence-api](https://wordpress.slack.com/archives/C0ASCNMB7FZ) on WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) Bug reports and discussion: [GitHub Issues](https://github.com/WordPress/presence-api/issues) Thank you to [@jorbin](https://profiles.wordpress.org/jorbin/) and [@desrosj](https://profiles.wordpress.org/desrosj/) for helping to stand up this feature plugin. Props [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/), [@mindctrl](https://profiles.wordpress.org/mindctrl/), [@czarate](https://profiles.wordpress.org/czarate/), [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/), [@dd32](https://profiles.wordpress.org/dd32/), [@maxschmeling](https://profiles.wordpress.org/maxschmeling/), and [@westonruter](https://profiles.wordpress.org/westonruter/) for the architectural discussion in [#64696](https://core.trac.wordpress.org/ticket/64696) that informed this work. [#performance](https://make.wordpress.org/core/tag/performance/), [#presence-api](https://make.wordpress.org/core/tag/presence-api/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F04%2F27%2Fpresence-api-feature-plugin%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/luisherranz/) [luisherranz](https://profiles.wordpress.org/luisherranz/) 1:11 pm _on_ April 22, 2026   # 󠀁[What’s new in Gutenberg 23.0? (22 April)](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/)󠁿 “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 23.0? Gutenberg 23.0 has been released and is [available for download](https://wordpress.org/plugins/gutenberg/)! This release introduces a 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. panel for templates, template parts, and patterns (experimental), and extends the Site Editor’s Design › Identity panel with Site Title and Site Tagline fields, completing the set alongside the previously added Site Logo and Icon. Real-time collaboration gains compatibility with legacy metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. boxes and a range of reliability improvements, while 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 receives several quality-of-life refinements. A total of [174 PRs](https://github.com/WordPress/gutenberg/pulls?q=is%3Apr+milestone%3A%22Gutenberg+23.0%22+is%3Aclosed+) were merged in Gutenberg 23.0, with 8 first-time contributors. **Table of contents** 1. [Revisions panel in templates, template parts, and patterns (experimental)](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#revisions-panel-in-templates-template-parts-and-patterns-experimental) 2. [Site Title and Site Tagline in the Design › Identity panel](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#site-title-and-site-tagline-in-the-design-identity-panel) 3. [Other Notable Highlights](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#other-notable-highlights) 4. [Note for users of the Guidelines experiment](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#note-for-users-of-the-guidelines-experiment) 5. [Changelog](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#changelog) 6. a. [Enhancements](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#enhancements) b. [Bug Fixes](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#bug-fixes) c. [Accessibility](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#accessibility) d. [Performance](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#performance) e. [Experiments](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#experiments) f. [Documentation](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#documentation) g. [Code Quality](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#code-quality) h. [Tools](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#tools) 7. [First-time contributors](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#first-time-contributors) 8. [Contributors](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/#contributors) ## Revisions panel in templates, template parts, and patterns (experimental) [[ Editing a template, template part, or pattern now surfaces the same Revisions panel previously available only for posts and pages. When any of these entities has revisions, a Revisions row appears in the 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. with access to review and restore prior versions, matching the behavior already in place for regular post types. This is part of the ongoing `Editor Inspector: Use DataForm` experiment, which is progressively rolling out a unified DataForm-based inspector across all post types. Enable the experiment from **Gutenberg → Experiments** to try it in the Site Editor or while editing a template from the Post Editor. ([#77008](https://github.com/WordPress/gutenberg/pull/77008)) ## Site Title and Site Tagline in the Design › Identity panel [[ The **Design › Identity** panel — introduced in 22.8 with Site Logo and Site Icon— now also includes Site Title and Site Tagline. All four identity settings sit in a single panel, editable directly from the Site Editor without a trip to Settings → General. Because the title and tagline fields write to the same `root/site` entity that the Site Title and Site Tagline blocks read from, edits show up live in the editor canvas as you type. The panel uses consistent field styling across text and media controls, so the four settings read as one unified form. ([#76264](https://github.com/WordPress/gutenberg/pull/76264)) ## Other Notable Highlights * **Real-time Collaboration, legacy meta box compatibility.** 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 can now mark individual meta boxes as RTC-compatible using a new `__rtc_compatible_meta_box` flag, so the presence of a legacy meta box no longer unconditionally disables collaboration. Site administrators can also apply the flag to third-party meta boxes via the existing `filter_block_editor_meta_boxes` hook. ([#76939](https://github.com/WordPress/gutenberg/pull/76939)) * **Real-time Collaboration, reliability.** Concurrent edits to array-type block attributes — such as table rows — are now preserved when the array is restructured( [#77164](https://github.com/WordPress/gutenberg/pull/77164)). A single corrupted sync update no longer crashes the whole poll cycle and disconnects every room( [#76968](https://github.com/WordPress/gutenberg/pull/76968)). Gutenberg’s activation hook now honors the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. `WP_ALLOW_COLLABORATION` constant, giving hosts a reliable kill switch ([#77084](https://github.com/WordPress/gutenberg/pull/77084)). * **Keyboard shortcuts for moving blocks surface in tooltips.** The block toolbar’s move-up / move-down tooltips now display their keyboard shortcuts. ([#76992](https://github.com/WordPress/gutenberg/pull/76992)) * **Spacing side controls re-order when unlinked.** When link mode is off, the four side inputs are arranged in a more predictable order. ([#66317](https://github.com/WordPress/gutenberg/pull/66317)) * **Separator block honors the `---` shortcut’s default variation.** Inserting a Separator via the Markdown-style `---` shortcut now applies the block’s default style variation, matching the behavior of inserting it through the inserter. ( [#77135](https://github.com/WordPress/gutenberg/pull/77135)) ## Note for users of the Guidelines experiment If you had the **Guidelines** experiment enabled in a previous release, 23.0 renames its internal identifiers from `content-guidelines` / `content_guideline` to `guidelines`/` guideline`. The rename covers the custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. slug, REST base, meta keys, experiment flag, and Redux store. Because the experiment flag itself is renamed, it will appear disabled after updating — you’ll need to re-enable it from **Gutenberg → Experiments** and re-enter any previously saved guidelines. ([#77147](https://github.com/WordPress/gutenberg/pull/77147), [#77223](https://github.com/WordPress/gutenberg/pull/77223)) ## Changelog ### Enhancements #### Components * wordpress/ui: Add global CSSCSS Cascading Style Sheets. defense module. ([76783](https://github.com/WordPress/gutenberg/pull/76783)) * Adminadmin (and super admin) UIUI User interface: Increase page headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. vertical padding. ([77152](https://github.com/WordPress/gutenberg/pull/77152)) * Admin UI: Update Page background color to surface-neutral. ([76869](https://github.com/WordPress/gutenberg/pull/76869)) * Autocomplete: Remove getAutoCompleterUI factory pattern. ([77048](https://github.com/WordPress/gutenberg/pull/77048)) * DataForm: Add min/max date range support for date and datetime fields. ([77201](https://github.com/WordPress/gutenberg/pull/77201)) * DataForm: Show tooltip in edit button in `panel` layout. ([77024](https://github.com/WordPress/gutenberg/pull/77024)) * DataForm: Support disabled controls. ([77090](https://github.com/WordPress/gutenberg/pull/77090)) * FormToggle: Update disabled styles. ([77208](https://github.com/WordPress/gutenberg/pull/77208)) * Media Upload Modal: Persist view configuration. ([77288](https://github.com/WordPress/gutenberg/pull/77288)) * Text: Remove UA margins. ([76970](https://github.com/WordPress/gutenberg/pull/76970)) * UI `Text`: Mark as recommended. ([77044](https://github.com/WordPress/gutenberg/pull/77044)) * UI/Dialog: Add explicit `margin-inline-end` rule to Title. ([77334](https://github.com/WordPress/gutenberg/pull/77334)) * UI: Update `@base-ui/react` from `1.3.0` to `1.4.0`. ([77308](https://github.com/WordPress/gutenberg/pull/77308)) * UI: Use Text component for Badge typography. ([77295](https://github.com/WordPress/gutenberg/pull/77295)) * Use `--wpds-cursor-control` design token for interactive controls. ([76786](https://github.com/WordPress/gutenberg/pull/76786)),( [77259](https://github.com/WordPress/gutenberg/pull/77259)) * `@wordpress/ui`: Add `Popover`. ([76438](https://github.com/WordPress/gutenberg/pull/76438)) * ui/AlertDialog: Better async confirm APIs, fully use base ui’s `AlertDialog`.( [76937](https://github.com/WordPress/gutenberg/pull/76937)) * ui/`Dialog`: Update Header layout, refactor Title to use Text. ([77161](https://github.com/WordPress/gutenberg/pull/77161)) * ui: Expose `container` portal prop on all overlay Popup components. ([77163](https://github.com/WordPress/gutenberg/pull/77163)) #### Block Library * Add context for next/previous enlarge image. ([76967](https://github.com/WordPress/gutenberg/pull/76967)) * Image block: Validate attachment ID exists before treating image as local. ([77178](https://github.com/WordPress/gutenberg/pull/77178)) * Search Block: Ensure color settings apply to input field when button is disabled.( [77219](https://github.com/WordPress/gutenberg/pull/77219)) * Tab Menu Item: Simplify active tab menu item style. ([77195](https://github.com/WordPress/gutenberg/pull/77195)) * Tabs: Remove sequential numbering from new tab labels. ([77321](https://github.com/WordPress/gutenberg/pull/77321)) * Use entity link title for link control preview. ([77155](https://github.com/WordPress/gutenberg/pull/77155)) #### Guidelines * Guidelines CPT: Rename from “content guidelines” to “guidelines” (slug, classes, routes). ([77147](https://github.com/WordPress/gutenberg/pull/77147)), ([77223](https://github.com/WordPress/gutenberg/pull/77223)) * Guidelines: Make the CPT type-aware. ([77491](https://github.com/WordPress/gutenberg/pull/77491)) * Improve guideline revision UXUX User experience. ([76560](https://github.com/WordPress/gutenberg/pull/76560)) * Registers wp_guideline_type taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. [https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies)..( [77156](https://github.com/WordPress/gutenberg/pull/77156)) * Update actions-section and import/export workflow. ([76621](https://github.com/WordPress/gutenberg/pull/76621)) #### Post Editor * DataViews: Simplify `defaultLayouts` prop. ([77232](https://github.com/WordPress/gutenberg/pull/77232)) * RTC: Add filterable flag for meta box RTC compatibility. ([76939](https://github.com/WordPress/gutenberg/pull/76939)) * RTC: Change SyncConnectionModal to isSyncConnectionErrorHandled 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. and drop IS_GUTENBERG_PLUGIN check. ([76853](https://github.com/WordPress/gutenberg/pull/76853)) #### Block Editor * Display shortcuts for moving blocks via tooltips. ([76992](https://github.com/WordPress/gutenberg/pull/76992)) * Re-order spacing side controls when unlinked. ([66317](https://github.com/WordPress/gutenberg/pull/66317)) #### Connectors * Update the AI plugin settings page slug we link to after activation. ([77336](https://github.com/WordPress/gutenberg/pull/77336)) #### DataViews * Classify admin-ui and dataviews to components. ([76959](https://github.com/WordPress/gutenberg/pull/76959)) #### Global Styles * Renamed focus visible label. ([77292](https://github.com/WordPress/gutenberg/pull/77292)) #### REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) 󠀁[https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)󠁿 * Add `date` field in templates and template parts. ([77134](https://github.com/WordPress/gutenberg/pull/77134)) #### Media * Media Modal Experiment: Set matching picker grid layout properties for when a user switches layouts. ([77118](https://github.com/WordPress/gutenberg/pull/77118)) #### Collaboration * 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.: Improve validation and permission checks for `WP_HTTP_Polling_Sync_Server`. ([76987](https://github.com/WordPress/gutenberg/pull/76987)) * RTC: Add optional `shouldSync` function to entity sync configuration. ([76947](https://github.com/WordPress/gutenberg/pull/76947)) * RTC: Respect WP_ALLOW_COLLABORATION in Gutenberg for activation hook. ([77084](https://github.com/WordPress/gutenberg/pull/77084)) #### Site Editor * Add Site Tagline and Site Title to Design > Identity panel. ([76264](https://github.com/WordPress/gutenberg/pull/76264)) ### Bug Fixes #### Components * Calendar: Fix disabled styles. ([77138](https://github.com/WordPress/gutenberg/pull/77138)) * Card: Set default foreground color on root. ([77013](https://github.com/WordPress/gutenberg/pull/77013)) * Checkbox: Fix disabled styles. ([77132](https://github.com/WordPress/gutenberg/pull/77132)) * DataForm: Remove `text-transform` from `panel` field labels. ([77196](https://github.com/WordPress/gutenberg/pull/77196)) * DataViews: Fix `compact` density clipping and remove top/bottom padding. ([77054](https://github.com/WordPress/gutenberg/pull/77054)) * Fix autocomplete overlapping trigger matching. ([77018](https://github.com/WordPress/gutenberg/pull/77018)) * FormTokenField: Fix disabled styles. ([77137](https://github.com/WordPress/gutenberg/pull/77137)) * RTC: Fix inline inserter reset on update sync. ([76980](https://github.com/WordPress/gutenberg/pull/76980)) * RadioControl: Add support for disabling radio group. ([77127](https://github.com/WordPress/gutenberg/pull/77127)) * Remove sandbox `allow-same-origin` for core/htmlHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. blocks. ([77212](https://github.com/WordPress/gutenberg/pull/77212)) * TextArea: Add disabled styles. ([77129](https://github.com/WordPress/gutenberg/pull/77129)) * UI: Normalize render prop and ref forwarding patterns. ([77160](https://github.com/WordPress/gutenberg/pull/77160)) #### Block Library * Cover block: Fix embed video background Error 153 in editor. ([76904](https://github.com/WordPress/gutenberg/pull/76904)) * Fix overflow of highlighted white-space in Code Block. ([77085](https://github.com/WordPress/gutenberg/pull/77085)) * Image block: Hide drag handles while an upload is in progress. ([77121](https://github.com/WordPress/gutenberg/pull/77121)) * Paragraph: Prevent `onEnter` splitting of parent block when insertion of that block type is not allowed. ([77291](https://github.com/WordPress/gutenberg/pull/77291)) * Post Author Biography: Preserve occurrence of white spaces. ([71133](https://github.com/WordPress/gutenberg/pull/71133)) * RTC: Core/cover block minor compatibility fixes. ([76916](https://github.com/WordPress/gutenberg/pull/76916)) * Search block: Match behavior of global styling for border and color with local styling (inspector controls) to remove inconsistency. ([77060](https://github.com/WordPress/gutenberg/pull/77060)) * Search block: Derive ‘isSearchFieldHidden’ value. ([77082](https://github.com/WordPress/gutenberg/pull/77082)) * Separator Block: Apply default block variation when inserting via `---` shortcut.( [77135](https://github.com/WordPress/gutenberg/pull/77135)) * Upload external media: Ensure notice only fires once. ([77218](https://github.com/WordPress/gutenberg/pull/77218)) #### Block Editor * Fix SyntaxError in Autocompleter UI when pasting matching content. ([76961](https://github.com/WordPress/gutenberg/pull/76961)) * LinkPicker: Decode HTML entities in link preview title. ([77170](https://github.com/WordPress/gutenberg/pull/77170)) * Prevent Enter key from inserting paragraphs in contentOnly sections. ([76989](https://github.com/WordPress/gutenberg/pull/76989)) * RTC: Fix “Edit as HTML” content reset during collaboration. ([77043](https://github.com/WordPress/gutenberg/pull/77043)) * Writing Flow: Fix format toolbar not appearing when selecting text from block edge. ([77136](https://github.com/WordPress/gutenberg/pull/77136)) * contentOnly template lock: Fix block insertion and removal rules. ([77119](https://github.com/WordPress/gutenberg/pull/77119)) * Fix numeric value clearing in preset input controls. ([77139](https://github.com/WordPress/gutenberg/pull/77139)) #### Guidelines * Guidelines CPT: Skip registration when post type already exists. ([77486](https://github.com/WordPress/gutenberg/pull/77486)) #### Data Layer * Core Data: Fix ‘useEntityProp’ for raw attributes. ([77120](https://github.com/WordPress/gutenberg/pull/77120)) * Core Data: Fix incorrect pagination for non-paginated entities. ([76406](https://github.com/WordPress/gutenberg/pull/76406)) * RTC: Fix core/table cell merging. ([76913](https://github.com/WordPress/gutenberg/pull/76913)) * RTC: Fix orphaned meta causing dirty editor state. ([77529](https://github.com/WordPress/gutenberg/pull/77529)) * RTC: Improve array attribute stability when structural changes occur. ([77164](https://github.com/WordPress/gutenberg/pull/77164)) * getMergedItemsIds: Receive full page bigger than perPage. ([77262](https://github.com/WordPress/gutenberg/pull/77262)) #### Connectors * Account for mu-plugins when resolving plugin.file status. ([76994](https://github.com/WordPress/gutenberg/pull/76994)) * Don’t clobber third-party custom render in registerDefaultConnectors. ([77116](https://github.com/WordPress/gutenberg/pull/77116)) * Hide Akismet unless already installed. ([76962](https://github.com/WordPress/gutenberg/pull/76962)) * Replace speak() with notice store for state changes. ([77174](https://github.com/WordPress/gutenberg/pull/77174)) * Update help text from ‘reset’ to ‘manage’. ([76963](https://github.com/WordPress/gutenberg/pull/76963)) #### Post Editor * Fields: Fix `postContentInfoField` when there are edits. ([76901](https://github.com/WordPress/gutenberg/pull/76901)) * Fix: Restore editor canvas padding in classic themes. ([76864](https://github.com/WordPress/gutenberg/pull/76864)) * RTC: Fix button flickering on retry dialog. ([77234](https://github.com/WordPress/gutenberg/pull/77234)) * RTC: Predefined retry schedules for disconnect dialog, make more lenient. ([76966](https://github.com/WordPress/gutenberg/pull/76966)) * Revision: Fix ‘Show changes’ button reset state. ([77122](https://github.com/WordPress/gutenberg/pull/77122)) #### Collaboration * Fix failing ‘WP_HTTP_Polling_Sync_Server’ unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see [regression](https://make.wordpress.org/core/page/3/?output_format=md#regression)..( [77025](https://github.com/WordPress/gutenberg/pull/77025)) * RTC: Fix disconnect dialog due to uneditable entity. ([77242](https://github.com/WordPress/gutenberg/pull/77242)) * RTC: Isolate sync update failures to prevent full disconnect. ([76968](https://github.com/WordPress/gutenberg/pull/76968)) #### Global Styles * Fix duotone filter not applying on style variation switch. ([77229](https://github.com/WordPress/gutenberg/pull/77229)) * Global Styles Revisions: Fix footer overflow. ([77103](https://github.com/WordPress/gutenberg/pull/77103)) #### DataViews * Fix Gutenberg_REST_View_Config_Controller_7_1 PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher warnings. ([77290](https://github.com/WordPress/gutenberg/pull/77290)) #### Patterns * Fix custom categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. in site editor not displaying pattern actions. ([77251](https://github.com/WordPress/gutenberg/pull/77251)) #### Media * MediaEdit: Handle ‘*’ wildcard in validateMimeType. ([77168](https://github.com/WordPress/gutenberg/pull/77168)) #### Client Side Media * Use image.copyMemory() for batch thumbnail generation. ([76979](https://github.com/WordPress/gutenberg/pull/76979)) ### 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) #### Components * `ValidatedRangeControl`: Fix aria-label rendered as [object Object]. ([77042](https://github.com/WordPress/gutenberg/pull/77042)) ### Performance #### Post Editor * Autocompleters: Move and improve links search. ([76995](https://github.com/WordPress/gutenberg/pull/76995)) #### Client Side Media * Add performance metrics for client-side media processing. ([76792](https://github.com/WordPress/gutenberg/pull/76792)) ### Experiments #### Post Editor * Add revisions panel to templates, template parts and patterns. ([77008](https://github.com/WordPress/gutenberg/pull/77008)) ### Documentation * Add missing documentation in `collaboration.php`. ([77173](https://github.com/WordPress/gutenberg/pull/77173)) * Autocomplete: Clarify ‘isDebounced’ setting limitation. ([77062](https://github.com/WordPress/gutenberg/pull/77062)) * Docs: Add README for DatePicker and TimePicker Components. ([70365](https://github.com/WordPress/gutenberg/pull/70365)) * Editor: Fix ‘selectedNote’ action JSDoc. ([77080](https://github.com/WordPress/gutenberg/pull/77080)) * Eslint: Suggest alternative in `no-setting-ds-tokens` rule. ([77154](https://github.com/WordPress/gutenberg/pull/77154)) * Fix: A sentence has no ending punctuation in README.md file. ([77027](https://github.com/WordPress/gutenberg/pull/77027)) * HStack, VStack: Mark as not recommended for use. ([77041](https://github.com/WordPress/gutenberg/pull/77041)) * Improve CSS setup instructions in package readmes. ([76975](https://github.com/WordPress/gutenberg/pull/76975)) * Storybook: Enable theming toolbar for wp-components. ([77038](https://github.com/WordPress/gutenberg/pull/77038)) * Storybook: Fix “Default” cursor option in theming toolbar. ([77037](https://github.com/WordPress/gutenberg/pull/77037)) * UI/Tooltip: Add usage guidelines documentation. ([77158](https://github.com/WordPress/gutenberg/pull/77158)) * UI: Use Link component in details story example. ([76997](https://github.com/WordPress/gutenberg/pull/76997)) * iAPI Docs: Fix typos, code errors, and inaccuracies in the documentation. ([76636](https://github.com/WordPress/gutenberg/pull/76636)) * ui/docs: Add additional global css setup instructions. ([77228](https://github.com/WordPress/gutenberg/pull/77228)) ### Code Quality * TypeScript: Migrate a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access”( i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia. org/wiki/Accessibility) package to TS. ([70680](https://github.com/WordPress/gutenberg/pull/70680)) #### Components * Add `.scss` files to CSS module linting. ([77140](https://github.com/WordPress/gutenberg/pull/77140)) * Block Directory: Use `--wpds-cursor-control` design token. ([77330](https://github.com/WordPress/gutenberg/pull/77330)) * Autocomplete: Refactor useAutocomplete to use useReducer. ([77020](https://github.com/WordPress/gutenberg/pull/77020)) * BoxControl: Remove unused state for icon side. ([77143](https://github.com/WordPress/gutenberg/pull/77143)) * Build Tools: Update TypeScript to 6.0.2. ([77010](https://github.com/WordPress/gutenberg/pull/77010)) * Button: Remove obsolete Safari + VoiceOver workaround. ([77107](https://github.com/WordPress/gutenberg/pull/77107)) * Button: Remove unused Storybook stylesheet. ([77031](https://github.com/WordPress/gutenberg/pull/77031)) * Dataviews: Remove unneeded ref callbacks. ([77179](https://github.com/WordPress/gutenberg/pull/77179)) * Extract the autocomplete matcher into a separate function. ([76957](https://github.com/WordPress/gutenberg/pull/76957)) * FormTokenField: Remove unnecessary styles. ([77263](https://github.com/WordPress/gutenberg/pull/77263)) * Textarea: Remove unnecessary styles. ([77221](https://github.com/WordPress/gutenberg/pull/77221)) * Theme: Rename typography tokens to use “typography” prefix. ([76912](https://github.com/WordPress/gutenberg/pull/76912)) * Update 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/) function names for better ESLint detection. ([77148](https://github.com/WordPress/gutenberg/pull/77148)) * 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/page/3/?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.: Make sprintf return FormattedText for type-safe createInterpolateElement. ([76974](https://github.com/WordPress/gutenberg/pull/76974)) * ui/Card: Remove redundant margin reset from Card.Title. ([77187](https://github.com/WordPress/gutenberg/pull/77187)) * ui/VisuallyHidden: Standardize composition pattern. ([77190](https://github.com/WordPress/gutenberg/pull/77190)) #### Block Editor * Block Editor store: Refactor controlledInnerBlocks to Set. ([77094](https://github.com/WordPress/gutenberg/pull/77094)) * Global Styles: Move pseudo-state slicing logic into `useStyle` hook. ([77104](https://github.com/WordPress/gutenberg/pull/77104)) * BlockMover: Remove unused disabled button props. ([76993](https://github.com/WordPress/gutenberg/pull/76993)) * Extract getElementCSSRules from useBlockProps. ([77327](https://github.com/WordPress/gutenberg/pull/77327)) * updateBlockListSettings: Convert state to Map, do all updates in one action. ( [46392](https://github.com/WordPress/gutenberg/pull/46392)) #### Post Editor * BlockStyleVariationOverridesWithConfig: Change name and fix lint errors. ([77130](https://github.com/WordPress/gutenberg/pull/77130)) * ESLint plugin: Disable `jsx-a11y/heading-has-content`. ([77073](https://github.com/WordPress/gutenberg/pull/77073)) * Edit Post: Fix warning in ‘useMetaBoxInitialization’ hook. ([77311](https://github.com/WordPress/gutenberg/pull/77311)) * RTC: Store metaboxes RTC-compatible flag on location entries. ([77361](https://github.com/WordPress/gutenberg/pull/77361)) * Revisions: Simplify fetching. ([77086](https://github.com/WordPress/gutenberg/pull/77086)) #### Block Library * Tabs: Simplify anchor handling. ([77189](https://github.com/WordPress/gutenberg/pull/77189)) * TypeScript: Migrate `packages/list-reusable-blocks` package to TypeScript. ([70518](https://github.com/WordPress/gutenberg/pull/70518)) * TypeScript: Migrate viewport package. ([71118](https://github.com/WordPress/gutenberg/pull/71118)) #### Data Layer * Remove remaining esModuleInterop usage. ([77095](https://github.com/WordPress/gutenberg/pull/77095)) * Blocks: Convert blocks package to TypeScript. ([76312](https://github.com/WordPress/gutenberg/pull/76312)) #### Guidelines * Remove jsxRuntime pragma. ([77255](https://github.com/WordPress/gutenberg/pull/77255)) #### Icons * Override WP_Icons_Registry singleton with Gutenberg icons registry. ([76455](https://github.com/WordPress/gutenberg/pull/76455)) #### Annotations * TypeScript: Migrate annotations package to TS. ([70602](https://github.com/WordPress/gutenberg/pull/70602)) ### Tools #### Testing * Autocomplete: Fix flaky end-to-end tests. ([77322](https://github.com/WordPress/gutenberg/pull/77322)) * E2E Tests: Ensure artifacts generate correctly and remove unnecessary artifacts.( [77093](https://github.com/WordPress/gutenberg/pull/77093)) * Fix `page.waitForFunction` call arguments in e2e tests. ([77300](https://github.com/WordPress/gutenberg/pull/77300)) * Guidelines: Add end-to-end tests based on the Settings page testing instructions.( [77192](https://github.com/WordPress/gutenberg/pull/77192)) * Remove ‘Home’ and ‘End’ key usage from Navigation tests. ([77102](https://github.com/WordPress/gutenberg/pull/77102)) * Restore original template registration tests alongside activation variants. ( [77068](https://github.com/WordPress/gutenberg/pull/77068)) * Tests: Auto-fix some new ‘eslint-plugin-playwright’ warnings. ([77314](https://github.com/WordPress/gutenberg/pull/77314)) * Tests: Fix workspace test scripts (wp-env not found, argument forwarding). ([77055](https://github.com/WordPress/gutenberg/pull/77055)),( [77083](https://github.com/WordPress/gutenberg/pull/77083)) #### Build Tooling * Add iteration issue template. ([77113](https://github.com/WordPress/gutenberg/pull/77113)) * Build: Fix glob ignore patterns in dot-prefixed directories. ([75114](https://github.com/WordPress/gutenberg/pull/75114)) * Convert directories in test/ to workspaces. ([74684](https://github.com/WordPress/gutenberg/pull/74684)) * Env: Fix loopback requests when running on non-default ports. ([77057](https://github.com/WordPress/gutenberg/pull/77057)) * Fix lint-staged 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. documentation path. ([77203](https://github.com/WordPress/gutenberg/pull/77203)) * Resolve package-lock.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. inconsistency for [@babel](https://profiles.wordpress.org/babel/)/ eslint-parser. ([77256](https://github.com/WordPress/gutenberg/pull/77256)) * Storybook: Fix end-to-end subpath exports and add CI build smoke test. ([77034](https://github.com/WordPress/gutenberg/pull/77034)) * Refactor: Migrate bin/api-docs to tools/api-docs as workspace `@wordpress/api- docs-generator`. ([77019](https://github.com/WordPress/gutenberg/pull/77019)) * Upgrade ESLint to v10. ([76654](https://github.com/WordPress/gutenberg/pull/76654)) #### Data Layer * Fix pre-existing lint errors across the codebase. ([77002](https://github.com/WordPress/gutenberg/pull/77002)) * Remove unused catch block variables across the codebase. ([76969](https://github.com/WordPress/gutenberg/pull/76969)) ## First-time contributors The following PRs were merged by first-time contributors: * @DarkMatter-999: Fix numeric value clearing in preset input controls. ([77139](https://github.com/WordPress/gutenberg/pull/77139)) * [@dkotter](https://profiles.wordpress.org/dkotter/): Update the AI plugin settings page slug we link to after activation. ([77336](https://github.com/WordPress/gutenberg/pull/77336)) * @dpmehta: Search block: Match behavior of global styling for border and color with local styling (inspector controls) to remove inconsistency. ([77060](https://github.com/WordPress/gutenberg/pull/77060)) * [@mehrazmorshed](https://profiles.wordpress.org/mehrazmorshed/): Fix: A sentence has no ending punctuation in README.md file. ([77027](https://github.com/WordPress/gutenberg/pull/77027)) * [@prachigarg19](https://profiles.wordpress.org/prachigarg19/): Fix duotone filter not applying on style variation switch. ([77229](https://github.com/WordPress/gutenberg/pull/77229)) * [@samvaidya](https://profiles.wordpress.org/samvaidya/): Image block: Validate attachment ID exists before treating image as local. ([77178](https://github.com/WordPress/gutenberg/pull/77178)) * @sandipr942: Added missing documentation in `collaboration.php`. ([77173](https://github.com/WordPress/gutenberg/pull/77173)) * [@superdav42](https://profiles.wordpress.org/superdav42/): Connectors: Don’t clobber third-party custom render in registerDefaultConnectors. ([77116](https://github.com/WordPress/gutenberg/pull/77116)) ## Contributors The following contributors merged PRs in this release: [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) @Adi-ty [@aduth](https://profiles.wordpress.org/aduth/) [@alecgeatches](https://profiles.wordpress.org/alecgeatches/) [@andrewserong](https://profiles.wordpress.org/andrewserong/) [@annezazu](https://profiles.wordpress.org/annezazu/) [@aswasif007](https://profiles.wordpress.org/aswasif007/) @BugReportOnWeb [@CGastrell](https://profiles.wordpress.org/cgastrell/) @chriszarate @ciampo @coderGtm [@DAreRodz](https://profiles.wordpress.org/darerodz/) @DarkMatter- 999 [@dinhtungdu](https://profiles.wordpress.org/dinhtungdu/) [@dkotter](https://profiles.wordpress.org/dkotter/) @dpmehta [@ellatrix](https://profiles.wordpress.org/ellatrix/) [@gziolo](https://profiles.wordpress.org/gziolo/) [@hbhalodia](https://profiles.wordpress.org/hbhalodia/) [@iamchughmayank](https://profiles.wordpress.org/iamchughmayank/) @Infinite-Null [@ingeniumed](https://profiles.wordpress.org/ingeniumed/) [@jameskoster](https://profiles.wordpress.org/jameskoster/) [@jeryj](https://profiles.wordpress.org/jeryj/) [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) [@jsnajdr](https://profiles.wordpress.org/jsnajdr/) @kushagra-goyal-14 @madhusudhand @MaggieCabrera [@Mamaduka](https://profiles.wordpress.org/mamaduka/) [@manzoorwanijk](https://profiles.wordpress.org/manzoorwanijk/) [@mehrazmorshed](https://profiles.wordpress.org/mehrazmorshed/) [@mirka](https://profiles.wordpress.org/mirka/) [@nerrad](https://profiles.wordpress.org/nerrad/) [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) [@oandregal](https://profiles.wordpress.org/oandregal/) [@prachigarg19](https://profiles.wordpress.org/prachigarg19/) @R1shabh-Gupta @ramonjd [@samvaidya](https://profiles.wordpress.org/samvaidya/) @sandipr942 [@scruffian](https://profiles.wordpress.org/scruffian/) @shail-mehta @Shekhar0109 @shrivastavanolo [@superdav42](https://profiles.wordpress.org/superdav42/) @Swanand01 @t-hamano [@talldan](https://profiles.wordpress.org/talldan/) [@tyxla](https://profiles.wordpress.org/tyxla/) @USERSATOSHI [@yashjawale](https://profiles.wordpress.org/yashjawale/) [@yogeshbhutkar](https://profiles.wordpress.org/yogeshbhutkar/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F04%2F22%2Fwhats-new-in-gutenberg-23-0-22-april%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/bph/) [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 7:25 am _on_ April 22, 2026 Tags: [7.0 ( 68 )](https://make.wordpress.org/core/tag/7-0/), [dev-notes ( 618 )](https://make.wordpress.org/core/tag/dev-notes/), [dev-notes-7-0 ( 21 )](https://make.wordpress.org/core/tag/dev-notes-7-0/), [editor ( 222 )](https://make.wordpress.org/core/tag/editor/)    # 󠀁[Roster of design tools per block (WordPress 7.0 edition)](https://make.wordpress.org/core/2026/04/22/roster-of-design-tools-per-block-wordpress-7-0/)󠁿 Below you find a table that lists all coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks available in the inserter marks in the grid the feature they support in 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. It’s a basic lookup table that helps developers to find the information quickly. While this post is released as part of 6.8, the content summarizes changes between 6.1 and 7.0. This is an[ updated of the 6.8 edition](https://make.wordpress.org/core/2025/03/12/roster-of-design-tools-per-block-wordpress-6-8-edition/) and provides a cumulative list of design supports added with the last ten WordPress releases. The icon ☑️ indicates new in 6.9 or 7.0. The features covered are: * Align * Typography * Color * Dimension * Border * Layout * Gradient * Duotone * Shadow * Background image ## Changes to Blocks * The Verse block was renamed to **Poetry** block in WordPress 7.0 * **New Blocks added** - Accordion with Accordion Heading, Accordion Item, Accordion Panel - Breadcrumbs - Icon - Math - Post Time to Read - Term Query with Term Template, Term Count, Term Name ## Table changes In previous editions of this roster, the **PO/BB column** tracked a small, hardcoded set of core blocks where Pattern Overrides and Block Bindings were manually enabled— Button, Image, Paragraph, and Heading. That model no longer reflects how the feature works. WordPress 6.9 moved Block Bindings to a server-communicated list of supported attributes via the `block_bindings_supported_attributes` 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., and WordPress 7.0 extended that same mechanism to Pattern Overrides, so any block attribute that opts into Block Bindings now also supports Pattern Overrides— including custom blocks. Because support is opt-in per block, per attribute, and per site, a single check mark in a lookup table can no longer represent it accurately. The column has been removed in favor of a note pointing readers to the [Pattern Overrides in WP 7.0](https://make.wordpress.org/core/2026/03/16/pattern-overrides-in-wp-7-0-support-for-custom-blocks/) and [Block Bindings improvements in 6.9](https://make.wordpress.org/core/2025/11/12/block-bindings-improvements-in-wordpress-6-9/) dev notesdev 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.. | **Block** | **Align** | **Typography** | **Color** | **Dimension** | **Border** | **Layout** | **Gradient** | **Duotone** | **Shadow** | **Backgr.Img** | | **Accordion** | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | | ☑️ new | ☑️ new | | **Accordion Heading** | | ☑️ new | ☑️ new | ☑️ new | ☑️ new | | ☑️ new | | ☑️ new | | | **Accordion Item** | | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | | ☑️ new | | | **Accordion Panel** | | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | | ☑️ new | | | Archives | ✅ | ✅ | ✅ | ✅ | ✅ | – | | – | – | | | Audio | ✅ | – | – | ✅ | – | – | | – | | | | 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. | ✅ | – | | ✅ | ✅ | – | | ✅ | | | | **Breadcrumbs** | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | | ☑️ new | | | | | Button | | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | ✅ | | | Buttons | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | – | ✅ | | | Calendar | ✅ | ✅ | ✅ | – | – | – | | – | | | | Categories | ✅ | ✅ | ✅ | ✅ | ✅ | – | | – | | | | Code | ✅ | ✅ | ✅ | ✅ | ✅ | – | | – | | | | Column | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | – | ✅ | | | Columns | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | – | ✅ | | | Comment Author Avatar | | – | ✅ | ✅ | ✅ | – | | – | | | | Comment Author Name | | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | Comment Content | | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | Comment Date | | ✅ | ✅ | ✅ | ✅ | – | | – | | | | Comment Edit Link | | ✅ | ✅ | ✅ | ✅ | – | | – | | | | Comment Reply Link | | ✅ | ✅ | ✅ | ✅ | – | | – | | | | Comment Template | ✅ | ✅ | – | ✅ | ☑️ new | – | | – | | | | Comments | ✅ | ✅ | ✅ | ✅ | ☑️ new | | ✅ | – | | | | Comments Pagination | ✅ | ✅ | ✅ | – | – | ✅ | | – | | | | Comments Pagination Next | | ✅ | ✅ | – | – | – | ✅ | – | | | | Comments Pagination Numbers | | ✅ | ✅ | ☑️ new | – | – | ✅ | – | | | | Comments Pagination Previous | | ✅ | ✅ | – | – | – | ✅ | – | | | | Comments Title | ✅ | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | Cover | ✅ | ✅ | ✅ | ✅ | ✅ | ☑️ new | ✅ | ✅ | ☑️ new | | | Details | ✅ | ✅ | ✅ | ✅ | ✅ | ☑️ new | ✅ | | | | | Embed | ✅ | | – | ✅ | – | – | | – | | | | File | ✅ | – | ✅ | ✅ | ✅ | – | ✅ | – | | | | Footnotes | | ✅ | ✅ | ✅ | ✅ | | | | | | | Gallery | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | – | | | | Group | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | – | ✅ | ✅ | | Heading | ✅ | ✅ | ✅ | ✅ | ✅ | – | | – | | | | Home Link – Navigation | | ✅ | – | – | – | – | | – | | | | HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. | | – | – | – | – | – | | – | | | | **Icon** | ☑️ new | | ☑️ new | ☑️ new | ☑️ new | | | | | | | **Image** | ✅ | | – | ✅ | ✅ | – | | ✅ | ✅ | | | Latest Comments | ✅ | ✅ | ✅ | ✅ | ✅ | – | | – | | | | Latest Posts | ✅ | ✅ | ✅ | – | ✅ | – | ✅ | | | | | List | – | ✅ | ✅ | ✅ | ✅ | – | | – | | | | List Item | – | ✅ | ☑️ new | ✅ | ✅ | – | | – | | | | Login/logout | – | – | – | – | – | – | | – | | | | **Math** | – | ☑️ new | ☑️ new | ☑️ new | ☑️ new | – | ☑️ new | – | – | – | | Media & Text | ✅ | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | More (Read More) | – | – | – | – | – | – | | – | | | | Navigation | ☑️ new | ✅ | – | ✅ | – | ✅ | | – | | | | Navigation Link | – | ✅ | – | – | – | – | | – | | | | Navigation Submenu | – | ☑️ new | – | – | – | – | | – | | | | Next Page (Page Break) | – | – | – | – | – | – | | – | | | | Page List | – | ✅ | ✅ | ✅ | ✅ | – | | – | | | | **Paragraph** | ☑️ new | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | **Poetry (formerly Verse)** | | ✅ | ✅ | ✅ | ✅ | | ✅ | | | ✅ | | Post Author | | ✅ | ✅ | ✅ | ✅ | – | ✅ | ☑️ new | | | | Post Author Biography | | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | Post Author Name | | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | Post Comments Count | | ✅ | ✅ | ✅ | ☑️ new | – | ✅ | – | | | | Post Comments Form | | ✅ | ✅ | ✅ | ✅ | – | | ✅ | | | | Post Comments Link | | ✅ | ✅ | ✅ | ☑️ new | – | | ✅ | | | | Post Content | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | | ✅ | | Post Date | | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | Post ExcerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. | | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | Post Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. | ✅ | – | | ✅ | ✅ | – | | ✅ | ✅ | | | Post Navigation Link | | ✅ | ✅ | – | – | – | | – | | | | Post Template | ✅ | ✅ | ✅ | ✅ | – | ✅ | ✅ | | | | | Post Terms | | ✅ | ✅ | ✅ | ✅ | – | | – | | | | Post Title | ✅ | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | Preformatted | | ✅ | ✅ no link | ✅ | ✅ | – | ✅ | – | | | | Pullquote | ✅ | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | ✅ | | Query | ✅ | – | | – | – | ✅ | | – | | | | Query No Results | ✅ | ✅ | ✅ | – | – | – | ✅ | – | | | | Query Pagination | | ✅ | ✅ | – | – | ✅ | | – | | | | Query Pagination Next | | ✅ | ✅ | – | – | – | ✅ | – | | | | Query Pagination Numbers | | ✅ | ✅ | – | – | – | ✅ | – | | | | Query Pagination Previous | | ✅ | ✅ | – | – | – | ✅ | – | | | | Query Title | ✅ | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | **Query Total** | ✅ | ✅ | ✅ | ✅ | ✅ | | | | | | | Quote | | ✅ | ✅ | ✅ | – | – | | – | | ✅ | | Read More | | ✅ | ✅ | ✅ | ✅ | – | | – | | | | RSS | | – | – | ✅ | ✅ | – | | – | | | | Search | | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | Separator | ✅ | – | ✅ | ✅ | – | – | ✅ | – | | | | Site Logo | ✅ | – | ✅ | ✅ | – | – | | – | | ✅ | | Site Tagline | ✅ | ✅ | ✅ | ✅ | ✅ | – | | – | | | | Site Title | ✅ | ✅ | ✅ | ✅ | ✅ | – | | – | | | | Social Link | | – | – | – | – | – | | – | | | | Social Links | ✅ | – | ✅ | ✅ | ✅ | ✅ | ✅ | – | | | | Spacer | | – | – | ✅ | – | – | | – | | | | Table | ✅ | ✅ | ✅ | ✅ | ✅ | – | ✅ | – | | | | Tag Cloud | ✅ | ✅ | – | ✅ | ✅ | – | | – | | | | Template Part | ✅ | | | | | | | | | | | **Term Count** | | ☑️ new | ☑️ new | ☑️ new | ☑️ new | – | ☑️ new | | | | | **Term Description** | ✅ | ✅ | ✅ | ✅ | ✅ | – | – | – | | | | **Term Name** | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | – | ☑️ new | – | – | – | | **Terms Query** | ☑️ new | – | – | – | – | ☑️ new | – | – | – | – | | **Term Template** | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | ☑️ new | – | – | – | | **Time To Read** | – | ☑️ new | ☑️ new | ☑️ new | ☑️ new | – | ☑️ new | – | – | – | | Video | – | – | – | ✅ | – | – | – | – | – | – | _Props to [@awetz583](https://profiles.wordpress.org/awetz583/), [@westonruter](https://profiles.wordpress.org/westonruter/), and [@blackstar1991](https://profiles.wordpress.org/blackstar1991/) for review. _ [#7-0](https://make.wordpress.org/core/tag/7-0/), [#dev-notes](https://make.wordpress.org/core/tag/dev-notes/), [#dev-notes-7-0](https://make.wordpress.org/core/tag/dev-notes-7-0/), [#editor](https://make.wordpress.org/core/tag/editor/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F04%2F22%2Froster-of-design-tools-per-block-wordpress-7-0%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/amykamala/) [Amy Kamala](https://profiles.wordpress.org/amykamala/) 6:27 am _on_ April 22, 2026 Tags: [7.0 ( 68 )](https://make.wordpress.org/core/tag/7-0/), [release ( 32 )](https://make.wordpress.org/core/tag/release/)    # 󠀁[WordPress 7.0 Release Party Updated Schedule](https://make.wordpress.org/core/2026/04/22/wordpress-7-0-release-party-updated-schedule/)󠁿 Good news, everyone! WordPress 7.0 has a new release date: **May 20th, 2026**! Thank you all for your flexibility in these recent weeks while WordPress contributors around the world worked tirelessly on necessary architectural improvements for the 7.0 release. The team aims to ensure that this software version is the most stable and most performant it can be, while still delivering the much anticipated cornerstone features mapped out for WordPress 7.0. Below is the new release schedule, with expected dates and times for each release party, and the release squad contributors involved in each party for the [7.0 milestone](https://make.wordpress.org/core/7-0/). It also includes the pre-release versions that have already been released, and a( pending) call for testing from web hosts meant to help ensure compatibility across hosting systems. **Note: **While the most recent pre-release version was RC2, the RC3 release will be treated like 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 in practice. That means that your continued testing and feedback, particularly on the part of web hosts, will be incredibly valuable in keeping the development process informed during the next phase of this release cycle. Thank you all for your continued testing! ## Release Schedule As always, last-minute adjustments to this schedule are possible, and there could be additional timeline iterations based on the impact of host feedback to ensure that feedback is properly addressed. The release squad will do its best to communicate any changes promptly by posting in the [#core Slack channel](https://wordpress.slack.com/archives/C02RQBWTW), publishing a post on the change, and updating this post as the canonical reference. | **Date (UTC)** | **Milestone** | **Emcee / Release LeadRelease Lead The community member ultimately responsible for the Release.** | **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.** | **Security** | **Mission Control (Coordination)** | | [February 19, 2026 at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260219T1500) | Beta 1 | [@amykamala](https://profiles.wordpress.org/amykamala/) | [@ellatrix](https://profiles.wordpress.org/ellatrix/) | [@audrasjb](https://profiles.wordpress.org/audrasjb/) | [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) | | [February 26, 2026 at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260226T1500) | Beta 2 | [@amykamala](https://profiles.wordpress.org/amykamala/) | [@ellatrix](https://profiles.wordpress.org/ellatrix/) | [@audrasjb](https://profiles.wordpress.org/audrasjb/) | [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) | | [March 5, 2026 at 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260305T1400) | Beta 3 | [@amykamala](https://profiles.wordpress.org/amykamala/) | [@audrasjb](https://profiles.wordpress.org/audrasjb/) Committing from 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/). Nice Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of [https://make.wordpress.org/](https://make.wordpress.org/) There are many teams that people can participate in, each with a different focus. [https://2017.us.wordcamp.org/contributor-day/](https://2017.us.wordcamp.org/contributor-day/) [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)! | [@audrasjb](https://profiles.wordpress.org/audrasjb/) | [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) | | [March 10, 2026 at 23:30 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260310T2330)_Unplanned beta following the 6.9.2-6.9.3 security releases_ | Beta 4 | [@desrosj](https://profiles.wordpress.org/desrosj/) | [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) | [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) | [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) | | [March 12, 2026 at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260312T1500) | Beta 5 | [@chaion07](https://profiles.wordpress.org/chaion07/) | [@ellatrix](https://profiles.wordpress.org/ellatrix/) | [@audrasjb](https://profiles.wordpress.org/audrasjb/) | [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) | | [March 24, 2026 at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260324T1500) | RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/page/3/?output_format=md#alpha-beta). 1 | [@amykamala](https://profiles.wordpress.org/amykamala/) | [@ellatrix](https://profiles.wordpress.org/ellatrix/) | [@audrasjb](https://profiles.wordpress.org/audrasjb/) | [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) | | [March 26, 2026 at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260326T1500) | RC 2 | [@4thhubbard](https://profiles.wordpress.org/4thhubbard/) | [@ellatrix](https://profiles.wordpress.org/ellatrix/) | [@audrasjb](https://profiles.wordpress.org/audrasjb/) | [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) | | April 24, 2026 | Call for host testing | [@desrosj](https://profiles.wordpress.org/desrosj/) | n/a | n/a | n/a | | [May 8, 2026 at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260508T1500) | RC 3 (~in name, but test as a “new Beta 1”~) | [@amykamala](https://profiles.wordpress.org/amykamala/) | [@ellatrix](https://profiles.wordpress.org/ellatrix/) | [@audrasjb](https://profiles.wordpress.org/audrasjb/) | [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) | | [May 14, 2026 at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260514T1500) | RC 4 (~in name, but acting as a “new RC1”~) | ~[@4thhubbard](https://profiles.wordpress.org/4thhubbard/)~ [@chaion07](https://profiles.wordpress.org/chaion07/) | [@ellatrix](https://profiles.wordpress.org/ellatrix/) | [@audrasjb](https://profiles.wordpress.org/audrasjb/) | [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) | | [Tuesday, May 19, 2026 at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260519T1500)~ | Dry Run / 24-Hour Code Freeze | TBD | TBD | TBD | TBD | | Wednesday, May 20, 2026**Time TBA** | General Release | TBD | TBD | TBD | TBD | ## **How to Join the Party** * All parties happen in the [ #core channel on Slack](https://wordpress.slack.com/archives/C02RQBWTW). * Everyone is welcome! First-timers, veteran contributors, and all those curious about the process are invited. Here are detailed instructions on [how to contribute to a release party](https://make.wordpress.org/test/2025/03/04/how-to-contribute-to-wp-6-8-release-party/). Thank you to every contributor and community member that helps make 7.0 a success. See you at the parties! _Props to [@desrosj](https://profiles.wordpress.org/desrosj/), [@4thhubbard](https://profiles.wordpress.org/4thhubbard/), [@annezazu](https://profiles.wordpress.org/annezazu/), [@griffbrad](https://profiles.wordpress.org/griffbrad/), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/), and [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) for helping devise the new schedule, and [@desrosj](https://profiles.wordpress.org/desrosj/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/), and [@sumitsingh](https://profiles.wordpress.org/sumitsingh/) for reviewing this post. [#7-0](https://make.wordpress.org/core/tag/7-0/), [#release](https://make.wordpress.org/core/tag/release/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F04%2F22%2Fwordpress-7-0-release-party-updated-schedule%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/b1ink0/) [Aditya Dhade](https://profiles.wordpress.org/b1ink0/) 4:42 pm _on_ April 21, 2026 Tags: [core-performance ( 142 )](https://make.wordpress.org/core/tag/core-performance/), [hosting ( 47 )](https://make.wordpress.org/core/tag/hosting/), [performance ( 408 )](https://make.wordpress.org/core/tag/performance/), [performance-chat ( 335 )](https://make.wordpress.org/core/tag/performance-chat/), [summary ( 969 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Performance Chat Summary: 21 April 2026](https://make.wordpress.org/core/2026/04/21/performance-chat-summary-21-april-2026/)󠁿 The full chat log is available beginning [here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1776787295870969). ## **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)** * [@mukesh27](https://profiles.wordpress.org/mukesh27/) shared that [@westonruter](https://profiles.wordpress.org/westonruter/) discussed the Auto Sizes feature during 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 and opened issue [#2449](https://github.com/WordPress/performance/issues/2449) to outline next steps for further work. [@mukesh27](https://profiles.wordpress.org/mukesh27/) mentioned plans to review the issue and pick it up again when possible, and invited others to contribute in the meantime. - [@mukesh27](https://profiles.wordpress.org/mukesh27/) also noted that resolving the sizes issue for the Gallery 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. would put the feature in a good position to be proposed for WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. - [@ravikhadka](https://profiles.wordpress.org/ravikhadka/) replied expressing interest in working on the feature. **Our next chat will be held on [Tuesday, May 5, 2026 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260505T1600) 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/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F04%2F21%2Fperformance-chat-summary-21-april-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/estelaris/) [Estela Rueda](https://profiles.wordpress.org/estelaris/) 2:45 pm _on_ April 21, 2026 Tags: [make.wordpress.org/docs ( 22 )](https://make.wordpress.org/core/tag/make-wordpress-org-docs/), [p2-xpost ( 207 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: WordPress Documentation Team Closes 200+ Issues — and Needs Your Help](https://make.wordpress.org/core/2026/04/21/xpost-wordpress-documentation-team-closes-200-issues-and-needs-your-help/)󠁿 X-comment from [+make.wordpress.org/docs](https://make.wordpress.org/docs/): Comment on [WordPress Documentation Team Closes 200+ Issues — and Needs Your Help](https://make.wordpress.org/docs/2026/04/21/wordpress-documentation-team-closes-200-issues-and-needs-your-help/#comment-40593) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F04%2F21%2Fxpost-wordpress-documentation-team-closes-200-issues-and-needs-your-help%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 8:21 am _on_ April 21, 2026 Tags: [7.0 ( 68 )](https://make.wordpress.org/core/tag/7-0/), [agenda ( 1,128 )](https://make.wordpress.org/core/tag/agenda/), [core ( 727 )](https://make.wordpress.org/core/tag/core/), [core-privacy ( 53 )](https://make.wordpress.org/core/tag/core-privacy/), [dev chat ( 905 )](https://make.wordpress.org/core/tag/dev-chat/) # 󠀁[Dev Chat Agenda – April 22, 2026](https://make.wordpress.org/core/2026/04/21/dev-chat-agenda-april-22-2026/)󠁿 The next WordPress Developers Chat will take place on [Wednesday, April 22, 2026, at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260422T1500) 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 7.0 Updates * [The Path Forward for WordPress 7.0](https://make.wordpress.org/core/2026/04/02/the-path-forward-for-wordpress-7-0/). A new release schedule should be shared this week. * New Dev Notesdev 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.: - [Roster of design tools per block (WordPress 7.0 edition)](https://make.wordpress.org/core/2026/04/22/roster-of-design-tools-per-block-wordpress-6-8-edition-2/) ### General announcements * [WordPress Core Dev Environment Toolkit: A Faster Path to Your First Core Contribution](https://make.wordpress.org/core/2026/04/16/wordpress-core-dev-environment-toolkit-a-faster-path-to-your-first-core-contribution/) ### Editor * [What’s new in Gutenberg 23.0? (22 April)](https://make.wordpress.org/core/2026/04/22/whats-new-in-gutenberg-23-0-22-april/) ## 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._ * [@masteradhoc](https://profiles.wordpress.org/masteradhoc/) wants to draw attention on ticket [#65025](https://core.trac.wordpress.org/ticket/65025) and especially on [this PR](https://github.com/WordPress/wordpress-develop/pull/11442). Also the [#core-privacy](https://make.wordpress.org/core/tag/core-privacy/) channel is not maintained anymore, and we should probably get some new maintainers. [@masteradhoc](https://profiles.wordpress.org/masteradhoc/) is volunteering to maintain the related component, and to help on [PR11444](https://github.com/WordPress/wordpress-develop/pull/11444) or [PR11443](https://github.com/WordPress/wordpress-develop/pull/11443). ## 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/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F04%2F21%2Fdev-chat-agenda-april-22-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 8:18 am _on_ April 21, 2026 Tags: [7.0 ( 68 )](https://make.wordpress.org/core/tag/7-0/), [core ( 727 )](https://make.wordpress.org/core/tag/core/), [core-editor ( 750 )](https://make.wordpress.org/core/tag/core-editor/), [dev chat ( 905 )](https://make.wordpress.org/core/tag/dev-chat/)    # 󠀁[Dev Chat summary: April 15, 2026](https://make.wordpress.org/core/2026/04/21/summary-dev-chat-april-15-2026/)󠁿 [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1776265215862139) 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 [@amykamala](https://profiles.wordpress.org/amykamala/) 🔗 [Agenda post](https://make.wordpress.org/core/2026/04/15/dev-chat-agenda-april-8-2026-2/). ## Announcements 📢 ### WordPress 7.0 Updates * [The Path Forward for WordPress 7.0](https://make.wordpress.org/core/2026/04/02/the-path-forward-for-wordpress-7-0/). The 7.0 release is still on pause for the time being. A new schedule is being worked out and will be announced by the 22nd. There will be another Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/page/3/?output_format=md#alpha-beta). in name, but in practice the next release will be treated as 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., specifically to test architectural improvements to Real Time Collaboration. Thank you in advance to everyone who helps test! ### General * [Gutenberg 22.9 was released on April 8th](https://make.wordpress.org/core/2026/04/09/whats-new-in-gutenberg-22-9-8-april/) * Please take a look at this [Twenty Twenty-Seven: Team Announcement](https://make.wordpress.org/core/2026/04/08/tt7-team/) highlighting an emphasis on mentorship and creating an entry point for new contributors. ## Discussion 💬 [@annezazu](https://profiles.wordpress.org/annezazu/) has published [Defining expectations for Iteration issues](https://make.wordpress.org/core/2026/04/08/iteration-issue-expectations/) announcing some adjustments to iteration issue handling in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) repo. From [@amykamala](https://profiles.wordpress.org/amykamala/): “Finding the most current PRs and discussions can be a bit of a wild goose chase because while PRs mention tickets in their content, the fields/relationships on the right that would link PRs to a ticketticket Created for both bug reports and feature development on the bug tracker., project, status, etc are not actively being used. For 7.0 theres a kan ban board but nothing in it because tickets and PRs are not being tagged. So the only way to find this info is to scroll endlessly on tickets and click on all the links in the notifications. Some of you may remember a while back I asked devs in here to please start tagging their PRs in the fields on the right.” * [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) noted that the `#core-program` channel may be a good place to iterate on this topic. Matt is requesting community reps and organizers increase emphasis on [Elevating Individuals](https://make.wordpress.org/core/2026/04/11/elevating-individuals/) in the contributor space to to celebrate volunteers and folks who contribute in their own spare time. From [@miroku](https://profiles.wordpress.org/miroku/): “I can only report problems; can that be considered a contribution? I’m always struggling to figure out how to volunteer effectively”. [@jorbin](https://profiles.wordpress.org/jorbin/) answered that testing and finding bugs is absolutely a contribution! [@westonruter](https://profiles.wordpress.org/westonruter/) wanted to draw attention to this issue with `@wordpress/core-abilities` which [makes it difficult to use outside of a React context](https://github.com/WordPress/gutenberg/issues/77253). A [PR is available](https://github.com/WordPress/gutenberg/pull/77254) to fix the issue. [#7-0](https://make.wordpress.org/core/tag/7-0/), [#core](https://make.wordpress.org/core/tag/core/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F04%2F21%2Fsummary-dev-chat-april-15-2026%2F%23respond&locale=en_US) ## Post navigation [← Older posts](https://make.wordpress.org/core/page/4/?output_format=md) [Newer posts →](https://make.wordpress.org/core/page/2/?output_format=md)