The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
The full chat log is available beginning here on Slack.
WordPress Performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
@spacedmonkey asked whether commits to trunktrunkA 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. are currently allowed or if only RTC-related changes should be committed. @westonruter clarified that trunk is still frozen, except for 7.0-specific fixes that get back-ported, and testing commits.
@spacedmonkey said they would hold off committing any performance-related changes for now and asked others to pingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” them if anything needs review or commit.
@westonruter added that @pbearne already has a few PRs for testing changes that could be moved forward for commit now, though not performance-related.
@pbearne mentioned that there are more PRs to come.
@westonruter shared that there is about a 10% regressionregressionA software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in TTFB in WordPress 7.0 compared to 6.9, based on benchmarking noticed by @mukesh27. @westonruter mentioned that TTFB-LCP does not show a regression, so this appears to be additional PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher processing slowing things down, but no single cause has stood out yet.
@westonruter also shared ticketticketCreated for both bug reports and feature development on the bug tracker.#65165, which was recently opened, about script modules depending on classic scripts. @westonruter noted that this is related to performance because it can reduce the amount of scripts loaded on the page thanks to dynamic imports, which are non-blocking, and mentioned that the ticket had just come in and had not yet been reviewed in depth.
@westonruter further pointed out ticket #64696, which focuses on improving the scalability of real-time collaboration via HTTPHTTPHTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. polling and its impact on persistent post caches, noting that things seem to have gone a bit quiet on that ticket.
Performance Lab PluginPluginA 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/ or can be cost-based plugin from a third-party. (and other performance plugins)
@westonruter shared that PR #2461 which updates @wordpress/scripts and related packages while fixing backward compatibility issues, is currently top of mind.
Open Floor
@westonruter shared a LinkedIn post highlighting that appending <link rel="preload"> tags late in the <head> can be too late for optimal performance if an initial chunk of HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. is sent without those tags, which can happen when a lot of CSSCSSCascading Style Sheets. is inlined. @westonruter noted that this is relevant for Optimization Detective, since it currently appends these preload tags to the end of the head.
@westonruter mentioned that HTTP Link headers are also being sent, so in practice this might not be an issue. However, @westonruter pointed out issue #2304, where large Link headers can exceed NginxNGINXNGINX 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/. limits and cause 502 errors.
The Block Editor Handbook is one of the primary resources for developers building with GutenbergGutenbergThe 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/ and WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. Keeping it accurate and up-to-date as the editor evolves is an ongoing challenge.
Recently, a detailed Core Blocks reference section was proposed for the Handbook — providing structured APIAPIAn 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 for every blockBlockBlock 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. shipped in Gutenberg. The approach was to auto-generate these pages directly from each block’s block.json file, the single source of truth for a block’s attributes, supports, and metadata.
The initial pull request (#77350) was merged but subsequently reverted (#77590) due to insufficient community discussion before landing. That feedback was valid, and this post is the next step: bringing the proposal to the wider community before moving forward.
Understanding how a core block works today means reading its source code directly. A block is defined by attributes, supports, context, selectors, and parent/child relationships — but none of these are documented in context for any individual block. To learn about a specific block, a developer has to read its block.jsonJSONJSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. file — which shows the values but does not explain what they mean — and then separately hunt through the general documentation to understand each property. Per-block documentation with contextual links to each concept would close that gap entirely.
The same problem affects LLMs: without documented context for each property, they have to parse source files to infer semantics, spending more tokens and filling context unnecessarily. This is important for AI-assisted creation of templates, template parts, patterns, and other block editor content.
Most of this detail already exists in the codebase. If it can be surfaced automatically, there’s no good reason to leave it buried.
The proposed solution
The proposal introduces an automated pipeline that generates per-block API reference pages by reading each block’s block.json at build time. This means:
Every block shipped in Gutenberg automatically gets a documentation page reflecting its current attributes, supports, selectors, and other metadata.
Keeping docs in sync becomes a byproduct of keeping block.json accurate — which developers already do.
The Block Editor Handbook gains a canonical, always-current API reference for all core blocks.
The generated docs would live at paths like: developer.wordpress.org/block-editor/reference-guides/core-blocks/[block-name]/ and would look like this:
README.md per block in the repository
A key part of the proposal is that documentation is generated into a README.md file inside each block’s source directory — for example, packages/block-library/src/paragraph/README.md.
This follows the same convention already established for component documentation, where gen-components-docs generates a README.md inside each component’s directory at packages/components/src/{component}/README.md.
Having documentation live next to the code has a specific benefit: it allows hand-written narrative and auto-generated API reference to coexist in the same file. Generated content is wrapped in token delimiters (<!-- START TOKEN / END TOKEN -->), so any hand-written prose above the token is preserved across regenerations. The Navigation block README is a working example of this.
This mirrors the approach already used by the package API docs generator (update-api-docs.js) to document each package API inside each package README.md.
What this means for contributors
For block developers
No separate docs PR is needed when you add or change a block.json attribute — the reference page updates automatically.
The README.md lives next to the block’s source, making the API surface discoverable when browsing the codebase.
The expectation for what constitutes “well-documented” becomes clearer and more tractable.
For documentation contributors
A reliable, auto-generated foundation means energy can be focused on narrative guides and tutorials rather than maintaining API reference tables.
Custom hand-written explanations in a block’s README.md are preserved across regenerations, so narrative docs and API reference can grow independently.
Having a public view of block documentation may encourage contributors to get involved by creating issues or PRs if they find errors.
For users of the Handbook
Reference pages stay current with each Gutenberg release rather than drifting behind.
Open questions — we want your input
README.md in the repo vs. the docs site: Should per-block README.md files live in the Gutenberg repository, or be generated solely at the docs site level (as PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher references currently are)?
Process fit: Does auto-generating docs from block.json fit naturally into the existing contribution workflow? Where might it break down?
block.json as source of truth: Are there things about a block that can’t or shouldn’t be derived from block.json? How should those gaps be handled?
Anything we’re missing: What challenges or risks hasn’t this proposal addressed?
Join the conversation live: We’ll be hosting a Hallway Hangout with Docs and Core team members approximately two weeks after this post. Details will be shared in the comments — watch this post if you’d like to join. The Meeting link will be shared in the #core-editor channel the day of the Hallway Hangout.
Timeline
Milestone
Date
Feedback period opens
5th May
Hallway Hangout
18th May – 14:00 UTC
Feedback period closes
25th May
Next steps announced
Shortly after close
Feedback collected from the community will help refine the proposal and inform next steps for implementation.
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 ticketticketCreated 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.
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCoreCore 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.
The Presence API is an experimental feature pluginFeature PluginA plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See 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.
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. 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. Same setup, 40 seeded editors — useful for seeing how the widgets, admin bar, and post list handle density.
What the pluginPluginA 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/ or can be cost-based plugin from a third-party. provides
Dashboard widgets: “Who’s Online” and “Active Posts”
Admin bar online indicator with avatarAvatarAn 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” filterFilterFilters are one of the two types of 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-CLIWP-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/https://make.wordpress.org/cli/ commands
Post-lock bridge (coexists with existing _edit_lock behavior)
All features are gated on the edit_postscapabilitycapabilityA 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.
Background
During WordPress 7.0 development, discussion in #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. The plugin was presented at a coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat and subsequently transferred to the WordPress GitHubGitHubGitHub 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/ organization. It was submitted to the WordPress.orgWordPress.orgThe 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/ plugin directory on April 6, 2026.
Feedback welcome
This plugin is experimental. Feedback on the following is especially helpful:
Are the UIUIUser interface surfaces (widgets, admin bar, post list) useful as presented?
Are there admin screens or workflows where presence would be valuable?
“What’s new in GutenbergGutenbergThe 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/” posts (labeled with the #gutenberg-newtagtagA 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 of different ways to keep up with Gutenberg and the Editor.
This release introduces a revisionsRevisionsThe 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 metaMetaMeta 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 blockBlockBlock 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 were merged in Gutenberg 23.0, with 8 first-time 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 sidebarSidebarA 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)
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)
Other Notable Highlights
Real-time Collaboration, legacy meta box compatibility.PluginPluginA 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/ 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)
Real-time Collaboration, reliability. Concurrent edits to array-type block attributes — such as table rows — are now preserved when the array is restructured (#77164). A single corrupted sync update no longer crashes the whole poll cycle and disconnects every room (#76968). Gutenberg’s activation hook now honors the CoreCoreCore 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).
Keyboard shortcuts for moving blocks surface in tooltips. The block toolbar’s move-up / move-down tooltips now display their keyboard shortcuts. (#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)
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)
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 TypeWordPress 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, #77223)
Changelog
Enhancements
Components
wordpress/ui: Add global CSSCSSCascading Style Sheets. defense module. (76783)
Adminadmin(and super admin)UIUIUser interface: Increase page headerHeaderThe 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)
Admin UI: Update Page background color to surface-neutral. (76869)
RTC: Add filterable flag for meta box RTC compatibility. (76939)
RTC: Change SyncConnectionModal to isSyncConnectionErrorHandled filterFilterFilters are one of the two types of 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)
Block Editor
Display shortcuts for moving blocks via tooltips. (76992)
Re-order spacing side controls when unlinked. (66317)
Connectors
Update the AI plugin settings page slug we link to after activation. (77336)
DataViews
Classify admin-ui and dataviews to components. (76959)
REST APIREST APIThe 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/
Add date field in templates and template parts. (77134)
Media
Media Modal Experiment: Set matching picker grid layout properties for when a user switches layouts. (77118)
Collaboration
BackportbackportA 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)
RTC: Add optional shouldSync function to entity sync configuration. (76947)
RTC: Respect WP_ALLOW_COLLABORATION in Gutenberg for activation hook. (77084)
Site Editor
Add Site Tagline and Site Title to Design > Identity panel. (76264)
RTC: Fix inline inserter reset on update sync. (76980)
RadioControl: Add support for disabling radio group. (77127)
Remove sandbox allow-same-origin for core/htmlHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. blocks. (77212)
Fix failing ‘WP_HTTP_Polling_Sync_Server’ unit testunit testCode 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.. (77025)
RTC: Fix disconnect dialog due to uneditable entity. (77242)
RTC: Isolate sync update failures to prevent full disconnect. (76968)
Global Styles
Fix duotone filter not applying on style variation switch. (77229)
Global Styles Revisions: Fix footer overflow. (77103)
DataViews
Fix Gutenberg_REST_View_Config_Controller_7_1 PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher warnings. (77290)
Patterns
Fix custom categoryCategoryThe '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)
Media
MediaEdit: Handle ‘*’ wildcard in validateMimeType. (77168)
Client Side Media
Use image.copyMemory() for batch thumbnail generation. (76979)
AccessibilityAccessibilityAccessibility (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)
Performance
Post Editor
Autocompleters: Move and improve links search. (76995)
Client Side Media
Add performance metrics for client-side media processing. (76792)
Experiments
Post Editor
Add revisions panel to templates, template parts and patterns. (77008)
Documentation
Add missing documentation in collaboration.php. (77173)
UI: Use Link component in details story example. (76997)
iAPI Docs: Fix typos, code errors, and inaccuracies in the documentation. (76636)
ui/docs: Add additional global css setup instructions. (77228)
Code Quality
TypeScript: Migrate a11yAccessibilityAccessibility (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)
Theme: Rename typography tokens to use “typography” prefix. (76912)
Update ReactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces.
https://reactjs.org function names for better ESLint detection. (77148)
i18ni18nInternationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. 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)
ui/Card: Remove redundant margin reset from Card.Title. (77187)
Build: Fix glob ignore patterns in dot-prefixed directories. (75114)
Convert directories in test/ to workspaces. (74684)
Env: Fix loopback requests when running on non-default ports. (77057)
Fix lint-staged APIAPIAn 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)
Resolve package-lock.jsonJSONJSON, 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/eslint-parser. (77256)
Storybook: Fix end-to-end subpath exports and add CI build smoke test. (77034)
Refactor: Migrate bin/api-docs to tools/api-docs as workspace @wordpress/api-docs-generator. (77019)
Below you find a table that lists all coreCoreCore 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 blockBlockBlock 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 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_attributesfilterFilterFilters are one of the two types of 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 and Block Bindings improvements in 6.9dev notesdev noteEach 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
✅
–
–
✅
–
–
–
AvatarAvatarAn 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
✅
–
–
–
–
–
HTMLHTMLHyperText 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 ExcerptExcerptAn 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 imageA 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.
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. 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 betaBetaA 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, publishing a post on the change, and updating this post as the canonical reference.
Date (UTC)
Milestone
Emcee / Release LeadRelease LeadThe community member ultimately responsible for the Release.
CommittercommitterA 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.
@audrasjb Committing from WordCampWordCampWordCamps 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. Nice Contributor DayContributor DayContributor 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/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/!
RCrelease candidateOne 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). 1
The full chat log is available beginning here on Slack.
Performance Lab PluginPluginA 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/ or can be cost-based plugin from a third-party. (and other performance plugins)
@mukesh27 shared that @westonruter discussed the Auto Sizes feature during WordCampWordCampWordCamps 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. Asia and opened issue #2449 to outline next steps for further work. @mukesh27 mentioned plans to review the issue and pick it up again when possible, and invited others to contribute in the meantime.
@mukesh27 also noted that resolving the sizes issue for the Gallery blockBlockBlock 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 CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
@ravikhadka replied expressing interest in working on the feature.
You must be logged in to post a comment.