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.
As of WordPress 7.0, any 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. attribute that supports Block Bindings also supports Pattern Overrides. So now, you can use Pattern Overrides for any block you want — even custom blocks — the previous limit to a hardcoded set of CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks no longer holds you back. To get started, opt in through the server-side block_bindings_supported_attributes filter(s).
The underlying Block Bindings mechanism will make sure that:
In dynamic blocks, the correct, bound attribute values will be passed to render_callback().
In static blocks, the HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.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. is used to locate attributes sourced from html, rich-text, or attribute sources via their selectors in the persisted markup, replacing their values with the respective bound attribute values.
Bound attribute values should appear correctly in the rendered blocks’ markup in these cases. You shouldn’t need any other modifications.
For static blocks with unsourced attributes, or with sourced attributes whose selectors are more complex than the HTML API currently understands, you might need to add a render_callback() or a render_blockfilterFilterFilters 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. to make sure bound attribute values are correctly handled. It’s best if you first try without (i.e. by only adding the attribute via block_bindings_supported_attributes filter). Then, if the bound attribute value doesn’t render, add the callback or the filter that guarantees the render.
Props to @fabiankaegy and @marybaum for reviewing this dev notedev 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.!
WordPress 7.0 expands contentOnly editing to unsynced patterns and template parts.
The key behavioral change is that unsynced patterns and template parts inserted into the editor now default to contentOnly mode, prioritizing the editing of text and media without exposing the deeper 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. structure or style controls.
Pattern-level editing modes
At times a user will want to make design changes to a pattern, and this works differently depending on the type of pattern.
Unsynced — A user can click an ‘Edit pattern’ button or double click the body of a pattern, and a spotlight mode engages. In this mode users have full editing capabilitiescapabilityA 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)..
Synced (synced patterns / template parts) — Users can click the ‘Edit original’ button and are taken into an isolated editor when they can make any changes to the underlying pattern. The editor 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. provides navigation back to the originating document. Changes to synced patterns apply globally.
What developers need to do
Block authors
If your block is nested in a contentOnly pattern and should be editable, ensure attributes that represent a block’s content have "role": "content" set in block.json. This is unchanged from WordPress 6.7, but is now more important as contentOnly mode is applied more broadly by default.
Blocks without any "role": "content" attributes will be hidden from List View and non-selectable inside a contentOnly container.
At times a block may not have an appropriate attribute to which to apply "role": "content". A "contentRole": true property can be added to the block supports declaration, and this has the same effect as "role": "content".
{
"supports": {
"contentOnly": true
}
}
Developers should prefer "role": "content" where possible.
Parent / child contentOnly blocks
Many blocks are considered ‘content’, but consist of both parent and child block types. Some examples of CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks are:
List and List Item
Gallery and Image
Buttons and Button
Whenever both a parent and child block have a "role": "content" attribute or "contentRole": true block supports, contentOnly mode allows insertion of child blocks. This behavior has been present since WordPress 6.9, but is now more prominent.
Block developers can take advantage of this behavior.
List View block support
New for WordPress 7.0, block developers can add a "listView": true block supports declaration. This adds a List View tab to the block inspector with a dedicated List View UIUIUser interface for the block that allows users to easily rearrange and add inner blocks. This List View is also displayed in Patterns and is recommended for any block that acts as a container for a list of child blocks.
{ "supports": { "listView": true } }
Theme / pattern authors
Patterns that previously relied on unrestricted editing of their inner blocks will now be presented to users in contentOnly mode by default. Review your registered patterns and consider:
Testing that the content users are expected to change is accessible in contentOnly mode.
Auditing patterns containing Buttons, List, Social Icons, and Navigation blocks specifically — these have had targeted contentOnly improvements and may behave differently than before.
Restrict the allowed blocks if users shouldn’t be able to insert blocks in a specific area of a pattern. If assembling a pattern in a block editor, this can be done using the ‘Manage allowed blocks’ feature in the Advanced section of the block inspector for any blocks that have "allowedBlocks": true block support. Through code, the "allowedBlocks":[] attribute can be added to prevent insertion of inner blocks.
Site admins
A new block editor setting, disableContentOnlyForUnsyncedPatterns, allows opting out of contentOnly mode for unsynced patterns. Via PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher, use the block_editor_settings_allfilterFilterFilters 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.:
Or via JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser.
https://www.javascript.com:
When disableContentOnlyForUnsyncedPatterns is true, blocks with patternName metadata are no longer treated as section blocks and their children are not placed into contentOnly editing mode. Template parts and synced patterns (core/block) are unaffected — they remain section blocks regardless of this setting.
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. developers
If your plugin interacts with pattern editing state — toolbar controls, 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. panels, List View visibility, or entity navigation — test against the new editing modes. The contentOnly state is now applied more broadly, and UI components that assume full block access inside patterns may not render as expected.
Props to @talldanwp and @andrewserong for helping to write this dev notedev 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..
As of WordPress 6.9, you can hide any 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. entirely with blockVisibility: false in block metadata. In WordPress 7.0, viewport-based visibility rules give your users the power to show or hide blocks per device type — desktop, tablet, or mobile — without affecting other viewports.
Controls are available in the block toolbar, block inspector 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., and command palette to launch the block visibility options modal. In List View, blocks with active visibility rules show icons that indicate which viewports they are hidden on.
Note: Blocks hidden by viewport are rendered in the DOM. The hiding happens in the CSSCSSCascading Style Sheets..
That’s different from blockVisibility: false. That keeps the block from rendering in the DOM, thus it can’t ever show on the front end.
Updated blockVisibility metadata structure
The existing hide-everywhere behavior has NOT changed:
{
"metadata": {
"blockVisibility": false
}
}
But in WordPress 7.0, a new viewport key gives you and your 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.-literate users finer control, per breakpoint:
The viewport key is deliberately nested, leaving room for more sources (e.g., user role, time-based rules) to come in 7.1 and beyond.
The three supported viewport keys are mobile, tablet, and desktop. In 7.0 these map to fixed breakpoints, but you can expect configurable breakpoints and theme.json integration in WordPress 7.1 — see #75707.
Here’s how this all looks in serialized block markup:
<!-- wp:paragraph {"metadata":{"blockVisibility":{"viewport":{"mobile":false}}}} -->
<p>Hidden on mobile.</p>
<!-- /wp:paragraph -->
How to get your theme or 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. ready
Does your theme or plugin generate, transform, or parse block markup server-side? Then its blockVisibility metadata field might now contain a boolean (false) or an object ({ viewport: { ... } }). If your code assumes a scalar value, you’ll want to update it to handle both forms.
Blocks and patterns that include hardcoded blockVisibility metadata will work out of the box, and so will your reusable blocks that have visibility rules.
If your blocks don’t interact with markup on the server
Then you don’t have to do anything! Viewport visibility is part of the blockVisibility block support and applies automatically. You don’t need a separate opt-in in block.json.
Coming soon! To a future release near you
Current plans call for configurable breakpoints and theme.json integration for block visibility to land in WordPress 7.1. At that point, you’ll be able to let your themes and other products define almost any viewport labels and breakpoints you need, far beyond the fixed mobile/tablet/desktop defaults. Follow #75707 for progress.
Props to @andrewserong and @marybaum for helping to write this dev notedev 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..
WordPress 7.0 expands the Dimensions 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. supports system with three significant improvements: width and height are now available as standard block supports under dimensions, and themes can now define dimension size presets to give users a consistent set of size options across their site.
Background
Previously, blocks that needed width or height controls implemented them as custom block attributes with their own editor UIUIUser interface. This led to duplicated code, inconsistent experiences across blocks, and no straightforward way to define width or height values through Global Styles or theme.json. The broader Block 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. goal is to handle these concerns uniformly through block supports, the same system that already covers spacing, typography, color, and more.
Once opted in, the block gains a width input in the Dimensions panel of the block inspector and in the Styles panel of the Site Editor (under Styles > Blocks > Block Name). Theme authors can define default width values for specific block types via theme.json:
Alongside the new width and height supports, themes can now define a set of named dimension size presets via theme.json. These presets appear in the width and height controls, giving users a consistent palette of sizes to choose from rather than requiring manual entry of values each time.
Define presets under settings.dimensions.dimensionSizes:
Machine-readable identifier (used to generate a CSSCSSCascading Style Sheets. custom property)
size
Any valid CSS length value (px, %, em, rem, vw, vh, etc.)
The presets generate CSS custom properties following the --wp--preset--dimension-size--{slug} naming convention, consistent with other theme.json presets.
Control rendering: The number of presets defined affects how the control is rendered:
Fewer than 8 presets: A slider control is shown, allowing users to step through the preset values.
8 or more presets: A select list (dropdown) is shown instead to keep the UI manageable.
In both cases, users can still enter a custom value directly.
Backwards Compatibility
These are additive changes. No existing blocks are broken. Blocks that do not opt in to dimensions.width or dimensions.height in their block.json are unaffected.
Blocks that currently implement custom width or height controls as attributes are encouraged to evaluate migrating to the new block supports, but this is not required in WordPress 7.0.
The dimensionSizes preset key is new; themes without it simply have no presets defined, which is the default behavior — users can still enter free-form values in the width and height controls.
WordPress 7.0 introduces the ability to add custom CSSCSSCascading Style Sheets. directly to individual 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. instances from within the post and site editors. This closes a long-standing gap in the block styling system: while Global Styles has supported block-type-level custom CSS since WordPress 6.2, there was no built-in way to target a single specific block on a specific page without a multi-step workaround.
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/ issue:#56127 | PR:#73959
The Problem
Previously, applying one-off CSS to a specific block instance required a workaround: add a custom class name to the block, then write a matching rule in the Site Editor’s global Custom CSS field. This two-step process was not obvious to most users, and was entirely unavailable to content editors who lack access to the Site Editor.
Plugins emerged to fill this gap, confirming genuine demand for the feature.
What Changed
A new customCSS block support is registered. It provides a Custom CSS input inside the Advanced panel of the block inspector — the same panel that already contains the “Additional CSS Class(es)” field.
The panel behaves the same way as the block-type custom CSS field in Global Styles:
Only CSS declarations are needed — no selector is required.
Nested selectors can be written using & (e.g., & a { color: red; } targets anchor tags inside the block).
HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. markup in the CSS field is rejected.
The field is only visible to users with the edit_csscapabilitycapabilityA 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)..
How It Works
Storage
Custom CSS is stored in the block’s existing style attribute, under the css key — the same attribute that stores other block-level style overrides:
At render time, a unique class is generated for the block instance using a hash of the block’s content and attributes. The class is applied to the block’s outermost HTML element alongside a has-custom-css marker class:
The generated stylesheet is registered with a dependency on global-styles, ensuring block instance CSS loads after — and can therefore override — both WordPress defaults and Global Styles block-type CSS.
Editor Preview
The custom CSS is also applied live in the editor using a scoped style override, so changes are reflected immediately without saving.
Opt-Out
The customCSS support is enabled by default for all blocks. Block authors who need to opt out — for example, blocks that render raw content or have no meaningful outer element — can disable it in block.json:
{
"supports": {
"customCSS": false
}
}
The following coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks opt out by default: core/freeform, core/html, core/missing, core/more, core/nextpage, core/shortcode, and core/block (the Reusable Block wrapper).
Capability Check
The Custom CSS panel is gated by the edit_css capability. Users without it will not see the field in the block inspector. This is the same capability used to control access to the Custom CSS field in the CustomizerCustomizerTool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. and in Global Styles.
For 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 Theme Developers
No action is required for most blocks and themes. The support is enabled automatically.
If you maintain a block that should not expose a custom CSS input — because it wraps raw or opaque content, or because adding a class to its root element would break its rendering — add "customCSS": false to your block’s supports in block.json.
If you render blocks server-side using render_callback or render in block.json, the class will be injected into the first HTML element in the rendered output via WP_HTML_Tag_Processor. Ensure your block renders a standard HTML element as its outermost tagtagA 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.).
WordPress 7.0 introduces a new textIndentblockBlockBlock 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. support for typography, allowing blocks to opt in to text-indentCSSCSSCascading Style Sheets. support. The Paragraph block is the first coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. block to adopt this support.
Background
Text indentation is a standard typographic convention, particularly in long-form publishing. It has been one of the most-requested typography features for WordPress blocks since 2021 (#37462).
With this release, WordPress now supports it natively through a new block support. No custom CSS required.
The textIndent Block Support
Any block can now declare support for textIndent in its block.json:
When a block declares this support, the block editor will show a Line Indent control in the Typography panel of the block 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., and the block’s style.typography.textIndent attribute will be serialised as a text-indent CSS property.
This follows the same pattern as other typography block supports such as letterSpacing, textDecoration, and textTransform.
Paragraph Block: Selector Behaviour and the textIndent Setting
The textIndent support has a unique consideration specific to the core Paragraph block: in traditional typographic conventions of English and some other left-to-right (LTR) languages, only subsequent paragraphs (those that follow another paragraph) are typically indented, while the very first paragraph in a sequence is not. In some right-to-left (RTL) languages and publishing traditions, such as Arabic and Hebrew, however, it is common to indent all paragraphs.
To accommodate both conventions, a typography.textIndent setting controls which CSS selector is used when generating the text-indent rule. This setting is distinct from the style value (the actual indent amount) and applies at the Global Styles level.
Setting value
Selector used
Behaviour
"subsequent" (default)
.wp-block-paragraph + .wp-block-paragraph
Only paragraphs immediately following another paragraph are indented
"all"
.wp-block-paragraph
All paragraphs are indented
Note: This selector behaviour is specific to core/paragraph. Third-party blocks that opt in to textIndent support will have text-indent applied using their own block selector, but the subsequent/all switching logic is not currently available to them.
In Global Styles, an “Indent all paragraphs” toggle lets authors switch between the two modes interactively.
Configuring via theme.json
Themes can enable and configure Line Indent support through theme.json.
Enable the control with default (subsequent) behaviour:
This is a new opt-in feature. No existing block behaviour changes unless a block explicitly declares "textIndent": true in its supports.typography definition. There are no breaking changes to existing APIs.
Further Reading
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/ issue: #37462
After aligning with @photomatt and @4thhubbard, I’m excited to announce a call for volunteers to work on the Twenty Twenty-Seven default theme alongside @iamarinoh who has been chosen as the lead designer. Please comment below to express your interest in helping with the development of the theme.
As a reminder, the default theme ships with the last release of the year. For this year, that will be 7.2 which is set to be released in early December. For anyone volunteering to help, please keep this timeline in mind as it means being available to help during that timeframe in particular as well as in these early stages.
To set us all up for success, this call for volunteers is being shared on the early side so folks have plenty of time to get started, complete iterations, and land something wonderful for the broader community. Thanks to all who consider helping with the next default theme!
If you are interested in volunteering, please leave a comment belowby Friday, March 27th.
“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-new tag) 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.
New Connectors Screen and 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.
We have added a new “Connectors” adminadmin(and super admin) page under Settings > Connectors, which allows users to see and manage their connectors. We using an OpenAI connector demonstration as the first example, and we’ve also provided extension hooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. for plugins to add their own connectors. These screens are still in an experimental state. (75833, 75948, 76014)
Previews for style variation transforms
Style variation transforms now display a preview in the editor. This makes it easier to see the impact of transformations before committing to the change.
Style variations are now also available for patterns in contentOnly mode. (75889, 75761)
Improved Visualizer responsiveness in Grid 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.
The Grid block Visualizer is now synchronized quickly and accurately with the selected number of columns:
This makes it easier and quicker to build grid based layouts. (75820)
Playlist block now has a visualizer
We added WaveForm Player as a visualizer to the Playlist block. This gives users a visual representation of the audio file they are listening to, and opens the door to more designs for the block:
Please note that this block is still in an experimental state. (75203).
Other Notable Highlights
Content Guidelines: We added a new experimental 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/ and 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., to allow WordPress site owners to define and manage site-wide content rules (75164, 76187, 75420, 76155)
wp-env: We added phpMyAdmin support to the wp-env Playground runtime and introduced a new phpmyadmin boolean configuration option for cleaner enable/disable control. (75532)
Components: We added word-break: break-word to buttons to fix buttons with very long text (76071)
Custom CSSCSSCascading Style Sheets.: We now allow defining custom selector for CSS selectors in 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., which means that Global Styles can be applied to elements within the block. (75799)
Media Library: Optimise image loading for the media thumbnail field for better performance (75811)
Real Time Collaboration: Real Time Collaboration is now enabledf by default (75739)
Changelog
Enhancements
Add phpMyAdmin support to wp-env Playground runtime. (75532)
Connectors: Add _ai_ prefix to connector setting names. (75948)
Connectors: Dynamically register providers from WP AI Client registry. (76014)
Sync connector PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher behavior with CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.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. changes. (75968)
Content Guidelines: Add UXUXUser experience for site, copy, image, and additional guidelines (75420)
Guidelines: Add actions for Import, Export and 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. of guidelines (76155)
DataViews
Adjust column spacing in table layout when no titleField is provided. (75410)
Improve UI in list layout when we render only title and/or media fields. (76042)
MediaEdit: Auto-fill columns based on minimum item width. (75509)
Add previews for style variation transforms. (75889)
Try enabling style variation transforms for blocks in contentOnly mode. (75761)
Site Editor
QuickEdit: Rename status label and remove extra labels in popup. (75824)
Components
Refactor ColorPicker to preserve hue/saturation at achromatic colors. (75493)
ToggleGroupControl: Make unselected item color consistent across all variants. (75737)
Global Styles
Block Supports: Define CSS vars for blocks based on feature selectors. (75226)
Bug Fixes
Block editor: Force LTR direction in block HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. editing mode. (75904)
Remove Core’s full-page render interceptors for boot-based pages. (76036)
Theme: Add build plugins to inject design token fallbacks. (75589)
Theme: Remove global design tokens stylesheet. (75879)
wp-build: Deregister script modules before re-registering. (75909)
CI: Don’t build release notes during 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. build workflow for WP Core sync (76398)
Collaboration
Fix change-detection and new-post end-to-end tests after RTC enabled by default. (75751)
RTC: Back off when the window loses focus. (75843)
RTC: Bugfix: Fix casing of getPersistedCRDTDoc. (75922)
RTC: Fix fallthrough for sync update switch statement. (76060)
RTC: Fix stale CRDT document persisted on save. (75975)
RTC: Fix syncing of emoji / surrogate pairs. (76049)
RTC: Fix undefined array_first() call in sync storage. (75869)
Image: Hide ‘Set as 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.’ for in-editor revisions. (76123)
Navigation Link: Compare internal links by host instead of origin. (76015)
Navigation Overlay Close: Set Close as default text, rather than using a placeholder. (75692)
InvalidinvalidA resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. block selected style. (75796)
PHP-only Blocks: Reflect bound attribute values in inspector controls. (76040)
Pattern Editing: Fix sibling blocks to edited pattern not being disabled. (75994)
RichText: useAnchor: Fix TypeError in virtual element. (75900)
DataViews
DataForm: Fix focus loss and refactor Card layout. (75689)
DataForm: Fix text overflow for long unhyphenated text in panel layout. (76073)
Fix 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. toggle flickering when there are locked or primary filters. (75913)
Fix focus transfer while searching in list layout. (75999)
Admin UI: Fix type mismatch between Page title and NavigableRegion ariaLabel. (75899)
Editor: Remove View dropdown and pinned items from revisions 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.. (75951)
Fix: Skip scaled image sideload for images below big image threshold. (75990)
Client-side media processing: Try plumbing invalidation to the block-editor’s mediaUpload onSuccess callback (76173)
Client-side media processing: only use media upload provider when not in preview mode (76124)
Font Library
Fix: Use the same context for font library tabs translations. (75930)
Interactivity API
Interactivity Router: Fix back and forward navigation after refresh. (75927)
Interactivity: Fix crypto.randomUUID crash in non-secure contexts (76151)
Patterns
Unsynced patterns: Rename ‘Disconnect pattern’ to ‘Detach pattern’ in context menu. (75807)
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)
Block Editor
Fix writing flow navigation for annotation style, or any other block with border radius. (76072)
Media Thumbnail Field: Optimise image loading. (75811)
Experiments
Post Editor
RTC: Disable multiple collaborators if 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 are present. (75939)
Content Guidelines
Add experimental REST API and custom post type. (75164)
Workflows: Use pull_request_target for cherry-pick workflow. (75775)
wp-env: Enable pretty permalinks by default in Docker runtime. (75688)
Build Tooling
Build: Clean top-level build/ directory during clean:Packages. (75961)
ESLint: Add no-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.-in-save rule. (75617)
Prevent CSS modules in build from breaking Jest tests. (75792)
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.
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. 5 scheduled for Thursday, March 12th, at 15:00 UTC
New Dev 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.:
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.
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.
You must be logged in to post a comment.