Title: 2021 – Page 24 – Make WordPress Core --- # Yearly Archives: 2021 [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 9:52 pm _on_ July 27, 2021 Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [core ( 743 )](https://make.wordpress.org/core/tag/core/), [dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/)    # 󠀁[Dev Chat Agenda for July 28, 2021](https://make.wordpress.org/core/2021/07/27/dev-chat-agenda-for-july-28-2021/)󠁿 Here is the agenda for this week’s developer meeting to occur at [July 28, 2021 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210728T2000). ## Blogblog (versus network, site) Post Highlights * [A Week in Core – July 26, 2021](https://make.wordpress.org/core/2021/07/26/a-week-in-core-july-26-2021/) * [CSS](https://make.wordpress.org/core/2021/07/27/css-chat-summary-22-july-2021/) and [Editor](https://make.wordpress.org/core/2021/07/21/editor-chat-summary-21-july-2021-2/) chat summaries * [[Request for feedback] Updater Proof of Concept](https://make.wordpress.org/core/2021/07/21/request-for-feedback-updater-proof-of-concept/) * [Refining WordPress core’s lazy-loading implementation](https://make.wordpress.org/core/2021/07/15/refining-wordpress-cores-lazy-loading-implementation/) ## 󠀁[5.8 Review](https://make.wordpress.org/core/5-8/)󠁿 * **[5.8 “Tatum”](https://wordpress.org/news/2021/07/tatum/) final release all completed! 🎉** * Remaining tasks from [Releasing Major Versions handbook](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-major-versions/): - ~Run the DocBlocks parser for [DevHub](https://www.google.com/url?q=https://developer.wordpress.org/reference/&sa=D&source=calendar&ust=1627240643202000&usg=AOvVaw3m6TggAzgzRsF8v6AzLblQ) ~ ✅ - ~Update [wordpress.org/support/article/history](https://www.google.com/url?q=https://wordpress.org/support/article/history/&sa=D&source=calendar&ust=1627240643202000&usg=AOvVaw2ep3G_iFCqveLPq8gVjB8b) ~ ✅ - Publish a retrospective post if desired. - Check in with the [Support Team](https://www.google.com/url?q=https://make.wordpress.org/support/&sa=D&source=calendar&ust=1627240643202000&usg=AOvVaw1gJ_0QcTZ63kL5WBgpyTwH) for any notable issues. - Check in with the [Community Team](https://www.google.com/url?q=https://make.wordpress.org/community/&sa=D&source=calendar&ust=1627240643202000&usg=AOvVaw3cl_dY0FjZo7JwbrY0-pyN) for any community feedback. - Kick off the next cycle, [5.9](https://make.wordpress.org/core/5-9/), with the next lead. ## Components check-in and status updates * Check-in with each component for status updates. * Poll for components that need assistance. ## Open Floor Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above? Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly. This meeting happens in the [#core](https://wordpress.slack.com/messages/C02RQBWTW) channel. To join the meeting, you’ll need an account on the [Making WordPress Slack](https://make.wordpress.org/chat/). [#5-8](https://make.wordpress.org/core/tag/5-8/), [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core](https://make.wordpress.org/core/tag/core/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/) 9:33 pm _on_ July 27, 2021 Tags: [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[CSS Chat Summary: 15 July 2021](https://make.wordpress.org/core/2021/07/27/css-chat-summary-15-july-2021/)󠁿 [The meeting took place here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1626383011146400). [@notlaura](https://profiles.wordpress.org/notlaura/) facilitated and [@danfarrow](https://profiles.wordpress.org/danfarrow/) wrote up these notes. ## Housekeeping * [@notlaura](https://profiles.wordpress.org/notlaura/) wondered how we could encourage participation at the chats, and get more help with the Custom Properties project. She suggested maybe some guidelines on how to get started contributing * [@danfarrow](https://profiles.wordpress.org/danfarrow/) offered to add some notes to [the shared document](https://docs.google.com/document/d/1Z0Wo1W0ZQwFJYPcJ8GlsubA9uKhcFdT8ifYnso82z9I/edit#) * [@notlaura](https://profiles.wordpress.org/notlaura/) also suggested a “Call for CSSCSS Cascading Style Sheets. contributors” Make post linking to the shared document and offered to work on writing that ## Custom Properties (󠀁[#49930](https://core.trac.wordpress.org/ticket/49930)󠁿) * [@notlaura](https://profiles.wordpress.org/notlaura/) suggested spending some time working individually on the project which is something we’ve tried at previous meetings with great success _20 minutes later…_ * [@notlaura](https://profiles.wordpress.org/notlaura/) used the time to [write a draft](https://docs.google.com/document/d/1gnLJ1upGfP1BVyQJAFAOZGldNqyH2U6x7ZzQdd2m2cQ/edit#heading=h.s12ezm5j8yh) of the previously mentioned Make post * [@danfarrow](https://profiles.wordpress.org/danfarrow/) started updating `forms. css` noting that some custom properties have a longer ancestry e.g. `--wp-admin-- button--text` takes its value from `--wp-admin--button-primary`, which in turn takes its value from `--wp-admin--theme--primary`. He speculated that tooling could make it easier to traverse & understand this hierarchy ## CSS Link Share / Open Floor * [@notlaura](https://profiles.wordpress.org/notlaura/) shared a link to an interesting looking research paper [Understanding Learning Curves and Trajectories in CSS Layout](https://dl.acm.org/doi/pdf/10.1145/3287324.3287387) Thanks everyone! [#core-css](https://make.wordpress.org/core/tag/core-css/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 10:24 pm _on_ July 26, 2021 Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)    # 󠀁[A Week in Core – July 26, 2021](https://make.wordpress.org/core/2021/07/26/a-week-in-core-july-26-2021/)󠁿 Welcome back to a new issue of _Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress._. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between July 19 and July 26, 2021. * 24 commits * 23 contributors * 103 tickets created * 18 tickets reopened * 68 tickets closed Please note that as expected, WordPress 5.8 was released last week, on Tuesday July 20, 2021 🌟 Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the [Trac timeline for the period above](https://core.trac.wordpress.org/timeline?from=07%2F26%2F2021&daysback=7&authors=&ticket=on&changeset=on&repo-=on&repo-design=on&repo-tests=on&sfp_email=&sfph_mail=&update=Update). The following is a summary of commits, organized by component and/or focus. ## Code changes ### Build/Test Tools * Rename classes in `phpunit/tests/widgets/` per the naming conventions – [#53363](https://core.trac.wordpress.org/ticket/53363) * Rename classes in `phpunit/tests/sitemaps/` per the naming conventions – [#53363](https://core.trac.wordpress.org/ticket/53363) * Rename classes in `phpunit/tests/blocks/` per the naming conventions – [#53363](https://core.trac.wordpress.org/ticket/53363) * Move and fix incorrectly placed tests for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. supported styles – [#53363](https://core.trac.wordpress.org/ticket/53363) * Use better assertions in `WP_UnitTestCase_Base::assertEqualFields()`: – [#53363](https://core.trac.wordpress.org/ticket/53363) * Modernize the `WP_UnitTestCase_Base::assertEqualFields()` method: – [#53363](https://core.trac.wordpress.org/ticket/53363) * Correct placement of the `$message` parameter in `assertDiscardWhitespace()` – [#53363](https://core.trac.wordpress.org/ticket/53363) * Add a `$message` parameter for custom assertions in `WP_UnitTestCase_Base` – [#53363](https://core.trac.wordpress.org/ticket/53363) * Correct class name for `WP_Filesystem_Base::find_folder()` tests – [#53363](https://core.trac.wordpress.org/ticket/53363) * Update PHP_CodeSniffer to version 3.6.0 – [#53477](https://core.trac.wordpress.org/ticket/53477) ### Bundled Themes * Version Bump 2010, 2011 and 2012 – [#53777](https://core.trac.wordpress.org/ticket/53777) * Bundled Themes: Use correct path for loading images in block patterns – [#53769](https://core.trac.wordpress.org/ticket/53769) * Twenty Ten: Use correct path for loading block patterns – [#53752](https://core.trac.wordpress.org/ticket/53752) ### Media * Check the `posts_per_page` value in `wp_ajax_query_attachments()` before using it as a divisor – [#53773](https://core.trac.wordpress.org/ticket/53773) * Media: Remove unused code from `wp-admin/includes/media.php` – [#53764](https://core.trac.wordpress.org/ticket/53764) ### Documentation * Miscellaneous docblockdocblock (phpdoc, xref, inline docs) corrections and improvements– [#53399](https://core.trac.wordpress.org/ticket/53399) * Add a comment about the `$title` global usage in various adminadmin (and super admin) files – [#53729](https://core.trac.wordpress.org/ticket/53729) * Correct a comment about WebP constants in `wp-includes/compat.php` – [#53680](https://core.trac.wordpress.org/ticket/53680) ### Help/About * Add `/` character to `img` and `source` tags – [#53716](https://core.trac.wordpress.org/ticket/53716) ### Internationalization * Fix broken loopLoop The 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](https://codex.wordpress.org/The_Loop) in WP_Theme_JSON_Resolver ### Editor * Conditionally load registered styles for block variations – [#53616](https://core.trac.wordpress.org/ticket/53616) ### External Libraries * Correct the `underscore` version used when registering – [#53713](https://core.trac.wordpress.org/ticket/53713) * Correct the `jquery-form` version used when registering – [#53714](https://core.trac.wordpress.org/ticket/53714) * Correct the `hoverIntent` version used when registering – [#53715](https://core.trac.wordpress.org/ticket/53715) ## Props **Thanks to the 23 people who contributed to WordPress Core on Trac last week:** [@jrf](https://profiles.wordpress.org/jrf/) (5), [@audrasjb](https://profiles.wordpress.org/audrasjb/)( 4), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) (3), [@david](https://profiles.wordpress.org/david/). binda (3), [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/) (2), [@aristath](https://profiles.wordpress.org/aristath/) (2), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 1), [@schlessera](https://profiles.wordpress.org/schlessera/) (1), [@TobiasBg](https://profiles.wordpress.org/tobiasbg/)( 1), [@ankitmaru](https://profiles.wordpress.org/ankitmaru/) (1), [@radixweb](https://profiles.wordpress.org/radixweb/)( 1), [@rtm909](https://profiles.wordpress.org/rtm909/) (1), [@GaryJ](https://profiles.wordpress.org/garyj/)( 1), [@dd32](https://profiles.wordpress.org/dd32/) (1), [@ravipatel](https://profiles.wordpress.org/ravipatel/)( 1), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (1), [@loranrendel](https://profiles.wordpress.org/loranrendel/)( 1), [@ryelle](https://profiles.wordpress.org/ryelle/) (1), [@rudlinkon](https://profiles.wordpress.org/rudlinkon/)( 1), [@youknowriad](https://profiles.wordpress.org/youknowriad/) (1), [@kapilpaul](https://profiles.wordpress.org/kapilpaul/)( 1), [@2linctools](https://profiles.wordpress.org/2linctools/) (1), and [@johnbillion](https://profiles.wordpress.org/johnbillion/)( 1). **Congrats and welcome to our 5 new contributors of the week! **[@radixweb](https://profiles.wordpress.org/radixweb/), [@rtm909](https://profiles.wordpress.org/rtm909/), [@loranrendel](https://profiles.wordpress.org/loranrendel/), [@rudlinkon](https://profiles.wordpress.org/rudlinkon/), and [@2linctools](https://profiles.wordpress.org/2linctools/) ♥️ **Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 17), [@desrosj](https://profiles.wordpress.org/desrosj/) (3), [@gziolo](https://profiles.wordpress.org/gziolo/)( 2), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (1), and [@johnbillion](https://profiles.wordpress.org/johnbillion/)( 1). [#5-8](https://make.wordpress.org/core/tag/5-8/), [#week-in-core](https://make.wordpress.org/core/tag/week-in-core/) [ ](https://profiles.wordpress.org/ajitbohra/) [Ajit Bohra](https://profiles.wordpress.org/ajitbohra/) 8:18 pm _on_ July 26, 2021 Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-agenda ( 189 )](https://make.wordpress.org/core/tag/core-editor-agenda/), [meetings ( 14 )](https://make.wordpress.org/core/tag/meetings/)    # 󠀁[Editor Chat Agenda: 28 July 2021](https://make.wordpress.org/core/2021/07/26/editor-chat-agenda-28-july-2021/)󠁿 Facilitator and notetaker @ajitbohra This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, 28 Jul](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210728T1400) [y 2021, 14:00 UT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210728T1400) [C](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201104T1400). This meeting is held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). * [WordPress 5.8](https://wordpress.org/news/2021/07/tatum/) * [What’s new in Gutenberg 11.1.0](https://make.wordpress.org/core/2021/07/21/whats-new-in-gutenberg-11-1-0-21-july/) * GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) 11.2.0 RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/2021/page/24/?output_format=md#alpha-beta). * [Whats next in Gutenberg: July and August.](https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/) * [Project updates based on the latest site editing scope](https://github.com/WordPress/gutenberg/issues/33094): - BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. based WidgetWidget A 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. Editor. - Navigation Block & Navigation Editor. - Template editor. - Patterns. - Styling. - Mobile Team. * Task Coordination. * Open Floor. **Even if you can’t make the meeting, you’re encouraged to share anything relevant for the meeting in the comments below:** * If you have anything to share for the Task Coordination section, please leave it as a comment on this post. * If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below. [#core-editor](https://make.wordpress.org/core/tag/core-editor/) [#core-editor-agenda](https://make.wordpress.org/core/tag/core-editor-agenda/) [#agenda](https://make.wordpress.org/core/tag/agenda/) [#meetings](https://make.wordpress.org/core/tag/meetings/) [ ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/) 2:52 pm _on_ July 24, 2021 Tags: [core ( 743 )](https://make.wordpress.org/core/tag/core/), [dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Dev Chat Summary: July 21, 2021](https://make.wordpress.org/core/2021/07/24/dev-chat-summary-july-21-2021/)󠁿 @desroj led the weekly meeting at 20:00 UTC. [Here is the meeting agenda](https://make.wordpress.org/core/2021/07/20/dev-chat-agenda-for-july-21-2021/). [Link to 20:00 UTC in #core on Making WordPress Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1626897606173300) ## Notable news and blogblog (versus network, site) posts [WordPress 5.8 was released yesterday](https://wordpress.org/news/2021/07/tatum/)( July 20, 2021)! The new release was downloaded 7.7 million times in a little over 24 hours. [What’s next in Gutenberg?](https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/) [What’s new in Gutenberg 11.1.0?](https://make.wordpress.org/core/2021/07/21/whats-new-in-gutenberg-11-1-0-21-july/) ## Requests for Feedback * [Refining WordPress Core’s lazy-loading implementation](https://make.wordpress.org/core/2021/07/15/refining-wordpress-cores-lazy-loading-implementation/) * [Updater Proof-of-Concept](https://make.wordpress.org/core/2021/07/21/request-for-feedback-updater-proof-of-concept/) * [Changes to the Theme Directory requirements](https://make.wordpress.org/themes/2021/07/20/discussion-request-for-feedback-on-requirement-changes/) * [What is your favorite feature in WordPress 5.8?](https://docs.google.com/document/d/1nAHgf4ou2tTtX8L5l_HnqnuU8KrZeYm7LJhkc8LEzts/edit) ## Component Team Updates ### Build/Test Tools * Ongoing modernization of PHPUnit tests. [#53363](https://core.trac.wordpress.org/ticket/53363) * PHP_CodeSniffer updated to 3.6 (with PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8 support) [#53477](https://core.trac.wordpress.org/ticket/53477) ### Auto-Updates * Request for feedback on [Updater Proof-of-Concept ](https://make.wordpress.org/core/2021/07/21/request-for-feedback-updater-proof-of-concept/) ### Themes * Request for feedback on [changes to the Theme Directory requirements](https://make.wordpress.org/themes/2021/07/20/discussion-request-for-feedback-on-requirement-changes/) ## Open Floor * @desroj highlighted [a bug](https://core.trac.wordpress.org/ticket/52241) in the Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also **network**, **blog**, **site** Filesystem APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. that was requested to be prioritized in 5.9. * [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) raised [a discussion about Making WordPress Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1626899450214800)— what we can/should use it for. _Should [#core](https://make.wordpress.org/core/tag/core/) be the default channel? Should some other SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel be created to greet new users (who may or may not have context entering Slack that it is mostly a working environment)?_ This was a lively discussion, please add more thoughts in the comments below! * While it’s been a fairly quiet (some might say _too quiet_) and smooth release, [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) encouraged the hosting (and greater) community to check-in with support folks and report back any trends. [@johnbillion](https://profiles.wordpress.org/johnbillion/) also noted a handful of tickets about Widgets have been opened related to “widgetWidget A 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. customisation and logic plugins.” ## Watch For * WordPress 5.8 release reflection and retrospective. * New episodes of the [WordPress Briefing](https://wordpress.org/news/podcast/). * Our next [Weekly Developer Chat](https://make.wordpress.org/core/weekly-developer-chats/) is Wednesday, July 28 at 20:00 UTC. _Interested in volunteering for upcoming WordPress releases_? _Please comment below and team reps will reach out!_ _Props to [@dryanpress](https://profiles.wordpress.org/dryanpress/) for taking these [#summary](https://make.wordpress.org/core/tag/summary/) notes!_ [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/) 2:57 pm _on_ July 22, 2021 Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/)    # 󠀁[CSS Chat Agenda: July 22, 2021](https://make.wordpress.org/core/2021/07/22/css-chat-agenda-july-22-2021/)󠁿 This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday July 22 at 21:00PM UTC. The meeting will be held in the [#core-css](https://make.wordpress.org/core/tag/core-css/) channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). * **Housekeeping** * **Custom Properties** ([#49930](https://core.trac.wordpress.org/ticket/49930)) - Discussion as needed - Work time * **Open Floor + CSS Link Share** If there’s any topic you’d like to discuss, please leave a comment below! [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core-css](https://make.wordpress.org/core/tag/core-css/) [ ](https://profiles.wordpress.org/andraganescu/) [Andrei Draganescu](https://profiles.wordpress.org/andraganescu/) 5:30 pm _on_ July 21, 2021 Tags: [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-summary ( 185 )](https://make.wordpress.org/core/tag/core-editor-summary/) # 󠀁[Editor chat summary: 21 July, 2021](https://make.wordpress.org/core/2021/07/21/editor-chat-summary-21-july-2021-2/)󠁿 This post summarizes the weekly editor chat meeting ([agenda here](https://make.wordpress.org/core/2021/07/20/editor-chat-agenda-21-july-2021/)) held on [ Wednesday, July 21, 2021, 02:00PM UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210721T1400) on [Slack](https://wordpress.slack.com/archives/C02QB2JS7/p1626876061386100). Moderated by [@andraganescu](https://profiles.wordpress.org/andraganescu/). ## Announcements * [WordPress 5.8 is out!](https://wordpress.org/news/2021/07/tatum/) Lots of thanks to everyone for their hard work!  * [[[Gutenberg 11.1](https://github.com/WordPress/gutenberg/releases/tag/v11.1.0) was released and so [What’s new in Gutenberg 11.1.0](https://make.wordpress.org/core/2021/07/21/whats-new-in-gutenberg-11-1-0-21-july/) was posted today. Check it out for news about the new GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https:/ /wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) release. * Curious about what’s coming? Go read [What’s next in Gutenberg? Site Editing status check (Late July-August 2021)](https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/) and keep an eye on the [updated FSE scope issue](https://github.com/WordPress/gutenberg/issues/33094). ## Monthly Priorities & Key Project Updates **BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. based WidgetWidget A 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. Editor** As the project has landed in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., there is now [a new tracking issue](https://github.com/WordPress/gutenberg/issues/33242) set up for things identified by the community as great follow up work to improve on it. **Mobile Team** * _Shipping_: Block picker search and first iteration of the embed block will be shipping in the next release. * _In Progress_: Scoping the next phase of Global Style Support work focusing on text-related styles. ## Task Coordination [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) * Landed `SegmentedControl` ([PR: 31937](https://github.com/WordPress/gutenberg/pull/31937)) * I’m working on porting some more components from g2 and will make explorations for more layout integrations. Related Riad’s PR ([PR: 33359](https://github.com/WordPress/gutenberg/pull/33359)) @torounit * I am working on refactoring HierarchicalTermSelector ([PR: 33418](https://github.com/WordPress/gutenberg/pull/33418)) [@zieladam](https://profiles.wordpress.org/zieladam/) * Kept an eye open on the .org widgets channel, explored issues like[ ](https://github.com/WordPress/gutenberg/issues/33462)` is_admin()`[ being false in our API endpoints](https://github.com/WordPress/gutenberg/issues/33462) or [admin functions not being loaded at all](https://github.com/WordPress/gutenberg/pull/33454#discussion_r670457039), proposed a bunch of PRs to address these. * I surfaced the widgets editor problem with [414 too long request uris](https://github.com/WordPress/gutenberg/issues/33540) on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/). * Debugged and fixed a non-deterministic [Block moves to inactive widgets after being saved](https://github.com/WordPress/gutenberg/issues/33335) issue. * Proposed a few small PRs to other small problems, [Issue 33336](https://github.com/WordPress/gutenberg/issues/33336), [Ticket 53679](https://core.trac.wordpress.org/ticket/53679), and more. [@mamaduka](https://profiles.wordpress.org/mamaduka/) * Started refactoring `FlatTermSelector` into a [functional component](https://github.com/WordPress/gutenberg/pull/33459) and utilize core data module for fetching terms. * While working on this discovered a few minor issues with the “Most Used Terms” component, which should be fixed now. * Also, now users with author roles should be able to [set featured images](https://github.com/WordPress/gutenberg/pull/33567) uploaded by other users. [@aristath](https://profiles.wordpress.org/aristath/) * Autogenerate headings anchors – [PR: 30825](https://github.com/WordPress/gutenberg/pull/30825). * Allow enqueing multiple stylesheets per-block – [PR: 32510](https://github.com/WordPress/gutenberg/pull/32510). [@getdave](https://profiles.wordpress.org/getdave/) * I improved the build tooling by automatically grouping changelog items by feature when it is build on CI [PR: 33229](https://github.com/WordPress/gutenberg/pull/33229/). [@ajlende](https://profiles.wordpress.org/ajlende/) * Cropping for the site logo needs reviewers [PR: 31607](https://github.com/WordPress/gutenberg/pull/31607). * Working on duotone enhancements we can discuss more during open floor [PR: 33466](https://github.com/WordPress/gutenberg/pull/33466). * Related bugbug A 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. fix for cover block spacing ui  [PR: 33560](https://github.com/WordPress/gutenberg/pull/33560). ## Open Floor A [test file](https://github.com/WordPress/wordpress-develop/blob/master/tests/phpunit/includes/testcase-block-supports.php) was added to WP Core in 5.6.0, but added incorrectly, which means that the tests effectively were never run. I’m trying to fix that, but am now finding that 7 out of the 20 tests are failing. Raised by [@jrf](https://profiles.wordpress.org/jrf/) We need someone with good knowledge of global styles to help figuring out if the test’s problem is on the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher or JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. side of the global styles. @torounit surfaced [issue 33589](https://github.com/WordPress/gutenberg/issues/33589) This is probably a bug introduced by the recent work on the “select all” behavior in the block editor. [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) surfaced a problem in [PR: 1483](https://github.com/WordPress/wordpress-develop/pull/1483) – It seems there will be the need for WP version check in patterns The problem lies that patterns can have blocks with shape that is not supported in a WP version, but themes are also checked against WP version that are compatible. This isn’t the same WP version usually. [@ajlende](https://profiles.wordpress.org/ajlende/) asked if more people think it might be beneficial to have [a system to that allow block supports to detect placeholder state](https://github.com/WordPress/gutenberg/pull/33466#issuecomment-881345461). General support for the idea was offered. [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) raised [PR: 32516](https://github.com/WordPress/gutenberg/pull/32516) and asked if [this direction](https://github.com/getsource/gutenberg/commit/29873db49be173e39955320973a50f41721985ef) is a good approach. Looking forward for feedback from folks who know the rich-text package and can provide advice. Does that seem along the right lines for a fix? [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/) [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 4:56 pm _on_ July 21, 2021 Tags: [updater ( 21 )](https://make.wordpress.org/core/tag/updater/) # 󠀁[[Request for feedback] Updater Proof of Concept](https://make.wordpress.org/core/2021/07/21/request-for-feedback-updater-proof-of-concept/)󠁿 Over the past month, [@aristath](https://profiles.wordpress.org/aristath/) and [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) have been working on a proof of concept to solve the two first outcomes highlighted in the [Updater Initiative scope post](https://make.wordpress.org/core/2021/05/03/feature-project-updates-on-updating-the-updaters/#comment-41272). They drew inspiration from the [https://wordpress.org/plugins/rollback-update-failure/](https://wordpress.org/plugins/rollback-update-failure/) pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress. org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. and tried to address a few tickets. They created a proof of concept that can be found in a draft PR on [https://github.com/WordPress/wordpress-develop/pull/1492/files](https://github.com/WordPress/wordpress-develop/pull/1492/files) and does the following: * Add new arguments to `hook_extra` passed by plugin and theme updates to ensure we can rollback to the correct version. * After a plugin/theme is successfully downloaded and extracted, the old plugin/ theme folder is moved to `wp-content/upgrade/rollback/plugins/PLUGIN` or ~`wp- content/upgrade/themes/THEME` ~`wp-content/upgrade/rollback/themes/THEME` _(thanks [Paul Bigai](https://profiles.wordpress.org/optimizewordpress/) for catching that)_ * If the plugin/theme was successfully installed, the backup of the previous version we kept in `wp-content/upgrade/rollback/` is deleted. * If the plugin/theme was not successfully installed, then we cleanup any remnants of files in `wp-content/plugins/PLUGIN` (or the corresponding folder for themes), and then we move the backup we kept in the rollbacks folder back to its original location. * Adds info in the site-health screen, to make sure the rollback folder is writable( or can be created if it doesn’t exist) That is the basic concept. The team ran some tests, helped by @peona as well and it seems to be working. The main difference with the `rollback-update-failure plugin` is that this solution moves the plugin/theme folders instead of zipping/unzipping them. This change should help to make the implementation a bit lighter/safer on shared hosts with limited resources. Before moving forward, I would like to ask the Upgrade/Install Maintainers to have a look at this and discuss together, in the comments of this post, if you agree with this change, if it works, etc… I am not setting a deadline for the comments, but ideally, I would like to be able to write a merge proposal for 5.9 so I will review the post in mid-~July~August _( thanks [@meher](https://profiles.wordpress.org/meher/) for pointing out that we are at the end of July already 😂)_ and nudge a bit more 😉 Thank you all for your help and feedback! _Thanks [@ipstenu](https://profiles.wordpress.org/ipstenu/) for the peer review_ [#updater](https://make.wordpress.org/core/tag/updater/) [ ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/) 1:04 pm _on_ July 21, 2021 Tags: [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [full-site editing ( 15 )](https://make.wordpress.org/core/tag/full-site-editing/), [gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-next ( 23 )](https://make.wordpress.org/core/tag/gutenberg-next/) # 󠀁[What’s next in Gutenberg? Site Editing status check (Late July-August 2021)](https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/)󠁿 [_WordPress 5.8 is already here_](https://wordpress.org/news/2021/07/tatum/)_, an exciting release marked by the inclusion of many Full Site Editing features that have been big-picture focuses in recent times. Because of this important achievement, in contrast to normal monthly updates, this post seeks to review the status of Full Site Editing and summarize the next high-level focuses within GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) Phase 2._ --- Full Site Editing is the lighthouse goal for phase 2 of Gutenberg. As such, it’s good to remember it is **a collection of projects** that allow site editing with blocks, bringing powerful capabilitiescapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). for a smooth editing experience. WordPress 5.8 includes some of these Full Site Editing projects and features; while some of them will continue as ongoing focuses for subsequent Gutenberg releases ( ⚒️), others can be considered stable and enter a maintenance phase (✅) Without further ado, let’s look at the current status of [the milestones](https://github.com/WordPress/gutenberg/issues/24551) that have guided Full Site Editing work in the last months and the updated scope for Site Editing**.** ⚒️ [**Updated scope for Site Editing projects**](https://github.com/WordPress/gutenberg/issues/33094) ⚒️ ### Site Editing Infrastructure and UIUI User interface The Site Editing Infrastructure and UI provide foundational work for the rest of FSE projects, mainly in the Site/Template Editor, Template parts, and the numerous APIs that support work around Full Site Editing. The first two iterations of the site editor milestone introduced editing blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes and all their template files. The ongoing third one offers the possibility of creating custom block templates in classic themes and is available in WordPress 5.8 for those themes that opt-in to the site editing experience. Work will continue to [finalize the Site Editor naming and placement](https://github.com/WordPress/gutenberg/issues/29630#issuecomment-811617222): the current Site Editor as we know it in the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. may evolve for better navigation flows and interactions. Thanks to feedback from different [FSE Outreach Program](https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/) testing rounds, the next focus for site experience and tooling improvement include: * [Template previewing](https://github.com/WordPress/gutenberg/issues/27847) * [Browse mode](https://github.com/WordPress/gutenberg/issues/23328) * [Mosaic view for theme Templates](https://github.com/WordPress/gutenberg/issues/20477) * [Restricting block editing capabilities based on the context](https://github.com/WordPress/gutenberg/issues/27848) Overview Issues: ✅ [Part 1](https://github.com/WordPress/gutenberg/issues/20791), ✅ [Part 2](https://github.com/WordPress/gutenberg/issues/24818), ⚒️ [Part 3](https://github.com/WordPress/gutenberg/issues/27814) ### Global Styles Global Styles comprises two major areas that fall underneath the global styles umbrella: centralized theme configuration and an interface for manipulating visual aspects of blocks globally. Theme configuration absorbs things like declaring color palettes, presets, different supports and settings, and toggle on or off the available block design tools (typography, colors, dimensions, etc.). All of this can be managed through the theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. configuration file and is one of the key features available in WordPress 5.8. After a [few iterations](https://github.com/WordPress/gutenberg/issues/29891) and [open testing](https://make.wordpress.org/test/2021/06/24/call-for-testing-thrive-with-theme-json/), this feature is considered stable and moved to a maintenance phase. The other major part of global styles is the user interface to make edits to blocks globally. With theme.json in place, the next release cycle will have the [Global Styles UI](https://github.com/WordPress/gutenberg/issues/27473#issuecomment-796773866) as one of its main focuses, allowing users to tweak the theme easily. [Color handling](https://github.com/WordPress/gutenberg/issues/29568) will be an important focus, not only to better theme switch but also to seamlessly integrate color palettes with patterns. ![](https://lh3.googleusercontent.com/felV3uDo4aHZPuhwqfFZuHl_CLubxz3iKOW8C7SjKXdpityt9Dog1J8REDP5mGWD7DnnhKFAZXo5zZqYOT3_e6ePmeJiF2h7ZWwRD22Vwc0T4jxu0VGU_mYVEboV7eHiTv- jWBt_) ⚒️ [Global Styles Overview Issue](https://github.com/WordPress/gutenberg/issues/20331) ### Theme Blocks To support the theme building needs outside of the template and template parts infrastructure, there was a need to create many new blocks centered around theme functions. WordPress 5.8 brings several of these blocks, from Site Title, Site Tagline, and Site Logo that allow users to configure site settings with blocks, to the post-related blocks such as Post Title and Post Date, to be used inside a Query LoopLoop The 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](https://codex.wordpress.org/The_Loop) to display post data. ![](https://lh3.googleusercontent.com/zsPjl1HldyoYOSC3yDA_gIhUNaRpjtWv5ydHBM0p2BeAnpeWl3GO- O8wG1PEu8dykGJ32lkHH01iRfT-u4vj4K82MwOa9Xe4qfzdV3-kraDRs1DSSH0sNWffLAISziOOrOJm1b2f) Although new theme blocks may be added as the need arises and the existing ones will receive incremental upgrades, the basics of this milestone are complete. ✅ [Theme blocks Overview Issue](https://github.com/WordPress/gutenberg/issues/22724) ### Query Loop Block Among the theme blocks, the Query Loop Block has been a significant area of the site editing focus in the past months, deserving its own milestone. Taking some of the block APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. infrastructures to the limit, such a powerful block [has proven challenging to expose](https://make.wordpress.org/test/2021/04/14/fse-program-testing-call-5-query-quest/) at a user level. As a result of the feedback collected in the FSE Outreach Program, the block [has been renamed to clear confusion](https://github.com/WordPress/gutenberg/pull/32514), and [usability enhancements have been implemented ](https://github.com/WordPress/gutenberg/issues/30910) before launching it in WordPress 5.8. With the Query Loop foundations in place, the next iterations will seek to ease the user interactions and flows, even more, thanks to two fundamental Gutenberg tools – block patterns and block variations. The former will continue to help set the inner block structure and content. In contrast, the latter will present the powerful Query Loop’s features [in the form of preconfigured blocks](https://github.com/WordPress/gutenberg/issues/32268) and consolidate[ similar blocks to use the Query Loop Block](https://github.com/WordPress/gutenberg/issues/32332) as their underlying mechanism. ✅ [Query Loop Block Overview Issue](https://github.com/WordPress/gutenberg/issues/24762) ### Navigation Block Along with the Query Loop Block, the Navigation Block is another theme block that stands out as a project in its own right. This block has seen great improvements in the last few months, from [improved overlays](https://github.com/WordPress/gutenberg/pull/31149) to [responsive menus](https://github.com/WordPress/gutenberg/pull/30047). New blocks are available as well, such as the [Home Link block](https://github.com/WordPress/gutenberg/pull/30926). Shortly, we will see the Navigation block house whole new kinds of blocks thanks to the recent [frontend markup adjustments that allow blocks other than links](https://github.com/WordPress/gutenberg/pull/30551) in an accessible way. ![](https://lh5.googleusercontent.com/Zy-LUHbBb1GbluRKtQRFB9hc2gUv-PoPGM9IZImHJ2kFHX8EM7pVAAMryKq8cfzlUeXjSL6vlbP8afpneH_4QGW5OHYyiR22K9pwXDyOgbKZCgFnQYopnyLK- p46eSs_s1D8V6dR) Because of its key role in building rich theme blocks, the Navigation Block will be one primary focus during the next WordPress release cycle. Apart from [more blocks being available inside the Navigation Block](https://github.com/WordPress/gutenberg/issues/33278#issuecomment-879559751), customization options – such as [configuring dropdown behavior](https://github.com/WordPress/gutenberg/issues/18395) or adding [fullscreen variants](https://github.com/WordPress/gutenberg/issues/24604)– are an area that seeks improvement. These customizations should be design-driven due to the multiple layouts [nested navigation menus](https://github.com/WordPress/gutenberg/issues/23745) can have. ⚒️ [Navigation Block Tracking Issue](https://github.com/WordPress/gutenberg/issues/27593) ### Site Editing Gradual adoption Full Site Editing represents a new paradigm in site and theme building in the well- established WordPress ecosystem, and as such, providing the right tools is key to gradual adoption. Tools like the Widgets Editor and Navigation Editor bring block editing capabilities to traditional features that can’t take full advantage of their native block counterpart implementation. WordPress 5.8 brings the power of blocks to both the Block Widgets Editor and the CustomizerCustomizer Tool 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.. Users will be able to add blocks in widgetWidget A 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. areas, add widgets and blocks with live preview, and schedule and share directly from the Customizer. Because blocks can now be added to widget areas, developers are encouraged to phase out their widgets in favor of blocks, which are more intuitive and can be used in more places. Developers can [allow users to easily migrate a Legacy Widget block containing a specific widget to a block](https://developer.wordpress.org/block-editor/how-to-guides/widgets/legacy-widget-block/#allowing-migration-to-a-block) or multiple blocks.  On the other hand, the Navigation Editor has also seen its share of iterative improvements in the last months. Together with the Navigation Block, it will remain an ongoing focus for the next WordPress release cycle. ✅ [Widgets Editor Tracking Issue](https://github.com/WordPress/gutenberg/issues/24687) ⚒️ [Navigation Editor Tracking Issue](https://github.com/WordPress/gutenberg/issues/29102) ### Smoothing block interactions As mentioned with regards to Query and Navigation blocks, the complexity of the editor increases as site editing capabilities are introduced with advanced block structures and customization options. This highlights the need to expand our APIs and interactions — which are well suited for simple block structures — [to better support container blocks](https://github.com/WordPress/gutenberg/issues/27324). To address some of this, the[ List View introduced in Gutenberg 10.7, and WordPress 5.8](https://make.wordpress.org/core/2021/06/09/core-editor-improvement-improve-your-workflow-with-list-view/) aims to help navigate these advanced structures more efficiently and should [continue evolving further](https://github.com/WordPress/gutenberg/issues/29736) in the future. Internally, the List View is powered by a component available in the post editor List View and advanced blocks like Navigation; all features and blocks having a list of blocks will benefit from the [improvements made to this component](https://github.com/WordPress/gutenberg/issues/29733). ![](https://lh3.googleusercontent.com/sNNAgkDcdighxbAZtUVlHwgsq-V1p3c2uo6lZl7jISQ_yrGDUku7iF- iHqYPnkLkiHmS5r32Jj-FZjcMQ5DUYokoTGXW8_-R7bwDgS5TDGWbOE92ueQ-fZJ9g7uCWCnoA_pepxim) Another challenging editing experience with the increased number of container and inner blocks is adjusting parent block settings when editing a child block.  Users often need to switch between different child and parent blocks to change settings like layout or positioning. In turn, it is necessary to explore [Toolbar absorption mechanisms](https://github.com/WordPress/gutenberg/issues/26313) that allow parent blocks to expose their toolbar on their children. ### Patterns At this stage, it is no secret that block patterns represent considerable potential for users to add many blocks with different preset layouts and settings easily. By using patterns, users don’t need to individually add blocks to achieve rich representations in headers, columns, or Query blocks, as patterns act as a jumpstart blueprint that can be tweaked and adjusted to the user’s needs.  An example of the improved interaction block patterns is demonstrated by the Query block, which allows users to select[ block patterns in its placeholder state](https://github.com/WordPress/gutenberg/pull/29602). This is just the tip of the iceberg in terms of the ways patterns can leverage the editing experience, and as such, efforts will continue improving pattern insertion capabilities. ![](https://lh3.googleusercontent.com/EM1NLQEnmJt1zX8yOkVqldvtoEMWlhRyArmg9mdfQoYLlfqHJeeIllODNVtOfL4Xqatm23A094SREshlHW1M_MVWlZdlJOqepn1qLHc0Fvf0qNCjENLvkMO4aiVGR3Z7wPIe99fj) Thanks to the [recently released Block Pattern Directory](https://make.wordpress.org/meta/2021/07/20/the-wordpress-pattern-directory-is-live/), patterns can be copied and pasted into the block editor; upcoming Gutenberg iterations will connect and retrieve patterns from this directory, allowing users to choose from huge amounts of beautiful patterns without leaving the editor. Both to ease navigating the big number of patterns users will be able to choose from and accommodate increased pattern complexity and richness, such as in Query or HeaderHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. patterns, revisiting the pattern insertion UI will be an ongoing focus in the months to come.  ⚒️ [Pattern Insertion Tracking Issue](https://github.com/WordPress/gutenberg/issues/31153) ### Design Tools Several design tools are needed to ​​ensure a wide range of exquisitely crafted patterns can support powerful settings and rich block customizations. These encompass all tools related to the appearance of blocks and range from colors, typography, alignments, and positioning to filters like duotone, cropping, and background media and will need to integrate seamlessly with theme.json mechanics. Going further, controls like font size, even if exposed as single values to users in the UI, are built behind the scenes to accommodate different viewport ranges. Apart from providing access to the underlying mechanisms through theme.json, [responsive-previewing and device-specific editing](https://github.com/WordPress/gutenberg/issues/19909) will be necessary to support this. ![](https://lh4.googleusercontent.com/nJo3q1ruBiIf1aseaYZBrCacPSZlppRfMuFnyG2rXF4M3uCEmGApFg- DGMaRUcHoLPiZK_lrhvCiFVm120U3tas1y7O5zni4yCESZZOVKKyL8ZeJ3uZrRTlnZB0XQI81rP6WyIVG) To support the ever-increasing number of tools, the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme., while secondary in some regards to the block canvas and toolbar, [will need to accommodate many of these tools](https://github.com/WordPress/gutenberg/issues/27331), whereas the [Component System](https://github.com/WordPress/gutenberg/issues/27484) will provide a shared design language between all these controls. ⚒️ [Design Tools Overview Issue](https://github.com/WordPress/gutenberg/issues/33447) --- #### How to follow along with Gutenberg [Here’s an overview of different ways](https://make.wordpress.org/core/2020/05/20/ways-to-keep-up-with-full-site-editing-fse/) to keep up with Gutenberg and the Full Site Editing project. There is also an index page of [Gutenberg development-related posts](https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/) and an updated [Site Editing overview issue](https://github.com/WordPress/gutenberg/issues/33094) that breaks down the upcoming work into more concrete next steps. #### Ways to Get Involved While the above items are our focuses, don’t forget that you can always help with [triage](https://developer.wordpress.org/block-editor/contributors/triage/), [testing issues](https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is%3Aissue+label%3A%22Needs+Testing%22), [good first issues](https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+First+Issue%22), and [reviewing PRs](https://github.com/WordPress/gutenberg/tree/master/packages/env). In particular, if you’re interested in helping with triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. but don’t know where to start, there’s a course on Learn WordPress for [how to do triage on GitHub!](https://learn.wordpress.org/workshop/how-to-do-triage-on-github/) Check it out and join us. Hearing your feedback is crucial to drive upcoming priorities and iterate on our work, so you are more than welcome to [join our Full Site Editing Outreach Program](https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/)! If there’s anything we can do to make contributing easier, let us know in the comments or [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7) chats. While we can’t promise to fix everything, we’d appreciate being aware of any blockers. --- _Props to [@javiarce](https://profiles.wordpress.org/javiarce/) for creating the images, and to [@cbringmann](https://profiles.wordpress.org/cbringmann/) and [@mcsf](https://profiles.wordpress.org/mcsf/) for reviewing the post._ [#core-editor](https://make.wordpress.org/core/tag/core-editor/) [#gutenberg-next](https://make.wordpress.org/core/tag/gutenberg-next/) [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/) [#full-site-editing](https://make.wordpress.org/core/tag/full-site-editing/) [ ](https://profiles.wordpress.org/gwwar/) [Kerry Liu](https://profiles.wordpress.org/gwwar/) 4:26 am _on_ July 21, 2021 Tags: [block-editor ( 139 )](https://make.wordpress.org/core/tag/block-editor/), [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-new ( 216 )](https://make.wordpress.org/core/tag/gutenberg-new/)    # 󠀁[What’s new in Gutenberg 11.1.0? (21 July)](https://make.wordpress.org/core/2021/07/21/whats-new-in-gutenberg-11-1-0-21-july/)󠁿 Two weeks have passed since the last GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) release, which means a new version is available! [Gutenberg 11.1](https://github.com/WordPress/gutenberg/releases/tag/v11.1.0) adds the ability to edit a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. border easily, enables drag and drop support for the List View component, and includes many bugbug A 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. fixes centered around the Widgets Editor and Block Library. ## Block supports: border Take an early look at custom block borders! When borders are enabled in a [theme.json](https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-json/) file, and a block declares that it supports it with the [block supports](https://developer.wordpress.org/block-editor/reference-guides/block-api/block-supports/) APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., a new block panel is available that lets us change the [border radius, width, style, color](https://github.com/WordPress/gutenberg/pull/31585), and [border units](https://github.com/WordPress/gutenberg/pull/33315). Set and style custom block borders ## List View drag and drop Intuitively move and reorder blocks using [drag and drop in the List View](https://github.com/WordPress/gutenberg/pull/33320). Use the persistent list view to reorder blocks ## 11.1.0 ### Enhancements * Adminadmin (and super admin) panel available as PWA. ([33102](https://github.com/WordPress/gutenberg/pull/33102), [33310](https://github.com/WordPress/gutenberg/pull/33310)) * Block Breadcrumbs: Small chevron icon for breadcrumb separators. ([33042](https://github.com/WordPress/gutenberg/pull/33042)) * Block Library: - Columns Block: * Add stack on mobile setting to allow for columns without mobile breakpoints.( [31816](https://github.com/WordPress/gutenberg/pull/31816)) * Add the percent unit to the default units in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..( [33468](https://github.com/WordPress/gutenberg/pull/33468)) - Latest posts: Remove grey color for dark themes. ([33325](https://github.com/WordPress/gutenberg/pull/33325)) - List Block: Add link color control to list block. ([33185](https://github.com/WordPress/gutenberg/pull/33185)) - Post Terms Block: Add a “separator” attribute to post-terms block. ([32812](https://github.com/WordPress/gutenberg/pull/32812)) - RSS Block: Update block styles. ([33294](https://github.com/WordPress/gutenberg/pull/33294)) - Tag Cloud Block: * Add ability to change number of tags shown. ([32201](https://github.com/WordPress/gutenberg/pull/32201)) * Remove editor style so editor matches frontend. ([33289](https://github.com/WordPress/gutenberg/pull/33289)) * Design Tools, Border: - Add support for custom border units. ([33315](https://github.com/WordPress/gutenberg/pull/33315)) - Update border support UIUI User interface. ([31585](https://github.com/WordPress/gutenberg/pull/31585)) - Set border style none when border width zero. ([32080](https://github.com/WordPress/gutenberg/pull/32080)) * Link Editing: Add Unlink button to LinkControl popover. ([32541](https://github.com/WordPress/gutenberg/pull/32541)) * List View: Enable drag and drop in List View. ([33320](https://github.com/WordPress/gutenberg/pull/33320)) * WidgetWidget A 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. Editor: Adds auxiliary class names for editor styles. ([33388](https://github.com/WordPress/gutenberg/pull/33388)) * General UI: - Block Settings Menu: Don’t render ‘Move to’ if there is only one block. ([33158](https://github.com/WordPress/gutenberg/pull/33158)) - Disable ‘Post Publish’ button if saving non-post entities. ([33140](https://github.com/WordPress/gutenberg/pull/33140)) - Preferences: Polish labels and consolidate options in preferences. ([33133](https://github.com/WordPress/gutenberg/pull/33133)) ### New APIs * REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/): Block editor settings endpoint. ([33128](https://github.com/WordPress/gutenberg/pull/33128)) * UI Components: Add a SearchControl component and reuse across the UI. ([32935](https://github.com/WordPress/gutenberg/pull/32935)) ### Performance * Improve List View performance. ([33320](https://github.com/WordPress/gutenberg/pull/33320)) * Pattern Directory: Caching updates. ([33052](https://github.com/WordPress/gutenberg/pull/33052)) ### AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) * Improve high contrast mode rendering of icon buttons. ([33062](https://github.com/WordPress/gutenberg/pull/33062)) ### Bug Fixes * Block Breadcrumbs: Fix breadcrumbs htmlHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. structure and ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. [https://reactjs.org](https://reactjs.org/) warnings. ([33159](https://github.com/WordPress/gutenberg/pull/33159)) * Block Editor: - Move layout styles to document head (instead of rendering inline). ([32083](https://github.com/WordPress/gutenberg/pull/32083)) - Warn only in `edit` implementation when using `useBlockProps`. ([33380](https://github.com/WordPress/gutenberg/pull/33380)) - Iframeiframe iFrame 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.: Remove reset styles. ([33204](https://github.com/WordPress/gutenberg/pull/33204)) * Block Library: - Buttons Block: Remove green background color in button preview. ([33116](https://github.com/WordPress/gutenberg/pull/33116)) - Embed Block: Include missing attributes when upgrading embed block. ([33235](https://github.com/WordPress/gutenberg/pull/33235)) - Image Block: * Improve “can switch to cover” check. ([33095](https://github.com/WordPress/gutenberg/pull/33095)) * Fix replace link control styling. ([33326](https://github.com/WordPress/gutenberg/pull/33326)) - Query LoopLoop The 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](https://codex.wordpress.org/The_Loop) Block: * Prevent entering invalidinvalid A 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. values in the Query Loop block configuration. ([33285](https://github.com/WordPress/gutenberg/pull/33285)) * Update getTermsInfo() to workaround parsing issue for translatable strings.( [33341](https://github.com/WordPress/gutenberg/pull/33341)) - Search Block: * Fix search block button position dropdown accessibility/UXUX User experience issues. ([33376](https://github.com/WordPress/gutenberg/pull/33376)) * Update search block to handle per corner border radii. ([33023](https://github.com/WordPress/gutenberg/pull/33023)) - Site Title: Decode entities in site title. ([33323](https://github.com/WordPress/gutenberg/pull/33323)) - Home Link: Remove padding. ([33461](https://github.com/WordPress/gutenberg/pull/33461)) - Post Except: Fix `excerpt_more` filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered _stale_, and will require a _refresh_ of the changes before it can be applied, or the conflicts will need to be _resolved_. and remove `wordCount` attribute.( [33366](https://github.com/WordPress/gutenberg/pull/33366)) * Design Tools: - Color: Prevent color panel from showing as empty. ([33369](https://github.com/WordPress/gutenberg/pull/33369)) - Duotone: * Avoid rendering duplicate stylesheet and SVG. ([33233](https://github.com/WordPress/gutenberg/pull/33233)) * Update conditions to hide duotone panel. ([33295](https://github.com/WordPress/gutenberg/pull/33295)) - Theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. * Allow themes to provide empty values for `color.duotone` and `spacing.units`.( [33280](https://github.com/WordPress/gutenberg/pull/33280)) * Specify what settings can be part of `settings.layout`. ([33303](https://github.com/WordPress/gutenberg/pull/33303)) * Rich text: - Fix format deregistration. ([31518](https://github.com/WordPress/gutenberg/pull/31518)) - Autocomplete: Reset state for empty text. ([33450](https://github.com/WordPress/gutenberg/pull/33450)) - Run input rules after composition end. ([33416](https://github.com/WordPress/gutenberg/pull/33416)) * Site Editor: Close navigation sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. when all posts clicked. ([33393](https://github.com/WordPress/gutenberg/pull/33393)) * Slash Inserter: Fix slash command focus style. ([33084](https://github.com/WordPress/gutenberg/pull/33084)) * Widgets Editor: - Fix moving inner blocks in the Widgets CustomizerCustomizer Tool 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.. ([33243](https://github.com/WordPress/gutenberg/pull/33243)) - Fix inserter size on Widgets Editor headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.. ([33118](https://github.com/WordPress/gutenberg/pull/33118)) - Merge conflicting `wp.editor` objects into a single, non-conflicting module.( [33228](https://github.com/WordPress/gutenberg/pull/33228)) - Retrieve latest widgets before loading sidebars. ([32997](https://github.com/WordPress/gutenberg/pull/32997)) * Writing flow: - Allow select all from empty selection. ([33446](https://github.com/WordPress/gutenberg/pull/33446)) - Attempt to fix preview end-to-end failure. ([33467](https://github.com/WordPress/gutenberg/pull/33467)) * Components: - Suggestion List: Check if a node exists to scroll into view. ([33419](https://github.com/WordPress/gutenberg/pull/33419)) - Navigation component: Fix item handling onClick twice. ([33286](https://github.com/WordPress/gutenberg/pull/33286)) * Editor: Extract snackbars into a separate component. ([33355](https://github.com/WordPress/gutenberg/pull/33355)) ### Experiments * Component System: - Promote g2 `Popover` as `Flyout`. ([32197](https://github.com/WordPress/gutenberg/pull/32197)) - Add useControlledValue. ([33039](https://github.com/WordPress/gutenberg/pull/33039)) - Add normalizeArrowKey. ([33208](https://github.com/WordPress/gutenberg/pull/33208)) - Add mergeEventHandlers. ([33205](https://github.com/WordPress/gutenberg/pull/33205)) - Add useCx. ([33172](https://github.com/WordPress/gutenberg/pull/33172)) - Add useLatestRef hook. ([33137](https://github.com/WordPress/gutenberg/pull/33137)) - Remove `@emotion/css` from Divider. ([33054](https://github.com/WordPress/gutenberg/pull/33054)) * Navigation Block: - Add Color Options for Submenus. ([31149](https://github.com/WordPress/gutenberg/pull/31149)) - Change Navigation block markup on front end only. ([30551](https://github.com/WordPress/gutenberg/pull/30551)) - Improve handling of open overlay. ([32886](https://github.com/WordPress/gutenberg/pull/32886)) - Menu item placeholder inheritance. ([32512](https://github.com/WordPress/gutenberg/pull/32512)) - Pass block attributes with rendering with location. ([33043](https://github.com/WordPress/gutenberg/pull/33043)) - Refactor of navigation block rendering using location attribute. ([33244](https://github.com/WordPress/gutenberg/pull/33244)) * Global Styles: - Cover against non existing styles. ([33127](https://github.com/WordPress/gutenberg/pull/33127)) - Missing link color on style properties to css var mapping. ([33150](https://github.com/WordPress/gutenberg/pull/33150)) - Preset variables not being user on the site editor. ([33149](https://github.com/WordPress/gutenberg/pull/33149)) ### Documentation * Admin PWA: Make readme private. ([33216](https://github.com/WordPress/gutenberg/pull/33216)) * Handbook: - Block API: * Apply enhancements included in WordPress 5.8. ([33252](https://github.com/WordPress/gutenberg/pull/33252)) * Clarify the type of `apiVersion` in block metadata. ([33249](https://github.com/WordPress/gutenberg/pull/33249)) * Fixes a typo in the documentation for block supports. ([33247](https://github.com/WordPress/gutenberg/pull/33247)) - Block Editor API: Changes to support multiple admin screens in WP 5.8. ([33262](https://github.com/WordPress/gutenberg/pull/33262)) - Custom Block Editor: Fixed bad image syntax and bold text. ([32897](https://github.com/WordPress/gutenberg/pull/32897)) - Fix API documentation for data reference guides. ([33384](https://github.com/WordPress/gutenberg/pull/33384)) - PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Release: Update Gutenberg release documentation to clarify release post workflow. ([33328](https://github.com/WordPress/gutenberg/pull/33328)) - `theme.json`: * Add examples and highlight backward compatibility. ([33421](https://github.com/WordPress/gutenberg/pull/33421)) * Update `theme.json` documentation for WordPress 5.8. ([33131](https://github.com/WordPress/gutenberg/pull/33131)) * Fix codetabs syntax in `theme.json` documentation. ([33417](https://github.com/WordPress/gutenberg/pull/33417)) - Use markdown headings instead of links for API declarations. ([33381](https://github.com/WordPress/gutenberg/pull/33381)) * Update documentation for link color in WordPress 5.8. ([33162](https://github.com/WordPress/gutenberg/pull/33162)) * Packages: - Add `PanelBody` for `InspectorControls`. ([33227](https://github.com/WordPress/gutenberg/pull/33227)) - Correct wrong setState call. ([32808](https://github.com/WordPress/gutenberg/pull/32808)) - Remove `withState` HOC references. ([33173](https://github.com/WordPress/gutenberg/pull/33173), [33222](https://github.com/WordPress/gutenberg/pull/33222), [33259](https://github.com/WordPress/gutenberg/pull/33259)) ### Code Quality * Avoid calling `gutenberg_` functions within code shipped through WordPress Core.( [33331](https://github.com/WordPress/gutenberg/pull/33331)) * Block Editor: - Refactor the user autocompleter to avoid apiFetch and rely on the data module.( [33028](https://github.com/WordPress/gutenberg/pull/33028)) - Warn when `useBlockProps` hook used with a wrong Block API version. ([33274](https://github.com/WordPress/gutenberg/pull/33274)) * Block Library: - Image Block: Fix uncaught error. ([24334](https://github.com/WordPress/gutenberg/pull/24334)) - Latest Posts Block: Refactor to drop apiFetch usage in favor of using the data module. ([33063](https://github.com/WordPress/gutenberg/pull/33063)) - Template Part Block: Remove unnecessary function exists check on wp_filter_content_tags.( [33182](https://github.com/WordPress/gutenberg/pull/33182)) * Components: - BlockNavigation: Restructure the BlockNavigation component. ([31892](https://github.com/WordPress/gutenberg/pull/31892)) - Box Control: Rename VerticalHorizontalInputControls to AxialInputControls.( [33016](https://github.com/WordPress/gutenberg/pull/33016)) - GradientPicker: Stabilises GradientPicker and CustomGradientPicker components.( [31440](https://github.com/WordPress/gutenberg/pull/31440)) - Toolbar: Enforce `isAlternate` on `ToolbarDropdownMenu`. ([33129](https://github.com/WordPress/gutenberg/pull/33129)) - ZStack: Remove `@emotion/css` from ZStack. ([33053](https://github.com/WordPress/gutenberg/pull/33053)) * Packages: Hoist dependencies for WordPress packages. ([33387](https://github.com/WordPress/gutenberg/pull/33387)) * Plugin: Remove deprecated APIs that are no longer supported in version 11.0. ( [33258](https://github.com/WordPress/gutenberg/pull/33258)) ### Tools * Testing: - Add basic Site Title block coverage. ([32868](https://github.com/WordPress/gutenberg/pull/32868)) - Add some functionality to `createUser` and `deleteUser`. ([33067](https://github.com/WordPress/gutenberg/pull/33067)) - Enable previously skipped widgets tests. ([33121](https://github.com/WordPress/gutenberg/pull/33121)) - Skipping more end-to-end tests. ([33353](https://github.com/WordPress/gutenberg/pull/33353)) - Skip unstable end-to-end tests. ([33352](https://github.com/WordPress/gutenberg/pull/33352)) - Switch to new puppeteer APIs for emulating conditions. ([33410](https://github.com/WordPress/gutenberg/pull/33410)) - Update end-to-end tests to use new puppeteer drag and drop api. ([33386](https://github.com/WordPress/gutenberg/pull/33386)) * Dependencies: - Update CopyWebpackPlugin to v6. ([33220](https://github.com/WordPress/gutenberg/pull/33220)) - Upgrade Husky to 7.0.0 and git ignorance improved. ([33183](https://github.com/WordPress/gutenberg/pull/33183)) - Upgrade Puppeteer to 10.1. ([33327](https://github.com/WordPress/gutenberg/pull/33327)) - Upgrade Storybook to v6.3. ([33219](https://github.com/WordPress/gutenberg/pull/33219)) * NPM Packages: Introduce release types to npm publishing script. ([33329](https://github.com/WordPress/gutenberg/pull/33329)) * Plugin: Introduce `tools` folder with configuration files. ([33281](https://github.com/WordPress/gutenberg/pull/33281)) * Workflows: - Release Workflow: Remove “experimental” status from WP 5.8 stable items. ( [33214](https://github.com/WordPress/gutenberg/pull/33214)) - Re-enable manually triggered workflows on forks. ([32821](https://github.com/WordPress/gutenberg/pull/32821)) - Use NPM caching built into `action/setup-node`. ([33190](https://github.com/WordPress/gutenberg/pull/33190)) ## Performance Benchmark The following benchmark compares performance for a particularly sizeable post (~ 36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance. | Version | Loading Time | KeyPress Event (typing) | | Gutenberg 11.1 | 6.38s | 26.12ms | | Gutenberg 11.0 | 6.06s | 29.55ms | | WordPress 5.7 | 8.52s | 36.26ms | Kudos to all the contributors that helped with the release! 👏 Thanks to [**@javiarce**](https://profiles.wordpress.org/javiarce/) for creating the release post assets, [@cbringmann](https://profiles.wordpress.org/cbringmann/) for proofreading, and [@priethor](https://profiles.wordpress.org/priethor/), [@youknowriad](https://profiles.wordpress.org/youknowriad/), and [@get_dave](https://profiles.wordpress.org/get_dave/) for guiding me through this release! [#block-editor](https://make.wordpress.org/core/tag/block-editor/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#gutenberg-new](https://make.wordpress.org/core/tag/gutenberg-new/) # Post navigation [← Older posts](https://make.wordpress.org/core/2021/page/25/?output_format=md) [Newer posts →](https://make.wordpress.org/core/2021/page/23/?output_format=md)