Make WordPress Core

Keyboard Shortcuts | Hide comment threads

Core Editor Improvement: Introducing the Widget Group Block

While the Block Widgets Editor was released with WordPress 5.8, the work to improve the experience hasn’t stopped to help even more folks use blocks to build out widget areas in an endless number of ways. The latest in a series of improvements comes with the launch of Gutenberg 11.5 that introduces a Widget Group block. This new block replicates the familiar experience of being able to add a title to a group of blocks and allows you to group any block, making it easier to move and layout content however you’d like. This both helps with compatibility for older themes when migrating over to the new editor and enables a more cohesive experience for building out widget areas.

For example, before this update, it was tricky to get the spacing right for adding a header above another set of blocks. Now, you can do that with ease:

Video showing how to use the Widget Group Block.

This also makes it a breeze to move collections of blocks into new widget areas: 

Video showing how you can drag and drop a collection of blocks within the Widget Group Block.

As always, you can also make these changes in the Customizer! For more general information about the Block Widgets Editor, check out the Dev note and the user documentation. To get involved in this work, head to #feature-widgets-block-editor and explore the GitHub tracking project to see what’s next. 

Props to @critterverse for the lovely videos! #core-editor, #core-editor-improvement, #feature-widgets-block-editor

Dev Chat Agenda for Sept 22, 2021

Here is the agenda for this week’s developer meeting to occur at Wednesday, September 22, 2021 at 08:00 PM UTC.

Blog Post Highlights and announcements

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

Next releases status update

  • Next minor release: WP 5.8.2
  • Next major release: 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 channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-8-2, #5-9, #agenda, #core, #dev-chat

A Week in Core – September 20, 2021

Welcome back to a new issue of Week in Core. Let’s take a look at what changed on Trac 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 🛠

Ticket numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Block editor

  • Cache global stylesheet by theme key – #53175

Build/Test Tools

  • Expect an absolute path in WP_TESTS_PHPUNIT_POLYFILLS_PATH constant – #46149
  • Improve messaging when PHPUnit Polyfills cannot be found – #46149
  • Improve messaging when PHPUnit Polyfills do not comply with version requirements – #46149
  • Make WP_TESTS_PHPUNIT_POLYFILLS_PATH more flexible – #46149
  • Reworks Tests_Option_Option::test_bad_option_names() into data provider – #53635

Bundled Themes

  • Twenty Eleven: Set a fixed height for search form when header image is added – #40398
  • Twenty Seventeen: Make blog header margin more specific on front page – #43628
  • Twenty Twenty-One: Add missing escaping for the “Secondary menu” label – #54127

Coding Standards

  • Code Modernization: Fix “passing null to non-nullable” deprecation notice in WP_Comment_Query::get_comment_ids()#53635
  • Rename the $arrURL variable to $parsed_url in WP_Http::request()#53359
  • Rename the $arrURL variable to $parsed_url in WP_Http_Cookie::__construct()#53359
  • Rename the $arrURL variable to $parsed_url in WP_Http_Streams::request()#53359
  • Rename the $processedHeaders variable to $processed_headers in WP_Http::request()#53359
  • Use strict comparison in wp-inclues/class-wp-http-cookie.php#53359

Documentation

  • Update description for the $wp_version global – #53413

Embeds

  • Add Pinterest as a trusted oEmbed provider – #53448

Internationalization

  • Add a translator comment to clarify the “Block HTML” string in the Block widget settings form – #54110

Media

  • Fix $content parameter default value in img_caption_shortcode()#53635

Options, Meta APIs

  • Fix “passing null to non-nullable” deprecations to (get|add|update|delete)_option()#53635

Upgrade/Install

  • Create a temporary backup of plugins and themes before updating – #51857

Props

Thanks to the 42 people who contributed to WordPress Core on Trac last week: @hellofromTonya (9), @jrf (8), @lucatume (4), @schlessera (4), @jeherve (4), @sabernhardt (3), @mukesh27 (3), @SergeyBiryukov (3), @pbearne (2), @azaozz (2), @dd32 (2), @muhammadfaizanhaidar (2), @NekoJonez (1), @Amieiro (1), @knutsp (1), @johnbillion (1), @namith.jawahar (1), @ayeshrajans (1), @laurelfulford (1), @hirofumi2012 (1), @jainnidhi (1), @mai21 (1), @fedepia (1), @Soean (1), @francina (1), @a2hosting (1), @Boniu91 (1), @richards1052 (1), @galbaras (1), @KZeni (1), @pento (1), @mikeschroder (1), @audrasjb (1), @TimothyBlynJacobs (1), @poena (1), @pbiron (1), @afragen (1), @aristath (1), @joedolson (1), @oandregal (1), @teucrium (1), @lukecavanagh (1).

Congrats and welcome to our 7 new contributors of the week: @NekoJonez, @Amieiro, @namith.jawahar, @mai21, @richards1052, @KZeni, and @teucrium ♥️

Core committers: @sergeybiryukov (11), @hellofromtonya (8), @pento (1), @jorgefilipecosta (1).

#5-8-2, #5-9, #core, #week-in-core

Is there a planned release date for 5.8.2?

Yeah, and we have a “WP 5.8.2 Update” item in today’s devchat agenda, the minor release squad is going to tell us more about the planning 🙂

CSS Chat Summary: 16 September 2021

The meeting took place here on Slack. @dryanpress facilitated and @danfarrow wrote up these notes.

CSS Custom Properties (#49930)

  • @dryanpress shared the working document and the trac ticket, for anybody new to the project
  • All core CSS files have now been claimed, and are either in progress or have a PR, however @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 raised the topic of skinning 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 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 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 added that, as there are several PRs now merged, anybody interested could start generating some ideas for these next steps right now
  • @dryanpress asked if we are still on target for an --experimental release in 5.9 which @ryelle confirmed we have good momentum for
  • @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 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 provided a few notes of the current state of the project
  • @danfarrow had quickly calculated there are now 127 custom properties in custom-properties.css. @robertg added that this isn’t including the 225 (approx) in his PR

Open Floor / CSS Link Share

Thanks everybody!

#core-css, #summary

WordPress JavaScript Standards Change Proposal

This post was authored by @opr18 (Thomas Roberts).

During a recent WordPress #core-js meeting there was a discussion about updating the JavaScript 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 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 core 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: http://wayback.fauppsala.se:80/wayback/20210922144316/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 office hours that day.

#coding-style, #codingstandards, #proposal

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.

This meeting is held in the #core-editor channel in the Making WordPress Slack.

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, #core-editor, #core-editor-agenda, #meeting

For task coordination: I’ve landed a couple of fixes for floats without container and themes without theme.json. Also helped with reviews and release duties (11.5.1).

Upgrade/Install component meeting agenda for September 21, 2021

The next meeting is scheduled on Tuesday, September 21, 2021 at 05:00 PM UTC and will take place on the #core-auto-updates Slack channel.

The aim of the meeting is to discuss the four years old 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, #updater, #upgrade-install

Hi! @josvelasco and I have been collaborating on a patch to help with ticket #53049, regarding adding more information about plugins to the auto-update email notifications. It’s available as a PR at http://wayback.fauppsala.se:80/wayback/20210922144316/https://github.com/WordPress/wordpress-develop/pull/1688 and is ready for some discussion/review, if there’s time.

Editor chat summary: Wednesday, 15 September 2021

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor Slack channel, on Wednesday, September 15, 2021, 14:00 UTC.

WordPress 5.9

Preliminary Roadmap, a quick overview of the main areas and features currently underway for 5.9 in Gutenberg.

Gutenberg 11.5.0

Gutenberg 11.5.0 was released on 16th September, this update includes Block Gap support, improved support for Flex Layouts, performance improvements, and additional design tools. Check out the release post 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.json UI
  • Design Tools
  • Navigation Block
  • Navigation Editor

For a detailed plan check out monthly priorities post.

Updates on the key projects

Nav Editor:

@get_dave

Rest API:

@zieladam

  • For the REST API changes, saving menu items using rest API.
  • As a nice side-effect, we might get a simple API for saving changes in any editor that acts on entities through blocks (e.g. the widgets editor).

Mobile: 

@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 locale 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

@ntsekouras

In progress:

@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:
  • 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 sidebar 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

@mciampini

An update from the folks working on the components package

Shipping:

In Progress:

@oandregal

@annezazu

@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 HTML element options on the Group block.

@mkaz

Open Floor

@get_dave

  • Could whoever is running the Gutenberg Plugin release please let me know how they found the automated changelog feature grouping? I worked on a couple of PRs on that 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. My proposal does two things that I’d like some input on:1. opens up `theme.json` for extensibility by developers via hooks/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.

@paaljoachim

  • The following comment made by @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 doesn’t help here either.
    • Related issues.
    • 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 which has stalled.

Read complete transcript

#meeting-notes, #core-editor, #editor, #gutenberg, #core-editor-summary

What’s new in Gutenberg 11.5? (16 September)

It’s been two weeks since 11.4, so it’s time for another Gutenberg release, 11.5!

This update includes Block Gap support, improved support for Flex Layouts, performance improvements, and additional design tools.

Theme / Block Gap Support

Block Gap support 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, and was initially opt-out for themes. Following feedback, this feature is now opt-in. Thanks so much for the testing and feedback!

With Block Gap support in place, it has also been added to the Columns, Title, and Navigation 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 in 11.2.0, now Flex Layouts are supported within the Social Links and Group 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 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, 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, allowing block, theme, and patterns to have a reliable set of styles provided by core.

Themes are now able to selectively disable text and background colors. 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, and is now vertical, making it easier to visualize the hierarchy.

There is a new setting to customize the Next and Previous Page indicators 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)

Enhancements

Accessibility

  • Font weight screen reader description. (34312)

Block Editor

  • Media Placeholder: Change media URL input type to allow a local URL path. (29138)

Block Library

  • Columns Block: Use blockGap between Columns blocks. (34456)
  • Group Block: Add a row variation. (34535)
  • Heading Block: Vertical heading levels menu. (32926)
  • Navigation Block: Allow Site Title and Logo inside Navigation block. (33316)
  • Navigation Block, List View: Do not show appender and avoid closing the modal on block select. (34337)
  • Navigation Block: Remove horizontal and vertical navigation block variations from inserter. (34614)
  • Navigation Block: Use gap instead of margin. (32367)
  • Post Author Block: Add duotone suport. (34408)
  • Query Pagination Next/Previous: Add an arrow attribute and sync next/previous block’s arrow. (33656)
  • Site Logo Block: Update block description to be concise. (34471)
  • Site Title Block: Update block description to be concise. (34475)
  • Social Links Block: Use the new flex layout. (34493)
  • Video Block: Use existing video poster image on insert. (34415)

Components

  • MenuItem: Add right padding for unchecked radio and checkbox items. (34406)
  • ToggleGroupControl: Update stories to use knobs. (34497)

Core Data

  • Add isRawAttribute to entity configuration. (34388)

Design Tools

  • Add wide alignment control only if theme provides layout.wideSize. (34586)
  • Update justification control in flex layout. (34651)
  • ToolsPanel: Change icon from horizontal to vertical ellipsis. (34369)

Full Site Editing

  • Limit FSE admin notices to the Themes screen. (34353)

Global Styles

  • Allow disabling text and background color via theme.json. (34420)
  • Make global styles available to all themes. (34334)

i18n

  • Add context to ‘none’ strings for better translations. (34341)
  • Make permalinks documentation URL translatable. (34282)

Post Editor

  • Expose ThemeSupportCheck component. (20506)
  • Title block gap. (34570)

Themes

  • Add default editor styles applied to themes without theme.json and without editor styles. (34439)

Widgets Editor

  • Add ‘Widget Group’ block to widgets screens. (34484)
  • Legacy widget rendering endpoint. (34230)

New APIs

Design Tools

  • Allow themes with theme.json to opt-out of block gap styles. (34491)

Bug Fixes

Accessibility

  • Fix button block focus trap after a URL has been added. (34314)

Block Editor

  • Fix menu item padding regression. (34435)
  • Fix text-menu min widths. (34532)
  • Keep id on paste if internal link points to it. (31107)
  • Fix caret position on block merging. (34169)

Block Library

  • Heading Block, Paragraph Block: Fix long strings of text without spaces overflow the block. (34222)
  • Gallery Block: Fix bug with stalled upload when image size too large. (34371)
  • Gallery Block: Fix media placeholder height in site editor. (34629)
  • Gallery Block: Fix problem with overflowing captions on new gallery block format. (34402)
  • Latest Posts: Fix various React warnings in development log. (34428)
  • Navigation: Fix navigation block classname issues. (34344)
  • Navigation: Fix Page List styles inside responsive Navigation. (34517)
  • Navigation: Fix responsive menu height regression. (34488)
  • Navigation: Fix submenu layout in navigation page list. (34342)
  • Navigation: Fix submenus to only take up space when visible. (34382)
  • Navigation: Fix undo/redo ‘trap’ in navigation link block. (34565)
  • Site Title: Allow empty title in edit mode. (34274)
  • Social Links Block: Fix deprecation. (34639)
  • Video Block: Fix TypeError when removing poster. (34411)

Components

  • Align labels on focal point picker position controls above the inputs. (34209)
  • Check if in browser env before calling CSS.supports. (34572)
  • Combobox Component: Only force expanded state if the input has focus. (34090)
  • CustomSelectControl: Add describedBy fallback. (34385)
  • DateTime Component: Fix sizing of help info. (34370)
  • Fix ToggleGroupControlBackdrop not updating size when isAdaptiveWidth prop changes. (34595)
  • Fix selected value computation in CustomSelectControl when no initial value is set. (34490)
  • Fix subheadings from wrapping. (34319)

Design Tools

  • Border Controls: Display color indicator and check selected color. (34467)
  • Border Support: Fix check for displaying border support panel. (34516)
  • Gap block support: Force gap change to cause the block to re-render (fix Safari issue). (34567)
  • Letter Spacing: Group letter spacing correctly under typography supports. (34515)

Global Styles

  • Fix block-level global styles color panels. (34293)
  • Font Appearance Control: Fix error in global styles for Site Title in TT1-Blocks. (34520)

Meta Boxes

  • Change default value of enableCustomFields to undefined. (33931)
  • Fix metabox reordering. (30617)

Packages

  • Blocks: Register block when invalid value provided for the icon. (34350)
  • Core Data: Add ‘include’ to the query key. (34583)
  • Core Data: Use resolveSelect instead of select in saveEntityRecord. (34584)
  • Interface: Block Toolbar & Popover component – Prevent sticky position from causing permanently obscured areas of the selected block. (33981)
  • Scripts: Only use svgr/webpack in js files. (34394)
  • Scripts: Convert legacy entry point arguments for compatibility with webpack 5. (34264)

REST API

  • Default batch processor: Respect the batch endpoint’s maxItems. (34280)

Widgets Editor

  • Fix Block Settings sidebar unexpectedly collapsing. (34543)
  • Legacy widget’s preview functionality is broken when the page is moved. (34384)
  • Prevent focus trap in Legacy Widget block’s preview iframe. (33614)

Performance

Block Editor

  • Improve the getBlock and getBlocks performance. (34241)
  • Remove duplicated useValidAlignment hook. (34593)

Core Data

  • Move locks state from store to local variable. (34374)

Global Styles

  • Remove colors classes from the packages that are already provided by global styles. (34510)

Experiments

Navigation Editor

  • Add undo redo buttons in navigation editor. (34533)
  • Decode entities in the menu names. (34263)
  • Disable “block-nav-menus” feature for the purposes of removing the “experimental” status on the Navigation Editor. (34444)
  • Preload menu REST API requests on new navigation editor. (34364)
  • Update navigation editor placeholder. (34568)

Documentation

Handbook

  • Replace withSelect references with useSelect. (34549)
  • Updated Template Section copy. (34383)
  • Update block variations documentation about block scope. (34455)

Packages

  • Blocks: Correct typo in Blocks Documentation. (34396)
  • Componentes: Fix/update documentation alignment matrix control. (34624)
  • Componentes: Update DuotonePicker documentation for accuracy. (34494)
  • Eslint: Add no-unsafe-wp-apis to rules list in the documentation. (34416)
  • Prettier: Correct syntax in README.md for prettier-config. (34600)

Code Quality

Block Editor

  • Code cleanup to the getBlock refactoring. (34326)
  • Ensure that blockType is defined when accessing apiVersion. (34346)
  • Migrate lightBlockWrapper support to apiVersion for blocks. (34459)
  • Fix Animated warning log. (34197)
  • Rich Text: Replace global event handlers with local ones. (34492)
  • Rich text (core): OnFocus method can be replaced with HTMLElement.focus. (32054)
  • Use Setting: Consolidate the PATHS_WITH_MERGE constant to one instance. (34407)

Block Library

  • Gallery Block: Add docblock comments to the new gallery hooks. (34562)
  • Gallery Block: Remove IE specific CSS hacks. (34372)
  • Button Block: Replace global shortcut event handlers with local ones. (34498)
  • Navigation Block: Refactor to use generic classnames. (34171)
  • Navigation Link Block: Replace global shortcut event handlers with local ones. (34500)
  • Gallery Block: Remove redundant css selector. (34277)

Components

  • CustomGradientBar: Replace global shortcut event handlers with local ones. (34505)
  • Guide: Replace global shortcut event handlers with local ones. (34503)
  • Navigate regions: Use React events for shortcuts (portal bubbles & contextual). (33633)
  • Rename PolymorphicComponent* types to WordPressComponent*. (34330)
  • Simplify Modal with hooks. (34412)
  • Simplify & polish heading levels. (34378)

Core Data

  • Fix linting errors. (34596)
  • Fix linting error in trunk. (34464)
  • Migrate canUser resolver to thunks. (34580)
  • Migrate entities.js to thunks. (34582)
  • Migrate getAutosaves resolver to thunks. (34581)
  • Migrate getEntityRecord resolver to thunks. (34576)
  • Migrate getEntityRecords resolver to thunks. (34578)
  • Migrate resolvers to thunks: GetAuthors, _getCurrentUser, __getCurrentTheme, __getThemeSupports. (34579)
  • Refactor deleteEntityRecord to use thunks instead of generators. (34386)
  • Refactor editEntityRecord, undo, and redo to be thunks instead of generators. (34387)
  • Remove the PROCESS_PENDING_LOCK_REQUESTS action. (34343)
  • Refactor saveEntityRecord from redux-rungen to async thunks. (33201)
  • Remove extraction of raw values in saveEntityRecords. (34502)

Other Packages

  • Compose, useDropZone: Ensure drag event targets HTMLElement. (34272)
  • Editor: Replace hardcoded store key. (34296)
  • Env: Clarify config error within parse-config.js. (34322)
  • Post Editor: Fix gray W menu color. (34318)
  • URL: Add getFilename method to the URL package. (34313)

Tools

Build Tooling

  • ESLint: Add useSelect to direct function calls list. (34301)
  • ESLint: Update error message for @emotion/css with info about the useCx hook. (34418)
  • Fix build hang on Windows 10. (23589)
  • Linting: Remove global event listener warning. (34528)
  • More work on the stability of the performance metrics. (34229)

Plugin

  • Added janw-me to the Codeowners for the PHP FSE folder. (32990)
  • Fix title missing in bug report form. (34504)
  • Update bug form to use drop downs. (34458)
  • Update the minimum supported WordPress version to 5.7. (34536)

Testing

  • Add unit tests for edit site editor utils. (34401)
  • Debug e2e-tests in vscode. (29788)
  • Jest Preset: Restore the default setting for the verbose option. (34327)
  • Make Test_Widget compatible with WP_Widget. (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.

VersionLoading TimeKeyPress Event (typing)
Gutenberg 11.56.71s40.42ms
Gutenberg 11.46.80s44.79ms
WordPress 5.87.53s50.72ms

Kudos to all the contributors that helped with the release! 👏

Thanks to @beafialho and @joen for the release post assets, @priethor for coordination and review, @youknowriad for release and tools wrangling, @mamaduka for answers and help throughout, and @talldanwp for inviting me to shadow a release in preparation.

#block-editor, #core-editor, #gutenberg, #gutenberg-new

What’s next in Gutenberg? (Mid-September 2021)

This status update contains the high-level items that Gutenberg contributors are focusing on in preparation for the WordPress 5.9 Go/No Go that builds on the focus areas for 5.9 and the current Site Editing Scope. 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 to keep up with Gutenberg and the Full Site Editing project. There is also an index page of Gutenberg development-related posts.


Template Editor

The Template Editor is the editing mode that allows you to create, assign, and edit block 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 plugin. Current focuses include:

Follow along:

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:

Follow along:

Global Styles and theme.json UI

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.

Follow along:

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:

Follow along:

Navigation Block

With the help of the Navigation block, editing a site’s navigation menu 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:

Follow along:

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:

Follow along:

Other Projects

Apart from these bigger projects, there are a wide arrange of focuses where contributors can help improve Gutenberg, including:

Follow along:


Areas to be aware of

WordCamp US 2021:

  • WordCamp US 2021 is scheduled for October 1st, 2021 as an online event. Tickets are free and available here!

FSE Outreach Program:

Hallway Hangouts:

Design:


Ways to Get Involved

While the above items are our focuses, don’t forget that you can always help with triage, testing issues, good first issues, and reviewing PRs. In particular, if you’re interested in helping with triage but don’t know where to start, there’s a course on Learn WordPress for how to do triage in 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 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, here are specific meetings to join depending on your interest. Remember that you need a WordPress.org slack account to participate:

  • Core Editor weekly Wednesdays @ 14:00 UTC in #core-editor focused on all things Gutenberg.
  • Block Themes meeting twice monthly on Wednesday @ 16:00 UTC in #themereview focused on preparing for Full Site Editing.

Thanks to @annezazu and @cbringmann for reviewing this post.

#core-editor #gutenberg-next #gutenberg