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.
WordPress 6.4 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. 1 is September 27, 2023
@mukesh27 I’ve been working on issue #22192 and have received some feedback related to backward compatibility on the PR. I’m now in need of feedback from Joe and Felix
@thekt12#58196 in progress, planning to give for initial review tomorrow
@joemcgill I made good progress on #57789 yesterday and could use a second set of eyes. It doesn’t full solve the issue of making Theme.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. data persistent, but is a step in that direction, which reduces unnecessary recalculation of that data during a page load. I’m going to work on a parallel PR to the 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/ repo to get some testing of the strategy in 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 prior to making the change in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
@spacedmonkey It is unclear of the path forward of #59188 there seems to be disagreement on best path forward
@mukesh27 The majority of the work from my end has already been committed for the 6.4 milestone. I am now providing support to Jonny for the review and testing process.
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/. & CSSCSSCascading Style Sheets.
@westonruter Similarly, I have the elimination of manual script 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.) construction scope reduced to not include the adminadmin(and super admin). Now it is just the frontend and the login screen. PR ready for review. https://github.com/WordPress/wordpress-develop/pull/4773
@flixos90 Otherwise, reviewing the PRs for #58892 and #58893 which I see have received updates since, so I’ll take another look shortly after this chat
@flixos90 Last week I spent some time conducting field analyses to assess the performance impact of the WordPress 6.3 release. Primarily focusing on Web Vitals metric LCP which measures load time performance, and how it’s affected both in general, but also specifically by the two major enhancements that were projected to affect LCP:
the emoji loader script optimizations
the lazy-loading plus fetchpriority improvements
Sharing the most important highlights:
Overall, the Largest Contentful Paint (LCP) passing rate has improved by 5.6% for classic theme sites and by 2.7% for 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. theme sites
The Largest Contentful Paint (LCP) boost for classic theme sites using the emoji loader script is 3.4% to 7% higher than for those that don’t use it, and for block themes it’s 0.7% to 4.5% better as well
When looking at only the sites where that is the case and which were still lazy-loading the LCP image with WordPress 6.2, the LCP performance impact amounts to a massive 16% to 21% improvement for mobile viewports and 6% to 9% on desktop.
Lazy-loading accuracy has notably improved: In WordPress 6.3, only 9-10% of sites still lazy-load their LCP image for classic theme sites (down from 27-28% in 6.2) while for block theme sites it’s 5-8% (down from 17-29% in 6.2)
@joemcgill I wanted to mention that we should probably prepare some time after beta1 next week for some initial triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. of any performance issues we see after the first round of code syncing from the Gutenberg project has occurred.
@spacedmonkey I would like to start a tracking ticket for 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. this team is going to work on
Created https://github.com/WordPress/performance/issues/840 for tracking 6.4 Trac tickets that require dev notes
Here is the agenda for this week’s performance team meeting scheduled for Sep 19, 2023 at 15:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.
WordPress 6.4 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. 1 is September 27, 2023
At a high level, we will go through quick intros (what each person does/focuses on) before reviewing WordPress 6.3 performance impact in the field, diving into WordPress 6.4 performance improvements and looking ahead at what can be learned for WordPress 6.5.
As a reminder, hallway hangouts are meant to be casual and collaborative so come prepared with a kind, curious mind along with any questions or items you want to discuss around this important area of the project, especially since the agenda is intentionally loose to allow for it.
I’ve been working on refactoring how the block toolbar is semantically communicated in the DOM by moving it to render in 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., rather than within the editor canvas.
The is a PR as a proof of concept. It is not ready to really be reviewed but is useful for seeing the direction it’s going
Registering Variations for Posts terms and Nav 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.
@gaambo mentioned two issues they’d wish for some feedback and/or help with:
@webcommsat highlighted there were opportunities for contributors to put forward topic ideas and write for the Developer Blog or contribute to one of the approved topic submissions.
The post explores the latest updates to the Command Palette, a new tool available with WordPress 6.3 designed to speed up your workflow. It also gives a preview of highlights in creation experience coming in 6.4.
The FSE Outreach Program will become a focused space for solving issues, creating resources, and facilitating conversations around Phase 2 adoption. You can contribute by commenting on this post.
After 6.4 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. 1, the facilitated calls for FSE testing will be replaced by ad hoc calls for testing run by the Make Test team or contributors who need specific features tested.
Through greater focus on the unique needs of different user groups, Learn.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/ aims to create a more intuitive and effective learning environment.
The latest discussion focuses on how the resource can move towards consolidating the current content type offerings from courses, tutorials, and lesson plans to courses and lessons.
Deadline for feedback: Friday, September 15, 2023.
This came from an informal discussions at the Community Summit.
Two parts of this proposal: to move earlier the date of the Field GuideField guideThe field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. publication by one week to the final Beta, and to create and publish a simplified Field Guide on the Dev Blog.
Beta 1 is 2.5 weeks away on Sept 26, 2023 as this is a short release cycle. The next triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions will focus on brainstorming the remaining tickets to identify if they can be moved forward. A call to participate in the 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. scrubs was made by @oglekler and @webcommsat. Also, the scrubs are a great tool to review asynchronously to learn about the WordPress development process and identify ways to get involved.
Project Board for Editor Tasks for WordPress 6.4 on 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 be the repository owner. https://github.com/
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/
Gutenberg 16.7 RC1 on September 20, 2023 (originally planned on September 13)
This will be the general cut-off date for new features developed in 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, except tasks blessed in TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..
WordPress 6.4 Beta 1 on September 26, 2023
Except for the blessed tasks, only fixes can be included after this date.
Gutenberg 16.7 on September 27, 2023
Components & Tickets
The following tickets were raised by @afragen for feedback.
Core Trac #58281: Rollback Auto-Update (Rollback part 3)
Core Trac #22316: Plugin Dependencies (Yet Another Plugin Dependencies TicketticketCreated for both bug reports and feature development on the bug tracker.)
An update regarding the latest 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. proposal for WordPress core was raised by @sc0ttkclark
A first post-WCUS meeting was held on Fields API on September 13. It had a great discussion on the Fields API V1 proposal.
From this discussion, further confirmation from contributors and others who are interested in the project is wanted. A survey/vote on what the meeting wanted and did not want include in the V1 proposal was created.
The survey has been opened up to anyone interested in the Fields API. The survey closing date was extended following feedback in Dev Chat. Deadline: survey closes at September 20, 2023 at 17:00 UTC. Survey link to vote.
Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel or message @webcommsat, one of the Core Team reps, in the week before the meeting.
Core Editor improvement – commanding the command palette posted by @annezazu. The post explores the latest updates to the Command Palette, a new tool available with WordPress 6.3 designed to speed up your workflow. It also gives a preview of highlights in creation experience coming in 6.4.
The FSE Outreach Program will become a focused space for solving issues, creating resources, and facilitating conversations around Phase 2 adoption. You can contribute by commenting on this post.
After 6.4 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. 1, the facilitated calls for FSE testing will be replaced by ad hoc calls for testing run by the Make Test team or contributors who need specific features tested.
Deadline: share feedback by September 22, 2023
Final call: Feedback on the Learning Pathways outline from Training team from CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. is invited. Through greater focus on the unique needs of different user groups, Learn.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/ aims to create a more intuitive and effective learning environment. The latest discussion focuses on how the resource can move towards consolidating the current content type offerings from courses, tutorials, and lesson plans to courses and lessons. Deadline for feedback: Friday, September 15, 2023.
Reminder: Proposal for an update to the Field Guide accompanying a releasefrom some of the informal discussions at the Community Summit. There are two parts of this proposal: to move earlier the date of the Field GuideField guideThe field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. publication by one week to the final Beta, and to create and publish a simplified Field Guide on the Dev Blog. Deadline for feedback: September 15, 2023.
Project Board for Editor Tasks for WordPress 6.4 on 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 be the repository owner. https://github.com/
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/
Gutenberg 16.7 RC1 on September 20, 2023 (originally planned on September 13)
This will be the general cut-off date for new features developed in 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, except tasks blessed in TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..
WordPress 6.4 Beta 1 on September 26, 2023
Except for the blessed tasks, only fixes can be included after this date.
Gutenberg 16.7 on September 27, 2023
Tickets or Components help requests
Please add any items for this part of the agenda to the comments. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticketCreated for both bug reports and feature development on the bug tracker. if needed.
Open floor
If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.
A Week in Core – September 4, 2023 – Props to @audrasjb for pulling this together! Changes on TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between August 21 and September 4, 2023:
An overview of updates in Trac between August 21 and September 4, 2023:
75 commits
150 contributors
25 new contributors
129 tickets created
13 tickets reopened
117 tickets closed
Call for testing of Performant Translations > I18N Performance Analysis: Testing of a dedicated 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 as a solution for an issue discovered where localized WordPress sites load significantly slower than a site without translations, found in an in-depth i18n performance analysis.
Proposal: An update to the Field Guide: From some of the informal discussions at the Community Summit. There are two parts of this proposal: to move earlier the date of the Field GuideField guideThe field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. publication by one week to the final 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., and to create and publish a simplified Field Guide on the Dev Blogblog(versus network, site). Deadline for feedback: Sept 15th.
WordPress 6.4 Alpha 1 is underway: Beta 1 is due on September 25, 2023
Stay in the 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. with 6.4 by checking out:
The 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. scrub schedule will take place in core on the dates in this post. All are welcome to join the scrub!
Components & Tickets
6.4 Alpha dev has been underway since 18(ish) July. The window for early is closing soon. Contributors’ help is requested for testing and feedback on these tickets to help move them forward to hopefully land in 6.4.
Tickets that were raised:
CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Trac #59187: Bundled Themes need to be update to node 16 – Check out the Slack discussion for more info as it was raised by @mikestraw
Core Trac #56780: ShortcodeShortcodeA shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site.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. in block-based template part in a classic theme does not get expanded – More eyes were requested by @petitphp. Please check the Slack discussion for more information.
@flixos90 I left a comment on https://core.trac.wordpress.org/ticket/55996#comment:39 yesterday that I would like to get other people’s thoughts on. Revisiting that ticketticketCreated for both bug reports and feature development on the bug tracker., I’m not sure the original direction is really where we want to go
@spacedmonkey Code reviewed the draft PR. The biggest issue is the name of the 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. as that is already used
@flixos90 I also implemented two proof of concept PRs with alternative ways to address some of the related problems
@joemcgill Last week, I updated the overview ticket we had in the performance repo for improving template loading and created two new tickets, #59314 and #59315 related to that work. Right now, our team has a lot already in progress for the 6.4 milestone, and with it being a shorter release cycle, I’ve moved those two tickets to future release, but would like to prioritize them earlier. If anyone ends up having capacity to work on them during this milestone, I think we could consider moving them in.
@joemcgill I’m planning on taking another swing at #57789 this week, with the intent to try to make the changes in the 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/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 prior to getting them into coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., as discussed originally with @oandregal
@spacedmonkey I am worried about making that cache persistant. It hard to know when the theme.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 has been updated? What if someone ftp updates the file? A lot of the WordPress code base guess that files could change. But many hosts lock this down, like VIP GO. I wonder if we could have a new flag to say that files cannot be updated
@joemcgill That’s part of what needs to be solved. There are several cache invalidation issues that need to be addressed, but honestly, the FTPFTPFTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients. use case is a lower concern for me so long as any persistence is flushable. I think anyone who is manually updating files is already needing to run cache flushes as a part of their workflow at times.
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/. & CSSCSSCascading Style Sheets.
@10upsimon No updates from my side on this one at present, but I do wonder if we need to exercise due diligence and reach out to some of the larger orgs like WP Engine around “bad” docs on deferred/async script implementation especially as it will break fully once we solve the manual construction of script tags. Specifically, this documentation page: https://wpengine.com/resources/defer-parsing-javascript-wordpress/
@westonruter To this end, the PR for elimination of manual construction of script tags needs feedback. Ticket: https://core.trac.wordpress.org/ticket/58664 I’m thinking the scope should be reduced to just the frontend, leaving the adminadmin(and super admin) for a future release
as for https://core.trac.wordpress.org/ticket/58893 I did open a PR and there’s some feedback already. But I haven’t had the chance to 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. back.
@joemcgill Pascal recently updated the Performance workflow to show the relative change of a specific PR compared with the 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., which will show in the action summary. (example)
I think there’s still some room for us to improve the understandability and accuracy of those tables, but this is a much easier way to spot performance issues at a glance on PRs. Should be really helpful for reviewers
@10upsimon Arrived at a working UIUIUser interface for managing standalone plugins within the WPP settings screen
Transitioning to issues related to the migrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. aspect, i.e raising correct admin notices, enhancing the UI within the WPP settings screen to be more indicative of what current active modules have standalone plugins that should be activated instead, and so on.
@flixos90 Regarding the second point, not sure at what stage that exploration is at, but I think it would be great for the first PR to be only about the general UI, without the migration aspects, to limit scope
Open Floor
Agreed to focus tomorrows Bug Scrub on 6.4 tickets without an owner
Here is the agenda for this week’s performance team meeting scheduled for Sep 12, 2023 at 15:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.
These “CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvementtagtagA 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 a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects.
The following dives deep into the latest updates to the Command Palette, a new tool available with WordPress 6.3 designed to speed up your workflow. With work underway for WordPress 6.4, here are some very early looks at what you can look forward to when it comes to this new option in your WordPress creation experience and a reminder of what it’s capable of already.
Use commands to do more, faster in any editor
The Command Palette is available across the editing experience, whether you’re switching between templates in the Site Editor or toggling open settings in the Post Editor, with specific contextual options depending on where you are. In the video below, you’ll see the keyboard shortcut used to evoke the Command Palette, open and close List View, display and hide breadcrumbs, toggle on distraction free mode, and preview the page in a new tab.
Think of the Command Palette as the ultimate shortcut tool, allowing you to do more with less clicks, whether you’re trying to enable a specific setting or transform an Image 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. to a Cover block.
Explore every option
If you’re using WordPress 6.3, the following commands are ready to use to allow you to quickly switch between different parts of your site and personalize your experience without needing to find every setting individually:
Edit Template when editing a page.
Back to page to return to editing a page from a template.
Reset template
Reset template part
Reset styles to default
Delete template
Delete template part
Toggle 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.
Toggle block inspector
Toggle spotlight mode
Toggle top toolbar
Open code editor
Toggle list view in the Post Editor.
Toggle fullscreen mode
Open editor preferences
Open keyboard shortcuts
Customize CSSCSSCascading Style Sheets.
Open styles 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.
Open styles
Learn about styles to trigger the welcome guide for Styles
Additionally, you can access all transforms a block has defined using the Command Palette. For example, with an Image block, you will see the option to transform to a Cover block, a Gallery block, Columns block, File block, Group block, and Media & Text block. Finally, for the various reset, delete, and edit commands related to templates, the name of the template has been added to ensure you’re taking the actions you want on the exact item you want.
What commands do you want to see? Please share in Gutenberg’s GitHub repository or in the comments below to help make this feature even more powerful.
Enjoy a refreshed design and experience
To better accommodate a growing number of commands and make it easier to skim what each option allows, new styling was added that includes darker icons and an always present search icon. Below is an image showing the design before on the left and the current design on the right:
Thanks to a recent fix, this new design looks great on all screen sizes. Work has also been done to ensure that the commands that are listed are most applicable to the context at hand. For example, if a block is locked, grouping is no longer listed as a command, resulting in a more intuitive experience. For a bonus quality of life detail, the keyboard shortcut is also displayed when in site view in the Site Editor when you hover over the search icon.
Add your own commands (with or without an icon)
The Command Palette is an excellent option for extenders to seamlessly add commands related to their specific plugins. For instructions on how to do this, check out the dev note introducing this feature. Of note, with a recent change, the requirement of having an icon has been dropped as well with a discussion underway around how best to identify third party commands.
Thank you to @richtabor for creating the visuals used in this post.
You must be logged in to post a comment.