Title: What’s next in Gutenberg? (June 2021) Author: Héctor Prieto Published: June 4, 2021 --- [ ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/) 9:27 pm _on_ June 4, 2021 Tags: [core-editor ( 761 )](https://make.wordpress.org/core/tag/core-editor/), [gutenberg ( 553 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-next ( 23 )](https://make.wordpress.org/core/tag/gutenberg-next/) # What’s next in Gutenberg? (June 2021) This monthly status update contains the high-level items that 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/) contributors are focusing on for June. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so. **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 a [Site Editing Milestone overview issue](https://github.com/WordPress/gutenberg/issues/24551) that breaks down the upcoming work into more concrete next steps. ## WordPress 5.8 focuses With [WordPress 5.8 Beta 1 planned for June 8](https://make.wordpress.org/core/2021/03/30/5-8-pre-planning/),** the priorities for the month heavily focus on stabilizing, testing, 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. fixing, and documenting the features recently merged in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.**, which can be followed in the [WordPress 5.8 project board](https://github.com/WordPress/gutenberg/projects/55). However, design and development in other Gutenberg areas continue as well, and contributions are welcome! The remaining tasks for 5.8 include: * Audit correct [editability of content with FSE blocks](https://github.com/WordPress/gutenberg/issues/26573#issuecomment-848582711) * [Use theme mods for templates and template parts](https://github.com/WordPress/gutenberg/pull/31971) * Polish some Query 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. aspects, including: - Prevent editing post content by mistake in 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) by [disabling editing content by default](https://github.com/WordPress/gutenberg/issues/32317). - [Clarify the “inherit query” setting](https://github.com/WordPress/gutenberg/issues/31113) and [set its default value according to the context](https://github.com/WordPress/gutenberg/pull/32230). - [Rename the Query and Loop blocks](https://github.com/WordPress/gutenberg/pull/32283). * [Write Dev Notes](https://github.com/WordPress/gutenberg/issues/32365) ## Widgets Editor Work on the block-based Widgets Editor is a continued focus. The main efforts target stabilizing and documenting the 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. block editor, as well as deciding [whether the Widgets Editor should be enabled by default](https://github.com/WordPress/gutenberg/issues/26154). If you want to help us test the block-based Widgets Editor, drop by the [Widgets Editor Call for Testing](https://make.wordpress.org/core/2021/05/12/help-test-the-widgets-editor-for-wordpress-5-8/) and report on your experience! **Follow along:** You can find more information about the current work in progress in this [tracking issue](https://github.com/WordPress/gutenberg/issues/24687), as well as[ on this project board](https://github.com/WordPress/gutenberg/projects/27). Moreover, you can join [#feature-widgets-block-editor](https://make.wordpress.org/core/tag/feature-widgets-block-editor/) in WordPress.orgWordPress.org The 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/](https://wordpress.org/) 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/) for future 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-focused meetings. ## Navigation Editor Like the Widgets Editor, the Navigation Editor aims to help expand what’s possible with menus while bringing block functionality to yet another part of WordPress and offer a more modern experience. Current efforts include: * Continue defining Navigation Editor architecture. * Provide a [better way to disable/enable Navigation block features](https://github.com/WordPress/gutenberg/issues/30007) for the Navigation editor by [defining allowed inner blocks in the Navigation block via the block supports mechanism](https://github.com/WordPress/gutenberg/pull/32426). **Follow along:** You can follow the progress of this project [on this project board](https://github.com/WordPress/gutenberg/projects/31) or review the new [Navigation Editor tracking issue](https://github.com/WordPress/gutenberg/issues/29102) and join[ #feature-navigation-block-editor](https://wordpress.slack.com/archives/C01KDAZJMQ9) in WordPress.org Slack. ## Full Site Editing Work on this major focus for phase 2 is ongoing and is expected to [continue as a big-picture goal for 2021](https://make.wordpress.org/updates/2021/01/21/big-picture-goals-2021/). Apart from all the features making it into 5.8, this is the status of the different FSE areas and their upcoming work: Milestone 1 – [Site Editing Infrastructure and UI](https://github.com/WordPress/gutenberg/issues/24818) * As the Template Editing Mode is landing in 5.8, efforts focus on testing and stabilizing this feature. If you would like to help, check the [current FSE Outreach Program round](https://make.wordpress.org/test/2021/05/26/fse-program-testing-call-7-polished-portfolios/) focused on Template Editing Mode! Milestone 3 – [Global Styles](https://github.com/WordPress/gutenberg/issues/20331) * The first version of Global Styles has been merged in core, and focuses need to be revisited. Any relevant update will be posted in [this GitHub issue](https://github.com/WordPress/gutenberg/issues/20331#issuecomment-848685044) on demand. Milestone 4 – [Theme Blocks](https://github.com/WordPress/gutenberg/issues/22724) * With most [theme blocks](https://github.com/WordPress/gutenberg/issues/28744) merged in core, it’s time to polish the Site Logo block’s design and [bring feature parity with the Image block](https://github.com/WordPress/gutenberg/issues/30406). * Similarly, the [Site Title](https://github.com/WordPress/gutenberg/issues/30918) and [Site Tagline](https://github.com/WordPress/gutenberg/issues/30921) blocks require varnishing to bring feature parity with other text blocks. * Because Post-related blocks (Post Title, Post Date, etc.) behavior varies depending on the context they are in (post, template, or Query), it would be nice to [make their descriptions context-aware](https://github.com/WordPress/gutenberg/issues/32319). Milestone 5 – [Query Block](https://github.com/WordPress/gutenberg/issues/24762) * With great power comes great responsibility; because the Query Block is so powerful, contributors are making sure it lands in the best status possible in 5.8 as mentioned in the [“WordPress 5.8 focuses” section above](https://make.wordpress.org/core/2021/06/04/whats-next-in-gutenberg-june-2021/?output_format=md#wordpress-58-focuses). Further work on the Query block not limited to 5.8 includes: * [Refine the Posts List block](https://github.com/WordPress/gutenberg/issues/32268)( Query block variation) * To improve the user experience when inserting and modifying an existing Query block, creating [a UI that suggests patterns that are contextual](https://github.com/WordPress/gutenberg/issues/28736) to the currently selected block Milestone 6 – [Navigation Block](https://github.com/WordPress/gutenberg/issues/27593) * The main focus within the Navigation Block is to support [non-li inner blocks](https://github.com/WordPress/gutenberg/issues/29036) generating valid, semantic, accessible markup. There is a [discussion regarding the best approach for solving the navigation markup challenges](https://github.com/WordPress/gutenberg/issues/31951), and contributors are moving forward with having a [different markup in the frontend and the editor](https://github.com/WordPress/gutenberg/pull/30551). * Add an option to render the block [using a classic navigation data source](https://github.com/WordPress/gutenberg/pull/30852). **Follow along:** You can follow the progress of this project with this overview issue showing [key milestones for site editing](https://github.com/WordPress/gutenberg/issues/24551). For each major milestone, there are related issues you can follow if you want a more granular look at each next step. If you’re interested in testing Full Site Editing, check out the [FSE Outreach Program to learn more](https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/). If you have questions about Full Site Editing, [check out this recent effort to offer answers.](https://make.wordpress.org/test/tag/fse-answers/) ## Areas to be aware of **WCEU 2021** [WordCamp Europe 2021 is scheduled for 7 to 9 June 2021](https://europe.wordcamp.org/2021/) as an online event and will include several sessions related to Gutenberg, such as: * Full Site Editing (Discussion Panel) * A walkthrough of Full Site Editing (Workshop) * The Future of Themes in WordPress (Discussion Panel) * Blazing fast block development (Talk) Make sure to [register](https://europe.wordcamp.org/2021/registration/) if you haven’t already! **Theme Developers** * The Themes team held a [“Universal Themes” Hallway Hangout](https://make.wordpress.org/themes/2021/05/10/friday-may-14th-at-14utc/). Check out the [summary and recording of the event](https://make.wordpress.org/themes/2021/05/10/friday-may-14th-at-14utc/#comment-44246) to know more about this upcoming way to build themes that work both with the Site Editor and the Customizer as a fallback, not simultaneously, if the former is not available. **Calls for testing** * Help test the [Widgets Editor for WordPress 5.8](https://make.wordpress.org/core/2021/05/12/help-test-the-widgets-editor-for-wordpress-5-8/). * Help with the [seventh FSE Outreach Program call for testing](https://make.wordpress.org/test/2021/05/26/fse-program-testing-call-7-polished-portfolios/) by building a polished portfolio. This has been **extended to June 16th** to give folks more time to respond! **Block Patterns** * Since [Gutenberg 10.7](https://make.wordpress.org/core/2021/05/27/whats-new-in-gutenberg-10-7-26-may/), block patterns displayed in the inserter are fetched from the [WordPress.org Pattern Directory](https://wordpress.org/patterns/). This opens the door to having a big amount of wonderful patterns available in the inserter, which will require [iterating on the pattern insertion experience](https://github.com/WordPress/gutenberg/issues/31153). For more updates on the Pattern Directory, stay tuned for [Block Pattern Directory updates](https://make.wordpress.org/meta/2021/04/28/block-pattern-directory-update/) and check the most recent [design iterations for the Pattern Directory](https://make.wordpress.org/design/tag/patterns-directory/). ## 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 in GitHub!](https://learn.wordpress.org/workshop/how-to-do-triage-on-github/) Check it out and join us. If there’s anything we can do to make contributing easier, let us know in the comments or in [#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. **Meetings to join:** While you can [view all meetings here](https://make.wordpress.org/meetings/), here are specific meetings to join depending on your interest. Remember that you need a [WordPress.org slack account](https://make.wordpress.org/chat/) to participate: * Core Editor weekly Wednesdays @ 14:00 UTC in [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7) focused on all things Gutenberg. * Block Themes meeting twice monthly on Wednesday @ 16:00 UTC in [#themereview](https://wordpress.slack.com/archives/C02RP4Y3K) focused on preparing for Full Site Editing. _Thanks [@andreamiddleton](https://profiles.wordpress.org/andreamiddleton/)_ and_ [@cbringmann](https://profiles.wordpress.org/cbringmann/) for reviewing this 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/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2021/06/04/whats-next-in-gutenberg-june-2021/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2021/06/04/whats-next-in-gutenberg-june-2021/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2021/06/04/whats-next-in-gutenberg-june-2021/?share=bluesky) * [ X ](https://make.wordpress.org/core/2021/06/04/whats-next-in-gutenberg-june-2021/?share=x) * [ Facebook ](https://make.wordpress.org/core/2021/06/04/whats-next-in-gutenberg-june-2021/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2021/06/04/whats-next-in-gutenberg-june-2021/?share=linkedin) # Post navigation [← CSS Chat Summary: 03 June 2021](https://make.wordpress.org/core/2021/06/04/css-chat-summary-03-june-2021/) [DevChat meeting Summary – June 2, 2021 →](https://make.wordpress.org/core/2021/06/05/devchat-meeting-summary-june-2-2021/)