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 “Post” (or “Page”) tab of the editor’s Settings 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. is being rebuilt on top of DataForm, the same form that Quick Edit uses in the Site Editor. It’s available as a 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/ experiment and it’s ready for testing, mostly by 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 whose code extends that part of the editor. If you’re a site owner using plugins that add things there, there is a flow for you too.
What is it?
With the “Editor Inspector: Use DataForm” experiment on, 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 the classic summary panels of the post inspector (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., 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., status, date, author, template, etc.) are replaced by a DataForm, for every post type that uses the block editor. The settings follow what each post type supports.
The same form definition is also used to build the Quick Edit interface in the Site Editor.
For users, a cohesive experience: the inspector in the post editor and Quick Edit in the Site Editor show the same information and should look and behave the same, instead of drifting apart.
Quick Edit interface
For developers, APIs that work across both screens: controlling which settings show (this is one example, and it’s possible today with the view config 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 adding your own fields through the fields 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., so they show up in the inspector and in Quick Edit (#61084, #74865). The fields API is aimed for 7.2.
How to test
Install Gutenberg 24.0 or newer on a test site and turn on “Editor Inspector: Use DataForm” under Settings > Gutenberg. Then open a post and compare the Post tab with the experiment on and off. It’s always better to test in 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. because it’s the most current version, but Gutenberg 24.0 is acceptable.
Note: Gutenberg trunk needs WordPress 7.0 or later, the 24.0 release also works on 6.9. Either way, please mention which version you tested.
If you develop a plugin, your own dev environment with Gutenberg installed is all you need.
For a quick look without setting anything up there is WordPress Playground, with the experiment already on: Gutenberg 24.0, trunk or theeditor.MediaUploadPR (more on that below). To test your own plugin there, install it from the Plugins screen as usual, or upload its zip.
What to expect
PluginDocumentSettingPanel, PluginPrePublishPanel, PluginPostPublishPanel, PluginSidebar, PluginPostStatusInfo fills and removeEditorPanel keep working.
The PluginPostExcerpt slot is not ported. It’s a deprecated API and we’re considering not adding it at all, so whatever you render there should move to a PluginDocumentSettingPanel.
The editor.PostFeaturedImage filter doesn’t work yet. It might be ported, but anything targeting the classic panels’ CSSCSSCascading Style Sheets. class names or markup won’t be.
The featured image picker doesn’t go through the editor.MediaUpload filter yet. There is an exploratory PR which adds that, but it’s on hold for now (see why).
Hiding a default setting or changing where its label sits is already possible with the server side view config filter, get_entity_view_config_posttype_post for posts (see docs). There is an example in this GitHub issue.
Suggested testing flows
You don’t have to follow these exactly, they’re mostly here to give you ideas.
What your plugin adds to the inspector
Open a post with your plugin active. Is everything you add to or change in the Post tab (panels, fills, filters, styles, scripts) still there, and does it still work?
Your custom post types
If you register post types that use the block editor, open one of them. You should only see the settings the post type supports (for example no excerpt setting without excerpt support). Please report anything missing or extra there.
Other user roles
Log in as an editor, author or contributor and open a post. The settings should match what the role can do, like in the classic inspector (an author doesn’t get the Author setting, for example), and saving should still work. Some known issues have already be fixed in trunk (#82844, #82857, #82858).
The editor.MediaUpload filter
The featured image picker doesn’t go through the editor.MediaUpload filter yet. If your plugin replaces the media picker through editor.MediaUpload, you should test against this PR that adds it. You can try it in Playground or with the PR applied, both in the post editor and in Quick Edit in the Site Editor, and share what you find on the PR.
Site owners
You don’t need to be a developer for this one. If you use plugins that add things to the Post or Page tab (SEO or social fields, custom panels, that kind of thing), enable the experiment on a test site or in Playground and check they are still there. If something is missing, please share the plugin name and version, and a screenshot with the experiment on and off.
Sharing your feedback
Comments on this post are fine, but the best place is the GitHub issue for this call for testing. Share what you extend, what changed, and whether you can adapt on your side or need something from Gutenberg. “Checked X, nothing changed” is useful too. Feedback about the inspector itself (layout, labels, missing controls) is welcome on the tracking issue, where the open design questions are discussed.
There is no deadline, but the sooner the better, since this is aimed for 7.2.
Out of scope
The goal here is compatibility, what happens to the things plugins add to the inspector. A few things are handled separately:
Block editing, taxonomyTaxonomyA 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. panels and 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. The experiment doesn’t touch them.
Some design questions are still open, like which settings should be regular fields instead of panels, or the Reset button of the Date setting, which isn’t there for now and may come back in a follow up. These live in the tracking issue.
Thanks in advance for testing! Props to @mcsf for reviewing this post.
Ipsum is the proposal for the next default theme, planned to be bundled in WordPress 7.2. It is an intentionally minimal blogblog(versus network, site) theme that centers on a blank canvas to make your own, with built-in room for creativity. The approach for this theme also marks a move away from year-based naming, based on direction from @matt. Going forward, default themes will have their own names and change when the design calls for it, not when the calendar does. The road to 7.2 is short, so we’re opening Ipsum for testing now—the sooner we get feedback, the more it will shape the release.
How we got here
Months ago, we began to develop the default theme, building real demo pages directly in the Editor rather than in Figma mockups. That work started as Mētis, a theme for writers, makers, and thinkers, designed to showcase the design possibilities 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/ now offers. After reviewing the direction with Matt, we shifted: the default theme bundled with WordPress should be the simplest possible starting point, and the more expressive design can still stand.
There’s a principle behind this choice: build in public, and ship. Mētis is a powerful theme that’s diverse and opinionated, with lots of ways to stretch what’s there. However, Matt gave clear direction to go with a simpler blank canvas style approach that could appeal more quickly to more people to make their own. That’s why we picked a blank canvas blog design and are sharing it with the public for suggestions, instead of making Mētis the one. Real artists ship.
Mētis remains a separate theme that won’t ship with this release. Our new flagship theme will have its own post as soon as it’s ready to download and test.
Ipsum is a blank canvas built around the blogging experience, our proposal for what this year’s default theme should be. Named after lorem ipsum, the placeholder that fills a page until real content arrives, it is composed enough to stand on its own and to be transformed the moment people start writing.
It keeps the page quiet: dotted underlines from an editor’s pencil, a handful of typesets, and style variations that re-ink the whole page, images included. Every combination passes WCAGWCAGWCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. AA. Headers, heroes, and sidebars are there when you reach for them, but remain invisible when you just want to write.
What’s available today reflects the design work; development review is still ahead. The window before 7.2 is tight, so this is a focused ask: try it and tell us what breaks and what’s missing. We’ll fold in what we can before the release; what we can’t will shape the updates that follow, as it does for every default theme.
As part of the 7.2 release, Carolina Nymark (@poena), Maggie Cabrera (@onemaggie), and Juanfra Aldasoro (@juanfra) are leading development, while Henrique Iamarino (@iamarinoh) is leading design and theme building. The current build reflects the design work; the formal development review comes next, folding in what we hear from you along the way—we look forward to your involvement throughout the process.
Learn more
For information about previous default themes, read the following posts:
Here are a few resources if you’re interested in learning more about 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. Themes and the Site Editor:
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.
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.
“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.
This version extends visual 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. to include the post title, gives 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. a grid layout with per-breakpoint controls, and lets a site title scale to the width it is given.
Visual revisions now cover the post title
Visual revisions have been growing over the last few releases, and until now the post title sat outside them. In 24.0, the title participates like any other piece of content, including displaying change diffs directly in the post title (#82536, #82586).
Seeing it in the same view as body changes removes the need to guess when a rename happened.
A more adaptable Gallery block
The Gallery block gains a Grid variation that can be switched on from the block inspector, replacing the default non-editable flex layout with a fully customizable grid (#81909).
“Column count” and “Crop images to fit” can now also be set per breakpoint through viewport states. A gallery can show four columns on a wide screen and two on a tablet without any custom CSSCSSCascading Style Sheets. (#82003).
Site titles that fill their available space
The Site Title block now supports fit-text (#82074). Toggle it on from the ellipsis menu in the typography panel and the title scales to the full width available to it, rather than being sized in points and left to wrap or fall short.
Other notable highlights
A redrawn icon set. Nearly 100 icons have been redrawn from a mix of filled and outlined shapes into a single, consistently stroke-based visual language (78812, 78808, 82338).
Tab indents lists. In the List block, Tab and Shift+Tab now indent and outdent a fully selected list item, and work across a multi-item selection instead of only at the caret (82460, 82411).
Background images from a URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org. Background image support can now accept an image URL, rather than requiring an entry in the Media Library (82230).
Non-breaking spaces are visible. The format library now visualizes non-breaking spaces, so a character that silently changes wrapping is no longer invisible while editing (74040).
Changelog
Enhancements
Components
Add defaultShown, onShownChange to ToolsPanelItem. (78010)
Border Box Control: Try moving the unlink button to the label row, and rename the panel to Borders. (82163)
DataForm: Add a showPlaceholderIfEmpty option to the panel layout. (82527)
DataForm: Communicate the timezone in the datetime control. (82291)
Editor: Migrate post-card-panel Badge to UI Badge. (82500)
Global Styles UI: Migrate revisions Active Badge to UI Badge. (82560)
Icons: Redraw 35 prominent icons with consistent stroke widths. (78808)
Icons: Redraw 64 icons to be stroke-based. (78812)
Menu: Stabilize portaled iframeiframeiFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.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.. (82092)
Menu: Use Text for item labels and descriptions. (82237)
SearchableSelect: Add form primitive to wordpress/ui. (80961)
Storybook: Persist 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. theme in URL. (82111)
Support isAny and isNonefilterFilterFilters 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. operators for numeric fields. (77942)
Tab Panel: Show focus with outline instead of legacy box-shadow ring. (82421)
Validated form controls: Use design token for 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. focus rings. (82410)
List: Indent and outdent a fully selected list item with Tab. (82460)
List: Indent and outdent multi-selected items with Tab. (82411)
Query LoopLoopThe Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop: Rename the “Keyword” filter to “Search terms” and add help text. (82387)
Query: Replace the “Reload full page enabled” modal with a snackbar notice. (82246)
feat: Introduce ‘Add Media’ in the block controls for media-text block. (82420)
Post Editor
Autocompleters: Consider email address context in user mention. (47249)
CSS Styling: Represent focus with outline for list view component. (82129)
DataViews: Append an ellipsis to action labels that open a dialog. (81994)
Editor: Refactor the Options menu to use the Menu component. (81564)
Editor: Refactor the View menu to use the Menu component. (82321)
Editor: Render change diffs in the post title in revisions. (82586)
Editor: Show revision data in Post Title component. (82536)
Media: Attach unattached media to the current post on save/publish. (81977)
Menu: Align selection indicators and prefix icons with item labels. (82346)
Post slug: Prefer server sanitization in the editor. (78135)
Try: Add “reading settings” link to Front Page template. (81987)
Site Editor
Add New Template: Show the design system focus ring instead of legacy box-shadow rings. (82164)
Add a root error boundary to prevent a blank screen. (82486)
Site editor v2: Identity takes its form from the view configuration endpoint. (82692)
Site editor v2: Navigation takes view configuration from endpoint. (82138)
Site editor v2: Pages take view configuration from endpoint. (82140)
Site editor v2: Patterns take view configuration from endpoint. (82458)
Site editor v2: Template parts take view configuration from endpoint. (82457)
Site editor v2: Templates take view configuration from endpoint. (82456)
Site editor v2: Use the canonical template fields in the templates list. (82666)
Site editor v2: Use the canonical wp_block fields in the patterns list. (82672)
Block Editor
Background image: Support setting the image from a URL. (82230)
BlockPreview: Assert preview contents are inert. (82682)
Format library: Visualise non-breaking spaces. (74040)
List View: Disable block icon colors while the block is selected. (82498)
Show the block outline where the grab cursor shows. (81798)
Tab trap escape hatch: Leave/enter the canvas with Escape/Enter. (82314)
Dashboard
Site Health widgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user.: Route the body’s review link through the host. (82066)
Widget Dashboard: Add a Policy provider to govern what users may do. (81967)
Widget Dashboard: Enforce the policy on the staging layer for every instance operation. (82256)
Widget Dashboard: Govern Reset to default through the policy. (82255)
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. fetch
Add unregister to remove a registered middleware. (82408)
Expose defaultFetchHandler so overrides can restore it. (82553)
api-fetch: Resolve to null for a 200 response with an empty body. (79325)
