Title: 2021 – Page 16 – Make WordPress Core --- # Yearly Archives: 2021 [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 9:05 pm _on_ September 21, 2021 Tags: [5.8.2 ( 16 )](https://make.wordpress.org/core/tag/5-8-2/), [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [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 Sept 22, 2021](https://make.wordpress.org/core/2021/09/21/dev-chat-agenda-for-sept-22-2021/)󠁿 Here is the agenda for this week’s developer meeting to occur at [September 22, 2021, at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210922T2000). ## Blogblog (versus network, site) Post Highlights and announcements Bringing to your attention some interesting reads and some call for feedback and/ or volunteers: * [What’s next in Gutenberg? (Mid-September 2021)](https://make.wordpress.org/core/2021/09/17/whats-next-in-gutenberg-mid-september-2021/) * [What’s new in Gutenberg 11.5? (16 September)](https://make.wordpress.org/core/2021/09/17/whats-new-in-gutenberg-11-5-16-september/) * [Editor chat summary: Wednesday, 15 September 2021](https://make.wordpress.org/core/2021/09/20/editor-chat-summary-wednesday-15-september-2021/) * [WordPress JavaScript Standards Change Proposal](https://make.wordpress.org/core/2021/09/21/wordpress-javascript-standards-change-proposal/) * [CSS Chat Summary: 16 September 2021](https://make.wordpress.org/core/2021/09/21/css-chat-summary-16-september-2021/) * [A Week in Core – September 20, 2021](https://make.wordpress.org/core/2021/09/21/a-week-in-core-september-20-2021/) * Reminder: [The WordPress 5.9 planning roundup was published and is waiting for feedback](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/) ## Next releases status update * Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2( five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: WP 5.8.2 * Next major releasemajor release A release, identified by the first two numbers( 3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: WP 5.9 ## 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-2](https://make.wordpress.org/core/tag/5-8-2/), [#5-9](https://make.wordpress.org/core/tag/5-9/), [#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/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 4:30 pm _on_ September 21, 2021 Tags: [5.8.2 ( 16 )](https://make.wordpress.org/core/tag/5-8-2/), [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [core ( 743 )](https://make.wordpress.org/core/tag/core/), [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)    # 󠀁[A Week in Core – September 20, 2021](https://make.wordpress.org/core/2021/09/21/a-week-in-core-september-20-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 September 13 and September 20, 2021. * 21 commits * 42 contributors * 31 tickets created * 0 tickets reopened * 23 tickets closed The Core team is currently working on the next point (5.8.2) and major (5.9) releases 🛠 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=09%2F20%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 ### 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. editor * Cache global stylesheet by theme key – [#53175](https://core.trac.wordpress.org/ticket/53175) ### Build/Test Tools * Expect an absolute path in `WP_TESTS_PHPUNIT_POLYFILLS_PATH` constant – [#46149](https://core.trac.wordpress.org/ticket/46149) * Improve messaging when PHPUnit Polyfills cannot be found – [#46149](https://core.trac.wordpress.org/ticket/46149) * Improve messaging when PHPUnit Polyfills do not comply with version requirements– [#46149](https://core.trac.wordpress.org/ticket/46149) * Make `WP_TESTS_PHPUNIT_POLYFILLS_PATH` more flexible – [#46149](https://core.trac.wordpress.org/ticket/46149) * Reworks `Tests_Option_Option::test_bad_option_names()` into data provider – [#53635](https://core.trac.wordpress.org/ticket/53635) ### Bundled Themes * Twenty Eleven: Set a fixed height for search form when 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. image is added – [#40398](https://core.trac.wordpress.org/ticket/40398) * Twenty Seventeen: Make blogblog (versus network, site) header margin more specific on front page – [#43628](https://core.trac.wordpress.org/ticket/43628) * Twenty Twenty-One: Add missing escaping for the “Secondary menu” label – [#54127](https://core.trac.wordpress.org/ticket/54127) ### Coding Standards * Code Modernization: Fix “passing null to non-nullable” deprecation notice in ` WP_Comment_Query::get_comment_ids()` – [#53635](https://core.trac.wordpress.org/ticket/53635) * Rename the `$arrURL` variable to `$parsed_url` in `WP_Http::request()` – [#53359](https://core.trac.wordpress.org/ticket/53359) * Rename the `$arrURL` variable to `$parsed_url` in `WP_Http_Cookie::__construct()`– [#53359](https://core.trac.wordpress.org/ticket/53359) * Rename the `$arrURL` variable to `$parsed_url` in `WP_Http_Streams::request()`– [#53359](https://core.trac.wordpress.org/ticket/53359) * Rename the `$processedHeaders` variable to `$processed_headers` in `WP_Http:: request()` – [#53359](https://core.trac.wordpress.org/ticket/53359) * Use strict comparison in `wp-inclues/class-wp-http-cookie.php` – [#53359](https://core.trac.wordpress.org/ticket/53359) ### Documentation * Update description for the `$wp_version` global – [#53413](https://core.trac.wordpress.org/ticket/53413) ### Embeds * Add Pinterest as a trusted oEmbed provider – [#53448](https://core.trac.wordpress.org/ticket/53448) ### Internationalization * Add a translator comment to clarify the “Block HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.” string in the Block 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. settings form – [#54110](https://core.trac.wordpress.org/ticket/54110) ### Media * Fix `$content` parameter default value in `img_caption_shortcode()` – [#53635](https://core.trac.wordpress.org/ticket/53635) ### Options, MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. APIs * Fix “passing null to non-nullable” deprecations to `(get|add|update|delete)_option()`– [#53635](https://core.trac.wordpress.org/ticket/53635) ### Upgrade/Install * Create a temporary backup of plugins and themes before updating – [#51857](https://core.trac.wordpress.org/ticket/51857) ## Props **Thanks to the 42 people who contributed to WordPress Core on Trac last week:** [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/) (9), [@jrf](https://profiles.wordpress.org/jrf/)( 8), [@lucatume](https://profiles.wordpress.org/lucatume/) (4), [@schlessera](https://profiles.wordpress.org/schlessera/)( 4), [@jeherve](https://profiles.wordpress.org/jeherve/) (4), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/)( 3), [@mukesh27](https://profiles.wordpress.org/mukesh27/) (3), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 3), [@pbearne](https://profiles.wordpress.org/pbearne/) (2), [@azaozz](https://profiles.wordpress.org/azaozz/)( 2), [@dd32](https://profiles.wordpress.org/dd32/) (2), [@muhammadfaizanhaidar](https://profiles.wordpress.org/muhammadfaizanhaidar/)( 2), [@NekoJonez](https://profiles.wordpress.org/nekojonez/) (1), [@Amieiro](https://profiles.wordpress.org/amieiro/)( 1), [@knutsp](https://profiles.wordpress.org/knutsp/) (1), [@johnbillion](https://profiles.wordpress.org/johnbillion/)( 1), @namith.jawahar (1), [@ayeshrajans](https://profiles.wordpress.org/ayeshrajans/)( 1), [@laurelfulford](https://profiles.wordpress.org/laurelfulford/) (1), [@hirofumi2012](https://profiles.wordpress.org/hirofumi2012/)( 1), [@jainnidhi](https://profiles.wordpress.org/jainnidhi/) (1), [@mai21](https://profiles.wordpress.org/mai21/)( 1), [@fedepia](https://profiles.wordpress.org/fedepia/) (1), [@Soean](https://profiles.wordpress.org/soean/)( 1), [@francina](https://profiles.wordpress.org/francina/) (1), [@a2hosting](https://profiles.wordpress.org/a2hosting/)( 1), [@Boniu91](https://profiles.wordpress.org/boniu91/) (1), [@richards1052](https://profiles.wordpress.org/richards1052/)( 1), [@galbaras](https://profiles.wordpress.org/galbaras/) (1), [@KZeni](https://profiles.wordpress.org/kzeni/)( 1), [@pento](https://profiles.wordpress.org/pento/) (1), [@mikeschroder](https://profiles.wordpress.org/mikeschroder/)( 1), [@audrasjb](https://profiles.wordpress.org/audrasjb/) (1), [@TimothyBlynJacobs](https://profiles.wordpress.org/timothyblynjacobs/)( 1), [@poena](https://profiles.wordpress.org/poena/) (1), [@pbiron](https://profiles.wordpress.org/pbiron/)( 1), [@afragen](https://profiles.wordpress.org/afragen/) (1), [@aristath](https://profiles.wordpress.org/aristath/)( 1), [@joedolson](https://profiles.wordpress.org/joedolson/) (1), [@oandregal](https://profiles.wordpress.org/oandregal/)( 1), [@teucrium](https://profiles.wordpress.org/teucrium/) (1), [@lukecavanagh](https://profiles.wordpress.org/lukecavanagh/)( 1). **Congrats and welcome to our 7 new contributors of the week: **[@NekoJonez](https://profiles.wordpress.org/nekojonez/), [@Amieiro](https://profiles.wordpress.org/amieiro/), @namith.jawahar, [@mai21](https://profiles.wordpress.org/mai21/), [@richards1052](https://profiles.wordpress.org/richards1052/), [@KZeni](https://profiles.wordpress.org/kzeni/), and [@teucrium](https://profiles.wordpress.org/teucrium/) ♥️ **Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 11), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) (8), [@pento](https://profiles.wordpress.org/pento/)( 1), [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) (1). [#5-8-2](https://make.wordpress.org/core/tag/5-8-2/), [#5-9](https://make.wordpress.org/core/tag/5-9/), [#core](https://make.wordpress.org/core/tag/core/), [#week-in-core](https://make.wordpress.org/core/tag/week-in-core/) [ ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/) 3:49 pm _on_ September 21, 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: 16 September 2021](https://make.wordpress.org/core/2021/09/21/css-chat-summary-16-september-2021/)󠁿 [The meeting took place here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1631827176292100). [@dryanpress](https://profiles.wordpress.org/dryanpress/) facilitated and [@danfarrow](https://profiles.wordpress.org/danfarrow/) wrote up these notes. ## CSSCSS Cascading Style Sheets. Custom Properties (󠀁[#49930](https://core.trac.wordpress.org/ticket/49930)󠁿) * [@dryanpress](https://profiles.wordpress.org/dryanpress/) shared the [working document](https://docs.google.com/document/d/1Z0Wo1W0ZQwFJYPcJ8GlsubA9uKhcFdT8ifYnso82z9I/edit) and the [trac ticket](https://core.trac.wordpress.org/ticket/49930), for anybody new to the project * All coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS files have now been claimed, and are either in progress or have a PR, however [@dryanpress](https://profiles.wordpress.org/dryanpress/) reminded us that if anyone has claimed a file and can no longer work on it please do let us know * The next step is reviewing and merging PRs. Help is very welcome if anybody is up for “_trying out a PR and making sure the colors still look correct (or correct enough, where maybe we made changes)_“ * [@dryanpress](https://profiles.wordpress.org/dryanpress/) raised the topic of skinning adminadmin (and super admin) colour schemes, as there are some custom properties for `body.admin-color-ectoplasm` already in `custom-properties.css`. We would probably create a couple of colour schemes at a later stage, for testing& demonstration purposes * [@dryanpress](https://profiles.wordpress.org/dryanpress/) outlined the final todo list for the project: - Merge all remaining files - Look for duplication and opportunities for property consolidation - Final team review - Merge proposal write-ups * [@ryelle](https://profiles.wordpress.org/ryelle/) added that, before the final team review step, discussion will be needed about what to consolidate and how, for example `rgba` and `box-shadow` values * [@ryelle](https://profiles.wordpress.org/ryelle/) added that, as there are several PRs now merged, anybody interested could start generating some ideas for these next steps right now * [@dryanpress](https://profiles.wordpress.org/dryanpress/) asked if we are still on target for an `--experimental` release in 5.9 which [@ryelle](https://profiles.wordpress.org/ryelle/) confirmed we have good momentum for * [@ryelle](https://profiles.wordpress.org/ryelle/) observed that there are other places outside of CSS files where CSS is used, for example `php` and `js` files, which also need to be reviewed. [@dryanpress](https://profiles.wordpress.org/dryanpress/) offered to add this and the other tasks (mentioned above) to the planning document * @CodeXplorer admitted to wanting to help but feeling lost, to which [@dryanpress](https://profiles.wordpress.org/dryanpress/) provided [a few notes of the current state of the project](https://wordpress.slack.com/archives/CQ7V4966Q/p1631828995334700) * [@danfarrow](https://profiles.wordpress.org/danfarrow/) had quickly calculated there are now 127 custom properties in `custom-properties.css`. [@robertg](https://profiles.wordpress.org/robertg/) added that this isn’t including the 225 (approx) in his PR ## Open Floor / CSS Link Share * [@danfarrow](https://profiles.wordpress.org/danfarrow/) shared [An Interactive Guide to Keyframe Animations](https://www.joshwcomeau.com/animation/keyframe-animations/) * [@dryanpress](https://profiles.wordpress.org/dryanpress/) shared another great post from the same site [Designing Beautiful Shadows in CSS](https://www.joshwcomeau.com/css/designing-shadows/) Thanks everybody! [#core-css](https://make.wordpress.org/core/tag/core-css/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/nerrad/) [Darren Ethier (nerrad)](https://profiles.wordpress.org/nerrad/) 2:51 pm _on_ September 21, 2021 Tags: [coding style ( 6 )](https://make.wordpress.org/core/tag/coding-style/), [codingstandards ( 7 )](https://make.wordpress.org/core/tag/codingstandards/), [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), [proposal ( 38 )](https://make.wordpress.org/core/tag/proposal/)    # 󠀁[WordPress JavaScript Standards Change Proposal](https://make.wordpress.org/core/2021/09/21/wordpress-javascript-standards-change-proposal/)󠁿 _This post was authored by [@opr18](https://profiles.wordpress.org/opr18/) (Thomas Roberts)._ [During a recent WordPress #core-js meeting](https://wordpress.slack.com/archives/C5UNMSU4R/p1631029579073200) there was a discussion about updating the JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. [https://www.javascript.com](https://www.javascript.com/) coding standard. The specific update that is being proposed is to change the rules relating to comments. Currently, the standard reads: > Comments come before the code to which they refer, and should always be preceded > by a blank line. Capitalize the first letter of the comment, and include a period > at the end when writing full sentences. There must be a single space between the > comment token (//) and the comment text. The proposal is that the new wording should be: > Comments come before the code to which they refer, and should always be preceded > by a blank line. Unless writing a linter override, or a `@see` type comment, capitalize > the first letter of the comment, and include a period at the end. There must be > a single space between the comment token (//) and the comment text. The problem with the current guideline is that it is not enforceable by automated tools. It is hard for linting tools to easily distinguish between what is and isn’t a full sentence in the context of code comments. Code reviews can quickly fill up with noisy comments and suggestions to capitalise or add periods to code comments. If this were fixable with a linting rule then these comments wouldn’t be necessary. There are instances where it may not make sense to write in sentence case, for example: adding linter overrides or writing `see` comments where the comment may just be the name of a method or file, etc. so we would not enforce the rule on these types of comments. If this guideline were to be amended, there would be several instances of code in the 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/) repository alone that do not follow it. It would be necessary to create a PR that fixes all of these issues. Because the change only relates to comments, a single PR can be made addressing all instances of comments that don’t follow the guideline, because the rule relates to comments only, this would have no impact on functionality so minimal testing would be required. WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. currently uses JSHint for linting JavaScript files, and it does not appear that even the existing style guideline is enforced. Even so, if efforts were made to move to ESLint in WordPress core, implementing a fix for any comments that do not follow the standard should be straightforward. Initially the rule could be enforced as a “warning” while the PR to fix the issues is completed and after it has been merged the rule could graduate to an “error”. Here is a draft PR demonstrating the punctuation aspect of the proposed change: https://github.com/WordPress/gutenberg/pull/34964 As a part of next steps, this post is looking for feedback on: * How do you feel about the proposed changes to the wording of the standard? * Are there any concerns about the plan for implementing this change? This proposal is open for feedback until **October 5th, 2021** at which point a final decision will be made during [#core-js](https://make.wordpress.org/core/tag/core-js/) office hours that day. [#coding-style](https://make.wordpress.org/core/tag/coding-style/), [#codingstandards](https://make.wordpress.org/core/tag/codingstandards/), [#proposal](https://make.wordpress.org/core/tag/proposal/) [ ](https://profiles.wordpress.org/paaljoachim/) [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/) 2:48 pm _on_ September 21, 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/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/)    # 󠀁[Editor Chat Agenda: 22 September 2021](https://make.wordpress.org/core/2021/09/21/editor-chat-agenda-22-september-2021/)󠁿 Facilitator and notetaker: @jorgefilipecosta This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, September 22 2021, 04:00 PM GMT+1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210922T16&p1=187&ah=1). _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/)._ * 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.6 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/16/?output_format=md#alpha-beta). will be released Wednesday. * [Whats next in Gutenberg: Mid-September 2021.](https://make.wordpress.org/core/2021/09/17/whats-next-in-gutenberg-mid-september-2021/) * WordPress 5.9 [Preliminary Roadmap](https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/). * Updates based on [updated scope for site editing projects](https://github.com/WordPress/gutenberg/issues/33094): - Navigation 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. & Navigation Editor. - Template editor. - Patterns. - Styling. - Mobile Team. * Task Coordination. * Open Floor. If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion: * If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself. * 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. [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-agenda](https://make.wordpress.org/core/tag/core-editor-agenda/), [#meeting](https://make.wordpress.org/core/tag/meeting/) [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 11:10 am _on_ September 21, 2021 Tags: [core-auto-updates ( 37 )](https://make.wordpress.org/core/tag/core-auto-updates/), [updater ( 21 )](https://make.wordpress.org/core/tag/updater/), [upgrade-install ( 32 )](https://make.wordpress.org/core/tag/upgrade-install/) # 󠀁[Upgrade/Install component meeting agenda for September 21, 2021](https://make.wordpress.org/core/2021/09/21/upgrade-install-component-meeting-agenda-for-september-21-2021/)󠁿 The next meeting is scheduled on [Tuesday, September 21, 2021, at 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210921T1700) and will take place on the [#core-auto-updates](https://wordpress.slack.com/archives/CULBN711P/p1583863308013300) 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. The aim of the meeting is to discuss the four years old ticketticket Created for both bug reports and feature development on the bug tracker. [#22316](https://core.trac.wordpress.org/ticket/22316) and two PRs that have been proposed to solve it. Let’s try something different! A Zoom call 🙂 I will drop the link to it in the Slack channel at the start of the meeting. Got something to propose for the agenda? Please leave a comment below. See you there! [#core-auto-updates](https://make.wordpress.org/core/tag/core-auto-updates/), [#updater](https://make.wordpress.org/core/tag/updater/), [#upgrade-install](https://make.wordpress.org/core/tag/upgrade-install/) [ ](https://profiles.wordpress.org/ajitbohra/) [Ajit Bohra](https://profiles.wordpress.org/ajitbohra/) 6:56 pm _on_ September 20, 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 ( 223 )](https://make.wordpress.org/core/tag/editor/), [gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/), [meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/)    # 󠀁[Editor chat summary: Wednesday, 15 September 2021](https://make.wordpress.org/core/2021/09/20/editor-chat-summary-wednesday-15-september-2021/)󠁿 This post summarizes the latest weekly Editor meeting ([agenda](https://make.wordpress.org/core/2021/09/14/editor-chat-agenda-15-september-2021/), [slack transcript](https://wordpress.slack.com/archives/C02QB2JS7/p1631714496006000)), held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) 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, on[ Wednesday, September 15, 2021, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210915T1400). ## WordPress 5.9 [Preliminary Roadmap](https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/), a quick overview of the main areas and features currently underway for 5.9 in 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/). ## Gutenberg 11.5.0 Gutenberg 11.5.0 was released on 16th September, this update includes 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. Gap support, improved support for Flex Layouts, performance improvements, and additional design tools. Check out the [release post](https://make.wordpress.org/core/2021/09/17/whats-new-in-gutenberg-11-5-16-september/) for a complete list of features and enhancements: ## Monthly Plan The monthly update containing the high-level items that Gutenberg contributors are focusing on for June are: * Template Editor * Patterns * Global Styles and 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. UIUI User interface * Design Tools * Navigation Block * Navigation Editor For a detailed plan check out [monthly priorities](https://make.wordpress.org/core/2021/09/17/whats-next-in-gutenberg-mid-september-2021/) post. ## Updates on the key projects Nav Editor: [@get_dave](https://profiles.wordpress.org/get_dave/) * Work is still progressing on migrating the navigation editor fully over to the 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/). The REST API changes have been merged, and now the front end code is being updated. * Lots of UI changes this week with the editor top bar being updated, the main block inserter added, and fixes to the block’s styles. * Good discussion underway on [how to provide backwards compatibility for custom fields on the existing Menus screen](https://github.com/WordPress/gutenberg/issues/31551). * Up next: We’re [looking into bulk adding links](https://github.com/WordPress/gutenberg/issues/31667), and [using theme.json to control aspects of the navigation block](https://github.com/WordPress/gutenberg/pull/34784). * Also in general, we’re always looking for contributors to help work on the Nav Editor and bloc, if you’re interested please head over to the [#feature-navigation-block-editor Slack channel](https://wordpress.slack.com/archives/C01KDAZJMQ9). Look forward to seeing you there. Rest API: [@zieladam](https://profiles.wordpress.org/zieladam/) * For the REST API changes, [saving menu items using rest API](https://github.com/WordPress/gutenberg/pull/34541). * As a nice side-effect, we might get a simple 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. for saving changes in any editor that acts on entities through blocks (e.g. the widgets editor). Mobile:** ** [@hypest](https://profiles.wordpress.org/hypest/) _Shipped_ * Inline preview support for Instagram, Vimeo. Now supporting all  5 most-used providers (YouTube, Twitter, WordPress, Instagram, Vimeo). _Fixes_ * Refresh embed preview when switching light/dark mode * Use device’s localeLocale A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese( Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English. in embed previews * Ensure inserter button is in view when RTL * Translate column block’s control labels _In Progress_ * Embed block. * GSS Font size, line height, colors. ## Task Coordination _Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something._ [@mamaduka](https://profiles.wordpress.org/mamaduka/) * [Refactored](https://github.com/WordPress/gutenberg/pull/33695) Post Author component for editor, It now only makes _one request to render the component instead of four_. * Helping with [Navigation Editor issues and PRs](https://github.com/WordPress/gutenberg/pull/33725). * Created an issue with some suggestions to [improve Core Data `cacheKey`](https://github.com/WordPress/gutenberg/pull/33725). Currently working on POC PR. * I would love to get feedback/review on [adding basic child theme support to FSE](https://github.com/WordPress/gutenberg/pull/33725). [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) * [Updated justification control](https://github.com/WordPress/gutenberg/pull/34651) in flex layout. In progress: * [Add icons to block settings](https://github.com/WordPress/gutenberg/pull/34785) dropdown. * [Show “none” as an alignment option ](https://github.com/WordPress/gutenberg/pull/34710) and use contextual text to clarify settings. [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) * Worked on the task to replace the color picker component namely enhance its design and started working on replacing tinycolor with colord. * Need some reviews on tinycolor to colord replacements: - [replace on contrast checker](https://github.com/WordPress/gutenberg/pull/34605). - [replace on block editor styles](https://github.com/WordPress/gutenberg/pull/34616). * Simple PR’s to get the ball rolling as long as one is approved I guess we can merge multiple similar ones. * Worked on implement the new custom gradient picker design. * Currently working on the new color palette editor. * For the next week I will continue with improving the global styles related components. * Will see how can I best help the effort of implementing the new 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. with its navigation system. * Will try to dedicate attention to old PR’s I have that are mostly ready. * Mosaic view and block awareness of global styles I hope to merge them so my head becomes free for other challenges and we can submit follow ups on them. [@zieladam](https://profiles.wordpress.org/zieladam/) * My main focus are the[ REST API changes for the navigation editor](https://github.com/WordPress/gutenberg/pull/34541) [@mciampini](https://profiles.wordpress.org/mciampini/) An update from the folks working on the components package _Shipping:_ * The `@wordpress/components` contributor guidelines [have been greatly expanded](https://github.com/WordPress/gutenberg/pull/33960), including [a new section on compound components](https://github.com/WordPress/gutenberg/pull/34697). * A [new Storybook story was added](https://github.com/WordPress/gutenberg/pull/34708) demonstrating some of the composition patterns and features of the [recently introduced ](https://github.com/WordPress/gutenberg/pull/33701)` ItemGroup`[ component](https://github.com/WordPress/gutenberg/pull/33701), which factors heavily in the [Global Styles designs](https://github.com/WordPress/gutenberg/issues/34574). _In Progress:_ * Further enhancements to the [new color picker design](https://github.com/WordPress/gutenberg/pull/34598) and [interactions](https://github.com/WordPress/gutenberg/pull/34601) and [the new gradient picker design](https://github.com/WordPress/gutenberg/pull/34712). * Some further [planning for the Typography Panel features](https://github.com/WordPress/gutenberg/pull/34028) in Global Styles, which will use the same `ToolsPanel` component recently introduced alongside the new Dimensions Panel. [@oandregal](https://profiles.wordpress.org/oandregal/) * Have been working on assorted things: - Alignments: add [wide control](https://github.com/WordPress/gutenberg/pull/34586) only if theme provides wideSize, [fix for floats](https://github.com/WordPress/gutenberg/pull/34635), - Link color: fix for [clearing the class](https://github.com/WordPress/gutenberg/pull/34700), fix for [link color in containers](https://github.com/WordPress/gutenberg/pull/34689), - Cache issues for global styles [stylesheet](https://github.com/WordPress/gutenberg/pull/34704), [theme.json](https://github.com/WordPress/gutenberg/pull/34540). - Adding support for [disabling](https://github.com/WordPress/gutenberg/pull/34420) text and background color controls via theme.json [@annezazu](https://profiles.wordpress.org/annezazu/) * Mainly have been doing some light triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., amplifying [the current block theme switching exploration](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/). * Working on updating 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. description (PR coming). * Ran a hallway [hangout for FSE items](https://make.wordpress.org/test/2021/09/10/hallway-hangout-discussion-on-full-site-editing-issues-prs-designs-10-september/). * Hoping to ship an additional coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor improvement post too in the next week. [@get_dave](https://profiles.wordpress.org/get_dave/) This week, I’ve have been mostly workin’ on: * Adding Global Inserter to Navigation Editor screen. * Experimenting with Theme JSON as means to control many aspect of Navigation block. * Fixes from the `High` priority section of Nav Editor tracking issue. * Various Link UI issues. * Added “help” descriptions for the various HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. element options on the Group block. [@mkaz](https://profiles.wordpress.org/mkaz/) * I’m working on a couple minor issues, [adding shortcut key to Preview Post](https://github.com/WordPress/gutenberg/issues/25021) but requires some refactoring. * The other is [adding explanatory text to the Quick Inserter](https://github.com/WordPress/gutenberg/issues/24007) when used in InnerBlocks, but still needs some further questions answered to have a clear path forward. ## Open Floor [@get_dave](https://profiles.wordpress.org/get_dave/) * Could whoever is running the Gutenberg Plugin release please let me know how they found the [automated changelog feature grouping](https://github.com/WordPress/gutenberg/pull/33229)? I worked on [a couple of PRs on that](https://github.com/WordPress/gutenberg/pull/33625) and I’m curious to know whether anything could * Working on how to make the Nav Editor more resilient to changes in the Navigation** block**. Currently it’s very difficult and not at all resilient. - One route I’m exploring is [using Theme JSON to control the features of the Nav block](https://github.com/WordPress/gutenberg/pull/34784). My proposal does two things that I’d like some input on:1. opens up `theme. json` for _extensibility_ by developers via **hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same./filters**. - Allows `theme.json` to control features that are **unique to particular blocks**( as opposed to things that are common across all blocks such as spacing). - I’d really like to understand whether this is within the intended scope for Theme JSON. - This has large utility outside Nav Editor because I imagine Themers wanting to be able to control multiple facets of blocks (and not just common things such as padding/margin…etc) without having to use complex hooks/filters - some dicussion but no conclusion [read complete discussion](https://wordpress.slack.com/archives/C02QB2JS7/p1631716812049200). [@paaljoachim](https://profiles.wordpress.org/paaljoachim/) * The following comment made by [@a4jpcom](https://profiles.wordpress.org/a4jpcom/) was posted to last weeks Core Editor Chat agenda after the chat was held. - The inserter (add block – the line with plus mark) is missing above the top inserted block. - [Toggle block inserter](https://wordpress.org/support/topic/blocks-cant-be-added-at-the-top-of-pages/#post-14847846) doesn’t help here either. - Related [issues](https://github.com/WordPress/gutenberg/issues/22801#issuecomment-913302262). - You currently have to add a block under the top inserted block then move it above the top block each time. It would be nice to get this fixed. - If the line that said add block were above the first block added it would just take one click to add new blocks, which is very nice. * I would like to bring up one more thing that would be nice to get some eyes on again.  - Moving the post/page title to the top bar, so that users can choose to have the title in the layout. Here is a [PR](https://github.com/WordPress/gutenberg/pull/31288) which has stalled. [Read complete transcript](https://wordpress.slack.com/archives/C02QB2JS7/p1631714496006000) [#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#editor](https://make.wordpress.org/core/tag/editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/) [ ](https://profiles.wordpress.org/kirasong/) [Kira Schroder](https://profiles.wordpress.org/kirasong/) 7:56 pm _on_ September 17, 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.5? (16 September)](https://make.wordpress.org/core/2021/09/17/whats-new-in-gutenberg-11-5-16-september/)󠁿 It’s been two weeks since 11.4, so it’s time for another 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, 11.5! This update includes 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. Gap support, improved support for Flex Layouts, performance improvements, and additional design tools. ## Theme / Block Gap Support [Block Gap support](https://github.com/WordPress/gutenberg/pull/33991) adds the ability for blocks to opt-in to a control that allows users to choose the distance between items within a block. The groundwork for this feature was [introduced in 11.4](https://make.wordpress.org/core/2021/09/01/whats-new-in-gutenberg-11-4-1-september/), and was initially opt-out for themes. [Following feedback](https://github.com/WordPress/gutenberg/pull/33812#issuecomment-910164634), this feature [is now opt-in](https://github.com/WordPress/gutenberg/pull/34491#issuecomment-913549683). Thanks so much for the testing and feedback! With Block Gap support in place, it has also been added to the [Columns](https://github.com/WordPress/gutenberg/pull/34456), [Title](https://github.com/WordPress/gutenberg/pull/34570), and [Navigation](https://github.com/WordPress/gutenberg/pull/32367) blocks. Buttons in the the Buttons Block move closer together or farther apart as the Block Gap is changed. ## Flex Layout Highlights Following the [introduction of Flex Layout](https://github.com/WordPress/gutenberg/pull/33359) in [11.2.0](https://make.wordpress.org/core/2021/08/05/whats-new-in-gutenberg-11-2-0-4-august/), now Flex Layouts are supported within the [Social Links](https://github.com/WordPress/gutenberg/pull/34493) and [Group](https://github.com/WordPress/gutenberg/pull/34535) blocks! The Social Links block now has a ‘flex’ justification option, for automatic best-fit.  There is also a [new variation of the Group block](https://github.com/WordPress/gutenberg/pull/34535) that allows for flex layout. You can try it out by choosing “Row” from the block inserter. Social Icons change flow when flex justification is selected. ## Site Title and Logo Inside Navigation Block It’s now possible to [build your site logo or title directly into menus](https://github.com/WordPress/gutenberg/pull/33316), enabling new design possibilities! Insert, and modify the title or logo that you prefer, using design tools, then re-order for your ideal look. A Site Logo is added to a Navigation Block, then resized and placed. ## Global Styles  Global styles are [now available to themes by default](https://github.com/WordPress/gutenberg/pull/34334), allowing block, theme, and patterns to have a reliable set of styles provided by coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Themes are now able to [selectively disable text and background colors](https://github.com/WordPress/gutenberg/pull/34420). This allows theme authors to provide exactly the experience they’d like to provide users, whether allowing custom colors, gradients, or only their curated selections. ## Other Notable Highlights The Heading Levels menu [has been redesigned](https://github.com/WordPress/gutenberg/pull/32926), and is now vertical, making it easier to visualize the hierarchy. There is a new setting to [customize the Next and Previous Page indicators](https://github.com/WordPress/gutenberg/pull/33656) in the Query Pagination block, allowing the addition of an arrow or a chevron to your designs. [[ New vertical Heading Levels menu, with H2 selected. ## 11.5.0 ### Features **Design Tools** * Block Support: Add gap block support feature. ([33991](https://github.com/WordPress/gutenberg/pull/33991)) ### Enhancements **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)** * Font weight screen reader description. ([34312](https://github.com/WordPress/gutenberg/pull/34312)) **Block Editor** * Media Placeholder: Change media URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org input type to allow a local URL path. ([29138](https://github.com/WordPress/gutenberg/pull/29138)) **Block Library** * Columns Block: Use `blockGap` between Columns blocks. ([34456](https://github.com/WordPress/gutenberg/pull/34456)) * Group Block: Add a row variation. ([34535](https://github.com/WordPress/gutenberg/pull/34535)) * Heading Block: Vertical heading levels menu. ([32926](https://github.com/WordPress/gutenberg/pull/32926)) * Navigation Block: Allow Site Title and Logo inside Navigation block. ([33316](https://github.com/WordPress/gutenberg/pull/33316)) * Navigation Block, List View: Do not show appender and avoid closing the modal on block select. ([34337](https://github.com/WordPress/gutenberg/pull/34337)) * Navigation Block: Remove horizontal and vertical navigation block variations from inserter. ([34614](https://github.com/WordPress/gutenberg/pull/34614)) * Navigation Block: Use gap instead of margin. ([32367](https://github.com/WordPress/gutenberg/pull/32367)) * Post Author Block: Add duotone suport. ([34408](https://github.com/WordPress/gutenberg/pull/34408)) * Query Pagination Next/Previous: Add an arrow attribute and sync next/previous block’s arrow. ([33656](https://github.com/WordPress/gutenberg/pull/33656)) * Site Logo Block: Update block description to be concise. ([34471](https://github.com/WordPress/gutenberg/pull/34471)) * Site Title Block: Update block description to be concise. ([34475](https://github.com/WordPress/gutenberg/pull/34475)) * Social Links Block: Use the new `flex` layout. ([34493](https://github.com/WordPress/gutenberg/pull/34493)) * Video Block: Use existing video poster image on insert. ([34415](https://github.com/WordPress/gutenberg/pull/34415)) **Components** * MenuItem: Add right padding for unchecked radio and checkbox items. ([34406](https://github.com/WordPress/gutenberg/pull/34406)) * ToggleGroupControl: Update stories to use knobs. ([34497](https://github.com/WordPress/gutenberg/pull/34497)) **Core Data** * Add `isRawAttribute` to entity configuration. ([34388](https://github.com/WordPress/gutenberg/pull/34388)) **Design Tools** * Add wide alignment control only if theme provides `layout.wideSize`. ([34586](https://github.com/WordPress/gutenberg/pull/34586)) * Update justification control in `flex` layout. ([34651](https://github.com/WordPress/gutenberg/pull/34651)) * ToolsPanel: Change icon from horizontal to vertical ellipsis. ([34369](https://github.com/WordPress/gutenberg/pull/34369)) **Full Site Editing** * Limit FSE adminadmin (and super admin) notices to the Themes screen. ([34353](https://github.com/WordPress/gutenberg/pull/34353)) **Global Styles** * Allow disabling `text` and `background` color via `theme.json`. ([34420](https://github.com/WordPress/gutenberg/pull/34420)) * Make global styles available to all themes. ([34334](https://github.com/WordPress/gutenberg/pull/34334)) **i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/2021/page/16/?output_format=md#l10n). Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.** * Add context to ‘none’ strings for better translations. ([34341](https://github.com/WordPress/gutenberg/pull/34341)) * Make permalinks documentation URL translatable. ([34282](https://github.com/WordPress/gutenberg/pull/34282)) **Post Editor** * Expose `ThemeSupportCheck` component. ([20506](https://github.com/WordPress/gutenberg/pull/20506)) * Title block gap. ([34570](https://github.com/WordPress/gutenberg/pull/34570)) **Themes** * Add default editor styles applied to themes without `theme.json` and without editor styles. ([34439](https://github.com/WordPress/gutenberg/pull/34439)) **Widgets Editor** * Add ‘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. Group’ block to widgets screens. ([34484](https://github.com/WordPress/gutenberg/pull/34484)) * Legacy widget rendering endpoint. ([34230](https://github.com/WordPress/gutenberg/pull/34230)) ### New APIs **Design Tools** * Allow themes with `theme.json` to opt-out of block gap styles. ([34491](https://github.com/WordPress/gutenberg/pull/34491)) ### Bug Fixes **Accessibility** * Fix button block focus trap after a URL has been added. ([34314](https://github.com/WordPress/gutenberg/pull/34314)) **Block Editor** * Fix menu item padding regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/2021/page/16/?output_format=md#blocker). Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.. ([34435](https://github.com/WordPress/gutenberg/pull/34435)) * Fix text-menu min widths. ([34532](https://github.com/WordPress/gutenberg/pull/34532)) * Keep id on paste if internal link points to it. ([31107](https://github.com/WordPress/gutenberg/pull/31107)) * Fix caret position on block merging. ([34169](https://github.com/WordPress/gutenberg/pull/34169)) **Block Library** * Heading Block, Paragraph Block: Fix long strings of text without spaces overflow the block. ([34222](https://github.com/WordPress/gutenberg/pull/34222)) * Gallery Block: Fix 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. with stalled upload when image size too large. ([34371](https://github.com/WordPress/gutenberg/pull/34371)) * Gallery Block: Fix media placeholder height in site editor. ([34629](https://github.com/WordPress/gutenberg/pull/34629)) * Gallery Block: Fix problem with overflowing captions on new gallery block format.( [34402](https://github.com/WordPress/gutenberg/pull/34402)) * Latest Posts: Fix various 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 in development log. ([34428](https://github.com/WordPress/gutenberg/pull/34428)) * Navigation: Fix navigation block classname issues. ([34344](https://github.com/WordPress/gutenberg/pull/34344)) * Navigation: Fix Page List styles inside responsive Navigation. ([34517](https://github.com/WordPress/gutenberg/pull/34517)) * Navigation: Fix responsive menu height regression. ([34488](https://github.com/WordPress/gutenberg/pull/34488)) * Navigation: Fix submenu layout in navigation page list. ([34342](https://github.com/WordPress/gutenberg/pull/34342)) * Navigation: Fix submenus to only take up space when visible. ([34382](https://github.com/WordPress/gutenberg/pull/34382)) * Navigation: Fix undo/redo ‘trap’ in navigation link block. ([34565](https://github.com/WordPress/gutenberg/pull/34565)) * Site Title: Allow empty title in edit mode. ([34274](https://github.com/WordPress/gutenberg/pull/34274)) * Social Links Block: Fix deprecation. ([34639](https://github.com/WordPress/gutenberg/pull/34639)) * Video Block: Fix `TypeError` when removing poster. ([34411](https://github.com/WordPress/gutenberg/pull/34411)) **Components** * Align labels on focal point picker position controls above the inputs. ([34209](https://github.com/WordPress/gutenberg/pull/34209)) * Check if in browser env before calling `CSS.supports`. ([34572](https://github.com/WordPress/gutenberg/pull/34572)) * Combobox Component: Only force expanded state if the input has focus. ([34090](https://github.com/WordPress/gutenberg/pull/34090)) * CustomSelectControl: Add describedBy fallback. ([34385](https://github.com/WordPress/gutenberg/pull/34385)) * DateTime Component: Fix sizing of help info. ([34370](https://github.com/WordPress/gutenberg/pull/34370)) * Fix `ToggleGroupControlBackdrop` not updating size when `isAdaptiveWidth` prop changes. ([34595](https://github.com/WordPress/gutenberg/pull/34595)) * Fix selected value computation in `CustomSelectControl` when no initial `value` is set. ([34490](https://github.com/WordPress/gutenberg/pull/34490)) * Fix subheadings from wrapping. ([34319](https://github.com/WordPress/gutenberg/pull/34319)) **Design Tools** * Border Controls: Display color indicator and check selected color. ([34467](https://github.com/WordPress/gutenberg/pull/34467)) * Border Support: Fix check for displaying border support panel. ([34516](https://github.com/WordPress/gutenberg/pull/34516)) * Gap block support: Force gap change to cause the block to re-render (fix Safari issue). ([34567](https://github.com/WordPress/gutenberg/pull/34567)) * Letter Spacing: Group letter spacing correctly under typography supports. ([34515](https://github.com/WordPress/gutenberg/pull/34515)) **Global Styles** * Fix block-level global styles color panels. ([34293](https://github.com/WordPress/gutenberg/pull/34293)) * Font Appearance Control: Fix error in global styles for Site Title in TT1-Blocks.( [34520](https://github.com/WordPress/gutenberg/pull/34520)) **MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Boxes** * Change default value of `enableCustomFields` to `undefined`. ([33931](https://github.com/WordPress/gutenberg/pull/33931)) * Fix metaboxMetabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. reordering. ([30617](https://github.com/WordPress/gutenberg/pull/30617)) **Packages** * Blocks: Register block when 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. value provided for the icon. ([34350](https://github.com/WordPress/gutenberg/pull/34350)) * Core Data: Add ‘include’ to the query key. ([34583](https://github.com/WordPress/gutenberg/pull/34583)) * Core Data: Use `resolveSelect` instead of `select` in `saveEntityRecord`. ([34584](https://github.com/WordPress/gutenberg/pull/34584)) * Interface: Block Toolbar & Popover component – Prevent sticky position from causing permanently obscured areas of the selected block. ([33981](https://github.com/WordPress/gutenberg/pull/33981)) * Scripts: Only use svgr/webpack in js files. ([34394](https://github.com/WordPress/gutenberg/pull/34394)) * Scripts: Convert legacy entry point arguments for compatibility with webpack 5. ([34264](https://github.com/WordPress/gutenberg/pull/34264)) **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/)** * Default batch processor: Respect the batch endpoint’s `maxItems`. ([34280](https://github.com/WordPress/gutenberg/pull/34280)) **Widgets Editor** * Fix Block Settings 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. unexpectedly collapsing. ([34543](https://github.com/WordPress/gutenberg/pull/34543)) * Legacy widget’s preview functionality is broken when the page is moved. ([34384](https://github.com/WordPress/gutenberg/pull/34384)) * Prevent focus trap in Legacy Widget block’s preview 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..( [33614](https://github.com/WordPress/gutenberg/pull/33614)) ### Performance **Block Editor** * Improve the `getBlock` and `getBlocks` performance. ([34241](https://github.com/WordPress/gutenberg/pull/34241)) * Remove duplicated `useValidAlignment` hook. ([34593](https://github.com/WordPress/gutenberg/pull/34593)) **Core Data** * Move locks state from store to local variable. ([34374](https://github.com/WordPress/gutenberg/pull/34374)) **Global Styles** * Remove colors classes from the packages that are already provided by global styles.( [34510](https://github.com/WordPress/gutenberg/pull/34510)) ### Experiments **Navigation Editor** * Add undo redo buttons in navigation editor. ([34533](https://github.com/WordPress/gutenberg/pull/34533)) * Decode entities in the menu names. ([34263](https://github.com/WordPress/gutenberg/pull/34263)) * Disable “block-nav-menus” feature for the purposes of removing the “experimental” status on the Navigation Editor. ([34444](https://github.com/WordPress/gutenberg/pull/34444)) * Preload menu REST API requests on new navigation editor. ([34364](https://github.com/WordPress/gutenberg/pull/34364)) * Update navigation editor placeholder. ([34568](https://github.com/WordPress/gutenberg/pull/34568)) ### Documentation **Handbook** * Replace `withSelect` references with `useSelect`. ([34549](https://github.com/WordPress/gutenberg/pull/34549)) * Updated Template Section copy. ([34383](https://github.com/WordPress/gutenberg/pull/34383)) * Update block variations documentation about `block` scope. ([34455](https://github.com/WordPress/gutenberg/pull/34455)) **Packages** * Blocks: Correct typo in Blocks Documentation. ([34396](https://github.com/WordPress/gutenberg/pull/34396)) * Componentes: Fix/update documentation alignment matrix control. ([34624](https://github.com/WordPress/gutenberg/pull/34624)) * Componentes: Update `DuotonePicker` documentation for accuracy. ([34494](https://github.com/WordPress/gutenberg/pull/34494)) * Eslint: Add `no-unsafe-wp-apis` to rules list in the documentation. ([34416](https://github.com/WordPress/gutenberg/pull/34416)) * Prettier: Correct syntax in `README.md` for `prettier-config`. ([34600](https://github.com/WordPress/gutenberg/pull/34600)) ### Code Quality **Block Editor** * Code cleanup to the `getBlock` refactoring. ([34326](https://github.com/WordPress/gutenberg/pull/34326)) * Ensure that `blockType` is defined when accessing `apiVersion`. ([34346](https://github.com/WordPress/gutenberg/pull/34346)) * Migrate `lightBlockWrapper` support to `apiVersion` for blocks. ([34459](https://github.com/WordPress/gutenberg/pull/34459)) * Fix Animated warning log. ([34197](https://github.com/WordPress/gutenberg/pull/34197)) * Rich Text: Replace global event handlers with local ones. ([34492](https://github.com/WordPress/gutenberg/pull/34492)) * Rich text (core): OnFocus method can be replaced with HTMLElement.focus. ([32054](https://github.com/WordPress/gutenberg/pull/32054)) * Use Setting: Consolidate the `PATHS_WITH_MERGE` constant to one instance. ([34407](https://github.com/WordPress/gutenberg/pull/34407)) **Block Library** * Gallery Block: Add docblockdocblock (phpdoc, xref, inline docs) comments to the new gallery hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same..( [34562](https://github.com/WordPress/gutenberg/pull/34562)) * Gallery Block: Remove IE specific CSSCSS Cascading Style Sheets. hacks. ([34372](https://github.com/WordPress/gutenberg/pull/34372)) * Button Block: Replace global shortcut event handlers with local ones. ([34498](https://github.com/WordPress/gutenberg/pull/34498)) * Navigation Block: Refactor to use generic classnames. ([34171](https://github.com/WordPress/gutenberg/pull/34171)) * Navigation Link Block: Replace global shortcut event handlers with local ones.( [34500](https://github.com/WordPress/gutenberg/pull/34500)) * Gallery Block: Remove redundant css selector. ([34277](https://github.com/WordPress/gutenberg/pull/34277)) **Components** * CustomGradientBar: Replace global shortcut event handlers with local ones. ([34505](https://github.com/WordPress/gutenberg/pull/34505)) * Guide: Replace global shortcut event handlers with local ones. ([34503](https://github.com/WordPress/gutenberg/pull/34503)) * Navigate regions: Use React events for shortcuts (portal bubbles & contextual).( [33633](https://github.com/WordPress/gutenberg/pull/33633)) * Rename `PolymorphicComponent*` types to `WordPressComponent*`. ([34330](https://github.com/WordPress/gutenberg/pull/34330)) * Simplify Modal with hooks. ([34412](https://github.com/WordPress/gutenberg/pull/34412)) * Simplify & polish heading levels. ([34378](https://github.com/WordPress/gutenberg/pull/34378)) **Core Data** * Fix linting errors. ([34596](https://github.com/WordPress/gutenberg/pull/34596)) * Fix linting error in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. ([34464](https://github.com/WordPress/gutenberg/pull/34464)) * Migrate `canUser` resolver to thunks. ([34580](https://github.com/WordPress/gutenberg/pull/34580)) * Migrate `entities.js` to thunks. ([34582](https://github.com/WordPress/gutenberg/pull/34582)) * Migrate `getAutosaves` resolver to thunks. ([34581](https://github.com/WordPress/gutenberg/pull/34581)) * Migrate `getEntityRecord` resolver to thunks. ([34576](https://github.com/WordPress/gutenberg/pull/34576)) * Migrate `getEntityRecords` resolver to thunks. ([34578](https://github.com/WordPress/gutenberg/pull/34578)) * Migrate resolvers to thunks: `GetAuthors`, `_getCurrentUser`, `__getCurrentTheme`,` __getThemeSupports`. ([34579](https://github.com/WordPress/gutenberg/pull/34579)) * Refactor `deleteEntityRecord` to use thunks instead of generators. ([34386](https://github.com/WordPress/gutenberg/pull/34386)) * Refactor `editEntityRecord`, undo, and redo to be thunks instead of generators.( [34387](https://github.com/WordPress/gutenberg/pull/34387)) * Remove the `PROCESS_PENDING_LOCK_REQUESTS` action. ([34343](https://github.com/WordPress/gutenberg/pull/34343)) * Refactor `saveEntityRecord` from `redux-rungen` to async thunks. ([33201](https://github.com/WordPress/gutenberg/pull/33201)) * Remove extraction of raw values in `saveEntityRecords`. ([34502](https://github.com/WordPress/gutenberg/pull/34502)) **Other Packages** * Compose, useDropZone: Ensure drag event targets `HTMLElement`. ([34272](https://github.com/WordPress/gutenberg/pull/34272)) * Editor: Replace hardcoded store key. ([34296](https://github.com/WordPress/gutenberg/pull/34296)) * Env: Clarify config error within `parse-config.js`. ([34322](https://github.com/WordPress/gutenberg/pull/34322)) * Post Editor: Fix gray W menu color. ([34318](https://github.com/WordPress/gutenberg/pull/34318)) * URL: Add `getFilename` method to the URL package. ([34313](https://github.com/WordPress/gutenberg/pull/34313)) ### Tools **Build Tooling** * ESLint: Add `useSelect` to direct function calls list. ([34301](https://github.com/WordPress/gutenberg/pull/34301)) * ESLint: Update error message for `@emotion/css` with info about the `useCx` hook.( [34418](https://github.com/WordPress/gutenberg/pull/34418)) * Fix build hang on Windows 10. ([23589](https://github.com/WordPress/gutenberg/pull/23589)) * Linting: Remove global event listener warning. ([34528](https://github.com/WordPress/gutenberg/pull/34528)) * More work on the stability of the performance metrics. ([34229](https://github.com/WordPress/gutenberg/pull/34229)) **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.** * Added janw-me to the Codeowners for the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher FSE folder. ([32990](https://github.com/WordPress/gutenberg/pull/32990)) * Fix title missing in bug report form. ([34504](https://github.com/WordPress/gutenberg/pull/34504)) * Update bug form to use drop downs. ([34458](https://github.com/WordPress/gutenberg/pull/34458)) * Update the minimum supported WordPress version to 5.7. ([34536](https://github.com/WordPress/gutenberg/pull/34536)) **Testing** * Add unit tests for edit site editor utils. ([34401](https://github.com/WordPress/gutenberg/pull/34401)) * Debug e2e-tests in vscode. ([29788](https://github.com/WordPress/gutenberg/pull/29788)) * Jest Preset: Restore the default setting for the `verbose` option. ([34327](https://github.com/WordPress/gutenberg/pull/34327)) * Make `Test_Widget` compatible with `WP_Widget`. ([34355](https://github.com/WordPress/gutenberg/pull/34355)) ## 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.5 | 6.71s | 40.42ms | | Gutenberg 11.4 | 6.80s | 44.79ms | | WordPress 5.8 | 7.53s | 50.72ms | Kudos to all the contributors that helped with the release! 👏 _Thanks to [@beafialho](https://profiles.wordpress.org/beafialho/) and [@joen](https://profiles.wordpress.org/joen/) for the release post assets, [@priethor](https://profiles.wordpress.org/priethor/) for coordination and review, [@youknowriad](https://profiles.wordpress.org/youknowriad/) for release and tools wrangling, [@mamaduka](https://profiles.wordpress.org/mamaduka/) for answers and help throughout, and [@talldanwp](https://profiles.wordpress.org/talldanwp/) for inviting me to shadow a release in preparation._ [#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/) [ ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/) 7:52 pm _on_ September 17, 2021 Tags: [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [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? (Mid-September 2021)](https://make.wordpress.org/core/2021/09/17/whats-next-in-gutenberg-mid-september-2021/)󠁿 This 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** **in preparation for the [WordPress 5.9 Go/No Go](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/) that builds on the [focus areas for 5.9](https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/) and the [current Site Editing Scope](https://github.com/WordPress/gutenberg/issues/33094). 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/). --- ## Template Editor The Template Editor is the editing mode that allows you to create, assign, and edit 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. templates to posts and pages. There are different editors that leverage this editing mode, such as the Template Editor inside the Post Editor or the Site Editor available 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.. Current focuses include: * Add a [Mosaic View of Theme Templates](https://github.com/WordPress/gutenberg/issues/20477). * Iterate over the [Template Part Focus Mode](https://github.com/WordPress/gutenberg/issues/33926), including improving [the entry](https://github.com/WordPress/gutenberg/pull/34679) and [exit paths](https://github.com/WordPress/gutenberg/pull/34732) from the Site Editor. * Add a setting to [opt-out of block templates using `theme.json`](https://github.com/WordPress/gutenberg/issues/33500). **Follow along**: * [Site Editing Infrastructure and UI](https://github.com/WordPress/gutenberg/issues/27814) ## Patterns With the initial rollout of the new directory in WordPress 5.8, there’s a growing need to expand the inserter integration to accommodate broader categories of patterns and the experience of browsing them: * Add a [“Featured” category for Block Patterns](https://github.com/WordPress/gutenberg/issues/33046) and display it by default in the Inserter. * Add more well-crafted [Header and Footer patterns](https://github.com/WordPress/gutenberg/pull/31610). * Bugfixes are to be tackled, too, such as [patterns previews expanding endlessly on certain conditions](https://github.com/WordPress/gutenberg/issues/34729). **Follow along**: * [Pattern insertion tracking issue](https://github.com/WordPress/gutenberg/issues/31153) ## Global Styles and 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. UIUI User interface WordPress 5.8 introduced the scaffolding necessary for themes to control how various aspects of blocks render and how the interface is controlled. The natural next step ahead is to develop the user interface that will allow themers to build with these style properties directly in the editor and when allowed, users to interact with these style properties. * Manage [Default Colors, Theme Colors, and Custom Colors](https://github.com/WordPress/gutenberg/issues/29568). * Add [duotone `theme.json` styles support](https://github.com/WordPress/gutenberg/pull/34667). * Update the [ColorPicker component](https://github.com/WordPress/gutenberg/issues/34284) and [refine the design](https://github.com/WordPress/gutenberg/pull/34598). * Add the [Typography tools](https://github.com/WordPress/gutenberg/issues/34345) panel. **Follow along**: * [Block Styles Breakdown overview issue](https://github.com/WordPress/gutenberg/issues/20331) * [Global Styles Interface overview issue](https://github.com/WordPress/gutenberg/issues/34574) ## Design Tools Design tools encompass all tools related to the appearance of blocks and it ranges from colors, typography, alignments, and positioning, to filters like duotone, cropping, and background media creation of shared tools and its consistent application across blocks: * Consolidate [dimension controls across blocks](https://github.com/WordPress/gutenberg/issues/28356). * Allow [fluid typography](https://github.com/WordPress/gutenberg/issues/24480) to improve responsiveness, especially of patterns. * Add [typography formatting options to the Post Title ](https://github.com/WordPress/gutenberg/pull/31623) [B](https://github.com/WordPress/gutenberg/pull/31623)[lock](https://github.com/WordPress/gutenberg/pull/31623). * Add a [Gutter Size option to the Columns Block](https://github.com/WordPress/gutenberg/issues/10730). * Add [crop to Site Logo Block](https://github.com/WordPress/gutenberg/pull/31607). * Allow adding [inline text background color](https://github.com/WordPress/gutenberg/issues/20835). **Follow along**: * [Design Tools overview issue](https://github.com/WordPress/gutenberg/issues/33447) ## Navigation Block With the help of the Navigation block, editing a site’s navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. will be possible with a block interface and within a stand-alone block editor. This will allow users to edit not only the menu’s structure but also its design directly in context and without the need for previewing. The main current focuses in this project are: * Improve the experience of [creating simple navigations menus](https://github.com/WordPress/gutenberg/issues/34041). * Add a [submenu block](https://github.com/WordPress/gutenberg/pull/33775) to replace submenu functionality in Navigation Link blocks. * [Resolve any bugs](https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is%3Aissue+label%3A%22%5BType%5D+Bug%22+label%3A%22%5BBlock%5D+Navigation%22) that are found. **Follow along**: * [Navigation Block project board](https://github.com/WordPress/gutenberg/projects/58) * [Navigation Block tracking issue](https://github.com/WordPress/gutenberg/issues/27593) * [#feature-navigation-block-editor](https://wordpress.slack.com/archives/C01KDAZJMQ9) 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/) ## Navigation Editor The Navigation Editor aims to help expand what’s possible with menus while bringing block functionality to yet another part of WordPress while offering a more modern experience. Current efforts include: * [Consolidate the Navigation Editor top bar](https://github.com/WordPress/gutenberg/issues/31241) with the one used in the Site Editor. * Improve the[ List View drag and drop functionality](https://github.com/WordPress/gutenberg/pull/34022/). * [Allow `theme.json` to control the Navigation block within the Navigation Editor](https://github.com/WordPress/gutenberg/pull/34784), allowing the ability to 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. the Navigation block’s settings when it is being used inside the Navigation Editor. * Add an option to [bulk add entities of any type in the Navigation Editor](https://github.com/WordPress/gutenberg/issues/31667). **Follow along**: * [Navigation Editor project board](https://github.com/WordPress/gutenberg/projects/31) * [Navigation Editor tracking issue](https://github.com/WordPress/gutenberg/issues/29102) * [#feature-navigation-block-editor](https://wordpress.slack.com/archives/C01KDAZJMQ9) in WordPress.org Slack ## Other Projects Apart from these bigger projects, there are a wide arrange of focuses where contributors can help improve Gutenberg, including: * [Allow selection of entire rows and columns](https://github.com/WordPress/gutenberg/issues/16294) in the Table Block. * [Allow merge/unmerge cells](https://github.com/WordPress/gutenberg/issues/15821) in the Table Block. * [Improve the UX of crop/edit tools](https://github.com/WordPress/gutenberg/issues/23721) of the Image Block. * [Add duotone support ](https://github.com/WordPress/gutenberg/issues/34146)to the Site Logo Block. * [Move color controls to the toolbar](https://github.com/WordPress/gutenberg/issues/20837) in the Cover Block. **Follow along**: * [Medium Projects tracking issue](https://github.com/WordPress/gutenberg/issues/29503) --- ## Areas to be aware of **WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). US 2021**: * [WordCamp US 2021](https://us.wordcamp.org/2021/) is scheduled for October 1st, 2021 as an online event. Tickets are free and available [here](https://us.wordcamp.org/2021/tickets/)! **FSE Outreach Program**: * You can [help with the future of Block Theme Switching](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/) as part of the current FSE Program Exploration, open until September 29th. * The [summary for the ninth call for testing](https://make.wordpress.org/test/2021/09/03/fse-program-handling-highered-headers-summary/) for the FSE Outreach Program, focusing on Handling HigherEd Headers, is available as well. **Hallway Hangouts**: * A [Hallway Hangout discussing Full Site Editing issues, PRs, and designs](https://make.wordpress.org/test/2021/09/10/hallway-hangout-discussion-on-full-site-editing-issues-prs-designs-10-september/) took place on September 10th. * On September 16th, another Hallway Hangout [discussed adoption pathways for Full Site Editing](https://make.wordpress.org/test/2021/09/17/hallway-hangout-discussion-on-adoption-pathways-for-full-site-editing-16-september/). **Design**: * If you would like to see a design exploration on the Inspector 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., take a look at [this post exploring ways to improve the Document Status and Visibility sections](https://make.wordpress.org/design/2021/09/16/document-status-and-visibility/). --- ## 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: * CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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 to [@annezazu](https://profiles.wordpress.org/annezazu/) 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/) [ ](https://profiles.wordpress.org/milana_cap/) [Milana Cap](https://profiles.wordpress.org/milana_cap/) 2:34 pm _on_ September 15, 2021 Tags: [make.wordpress.org/docs ( 23 )](https://make.wordpress.org/core/tag/make-wordpress-org-docs/), [p2-xpost ( 212 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: [Announcement] New workflow for reporting documentation issues](https://make.wordpress.org/core/2021/09/15/xpost-announcement-new-workflow-for-reporting-documentation-issues/)󠁿 X-comment from [+make.wordpress.org/docs](https://make.wordpress.org/docs/): Comment on [[Announcement] New workflow for reporting documentation issues](https://make.wordpress.org/docs/2021/09/15/announcement-new-workflow-for-reporting-documentation-issues/#comment-40308) # Post navigation [← Older posts](https://make.wordpress.org/core/2021/page/17/?output_format=md) [Newer posts →](https://make.wordpress.org/core/2021/page/15/?output_format=md)