What’s New in Gutenberg? (20th March)

This is the last Gutenberg release that will be entirely included in WordPress 5.2 and it’s an exciting one.

First, it introduces a block management modal with the ability to enable/disable blocks from the block inserter.

Block Management Modal

The release also includes the possibility to nest different kind of blocks in a Cover Block container.

Title, paragraph and buttons nested in a Cover Block.

The journey to improve different parts of the editor UI is continuing as well with improvements to the hover and selected block states with better a11y and less distraction.

Hover and selected block outlines

5.3 🇵🇹

Features

Enhancements

Bug Fixes

Documentation

Various

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~ 36000 words, ~ 1000 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 5.3.0 17.19 s 42.57 ms
Gutenberg 5.2.0 16.79 s
41.85 ms
Gutenberg 4.8 (WordPress 5.1) 23.43 s 82.75 ms
Gutenberg 4.7 (WordPress 5.0) 27.60 s 99.13 ms

👏 Kudos to all the contributors. Thank you.

#core-editor, #editor, #gutenberg

Editor chat summary: March 13th

This post summarizes the latest weekly Editor meeting, held in the #core-editor Slack channel, on Wednesday, March 13, 2019, 14:00 UTC.

Block Directory Proposal

  • @youknowriad shared the block directory proposal post and raised that the current block registration APIs do not allow for this kind of plugins, and therefore this would need to be be resolved before building the directory. It is proposed that a private API is created first for use only with core blocks to allow iterations.

Discussions are to continue on the above post and the relevant pull requests.

Code Owners Experimentation Feedback

A few weeks ago, a code owners flow has been introduced to the Gutenberg repository. This allows to  automatically ping people to review pull requests based on their interests on a certain area of the codebase.

A Discussion took place on the goal for this and whether it was achieved.

  • @aduth raised that one of the goals is to raise awareness and to get more core contributors.
  • @nosolosw felt that sometimes too many pings were sent out, and as a new contributor couldn’t commit the required time to review the codebase.
  • @youknowriad feels that the new workflow is not useful for occasional contributors.
  • @mcsf feels that the file paths do not map to the topics that people are interested in.

The new workflow will be kept for now, and reviewed at a later date.

Key Pull Requests

  • Block Management@aduth is actively working on this PR, some minor decisions still to be made, including wording.
  • Section Block – General consensus is that this should be shipped as an experimental block first. This is hoped to land soon, and will be iterated upon.
  • Block outlines UI – The PR is close to merge, it improves the Block outlines for the hover and selected state. @kjellr would like some feedback and testing on this PR.
  • React 16.8 Upgrade – React is going to be updated  on time for WordPress 5.2

Tasks Coordination

  • @aduth @mapk and the design team will be shipping the block management UI shortly
  • @get_dave and @danr are working on the section block (and related items) and will hopefully land a v1 shortly
  • @kjellr @joen @mapk and others are improving the hover and selected block outlines
  • @gziolo is working on the Block Registration API v2 and Axe tool integration
  • @youknowriad is working on the block editor module
  • @nerrad will resume working on the effects -> controls migration
  • @nosolosw and @gziolo are working on wp-scripts CLI improvements
  • @marekhrabe is working on improvements to the Media & Text resizer
  • @jorgefilipecosta is working on inserter improvements, e2e tests and the widget screen APIs

The meeting archive is here.

The agenda for the next meeting is here, please add anything you want to discuss.

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

#agenda, #editor, #gutenberg

What’s New in Gutenberg? (6th March)

As we dive into the block-based widgets screen, foundational work is required to support using the Gutenberg editor outside the Post Editor context. This release falls into this category of releases where it’s more about building the foundations and making the Gutenberg modules more flexible to support these new use-cases.

It introduces a new @wordpress/block-editor module allowing building block editors outside the post editor context and even outside the WordPress Admin context. This has some costs on the performance of the keypress events while working on very long posts that we hope to alleviate in the upcoming releases.


5.2

Enhancements

Bug Fixes

Documentation

Various

Chore

Mobile

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~ 36000 words, ~ 1000 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 5.2.0 11.7 seconds 57.8 ms
Gutenberg 5.1.0 11.4 seconds 22.25 ms
Gutenberg 4.8 (WordPress 5.1) 15.1 seconds 126 ms
Gutenberg 4.7 (WordPress 5.0) 16 seconds 185.2 ms

👏 Kudos to all the contributors. Thank you.

#core-editor, #editor, #gutenberg

Editor chat summary: February 20th

This post summarizes the latest weekly Editor meeting, held in the #core-editor Slack channel, on Wednesday, February 20, 2019, 14:00 UTC.

Gutenberg Release 5.1

Gutenberg 5.1 has been released which marks the end of the widget to blocks project. There are a range of essential enhancements which have been made in this release; details can be found on the release post.

WordPress 5.2 Planning

Based on the proposed schedule and scope for 5.2, a proposal to synchronize the Gutenberg plugin release dates with the WordPress feature-freeze date have been shared. Some concerns were raised about the short timeframes. This will be adapted to the final WordPress 5.2 release schedule.

The WordPress 5.2 scope has been discussed including the need for block discovery and management solutions as many users are feeling overwhelmed with the available choices.

Concerns about the short time frame to achieve these goals for 5.2 were shared and it was suggested that being able to turn blocks on/off. Favourite blocks could form part of 5.2. The wp.org directory could be independent of this roadmap.

Updating wordpress.org/gutenberg

The role and the necessary updates for this page were discussed:

  • The copy of the content needs to be refreshed.
  • Consistency with the marketing terminology is important.
  • Whether the page should be a feature page, or more related to the project roadmap.

@joostdevalk shared a call for ideas and thoughts over the next couple of days.

Tasks Coordination

For the next week, this is what everyone is working on:

  • @gziolo is starting to implement the new Block Registration API.
  • @mkaz is continuing on the documentation effort (i18n and JavaScript setup).
  • @youknowriad is starting to plan the block management and the widget screen work.
  • @youknowriad and @aduth will work on landing the generic block editor module.
  • @nosolosw is going to continue on the React deprecated APIs and JS documentation auto-generation.
  • @getdave and @marekhrabe are working on vertical alignment for the columns and media+text blocks.
  • @talldanwp and @andrei are working on the section block.
  • @jorgefilipecosta is working on improvements for the Calendar block, MediaPlaceholder and block insertion restrictions.

Open Floor

The meeting archive is here.

The agenda for the next meeting is here, please add anything you want to discuss.

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

#agenda, #editor, #gutenberg

What’s New in Gutenberg? (20th February)

More than 51 contributors participated in this release. It marks an important milestone for Phase 2, as it’s the end of the porting widgets to blocks project. Next releases will be focused on explorations around the Widgets screen.

Widgets 2 Blocks

This release also includes a big refactoring to the formatting buttons and the RichText component, allowing us to fix a significant number of issues and to improve the writing flow.

Core blocks (aside from the Classic block) are not using TinyMCE under the hood anymore. This change should not have any perceivable impact, as the APIs of the RichText component and the custom formats registration have not changed.

In addition, contributors have worked on a number of improvements to existing blocks and UI micro-animations.

Enhanced Menus

Click to activate embed blocks

5.1

Features

Enhancements

Bug Fixes

Various

Chore

Documentation

Mobile

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~ 36000 words, ~ 1000 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 5.1.0 9.4 seconds 16.4ms
Gutenberg 5.0.0 10.4 seconds 16.4ms
Gutenberg 4.8 (WordPress 5.1) 13.6 seconds 158.2ms
Gutenberg 4.7 (WordPress 5.0) 15.1 seconds 203.5ms

👏 Kudos to all the contributors. Thank you.

#core-editor, #editor, #gutenberg

What’s New in Gutenberg? (6th February)

@mapk said earlier that the Gutenberg repository is on fire 🔥, he was not lying. More than 52 contributors participated in this release.

This release is also the first release dropping support for WordPress versions prior to 5.0.

As part of the widgets 2 blocks project, this release introduces the RSS block.

RSS Block

The amazon kindle embed provider has been added recently to WordPress, this release adds the corresponding block to the editor.

Amazon Kindle Embed Block

It also brings some improvements to existing blocks including the possibility to define a custom focal point for the cover block’s background.

Cover Focal Point Picker

5.0 🇩🇪

Features

Enhancements

Bug Fixes

Various

Documentation

Chore

Mobile


👏 Kudos to all the contributors. Thank you.

#core-editor, #editor, #gutenberg

What’s New in Gutenberg? (23th January)

Gutenberg 4.9 is a big milestone in terms for performance improvements for Gutenberg. It introduces a new asynchronous mode for blocks rendering improving the responsiveness of the editor.

The Documentation efforts are still on-going with three new tutorials leveraging the Format API, the Sidebar Plugins API and Post Meta Blocks as well as a number of improved README files for our UI components.

In terms of developer experience, this release includes a lot of improvements to our e2e tests including support for aXe Accessibility testing.

Table Block Stripes
Color Swatch Indicator

4.9 🇦🇺

Performance

Bug Fixes

Enhancements

Extensibility

Documentation

Chore

Mobile

#core-editor, #editor, #gutenberg

Editor chat summary: January 16

Phase 2

  • 4.8 has been included in WordPress 5.1
  • 4.9 is going to be released next week according to the regular schedule.
  • In order to address some feedback about how to get involved for phase 2 this post was shared to hopefully clarify this more.
  • Task Co-ordination
    • The idea is not to get everything done for next week, a simple task could be to do some research and clarify the work needed to accomplish a task.
    • The main features/focus for phase 2 are highlighted here.

Block Proposals Flow

  • @karmatosed raised the point of getting new blocks into core.
    • When should something be proposed to core? Not all blocks should be core
    • How can you propose a block to core?
    • What ‘state’ should it be in?
    • How do we proceed from proposal to iterate and collaborate?
    • Don’t want to end up with 1000s of the same block

Widgets > Blocks

  • Need devs to build prototypes.
  • Would be great to get more people contributing and building these blocks.

PRs to highlight

  • E2e tests reorganisation@gziolo has been doing some great work on e2e tests both for accessibility and also a way to make the e2e tests setup usable outside the Gutenberg repository, reference here.
  • A note for those who write e2e tests, they have been moved them to packages/e2e-tests/specs folder. As new blocks are developed supporting documentation should be developed and attached to the block some way.
  • New package with all e2e test utils wordpress/e2e-test-utils which is going to be published to npm next month and will allow some code reuse for those who can start writing e2e tests for their WordPress sites.
  • aXe accessibility testing
    • The set of tools for accessibility static analysis which need integration with e2e tests to ensure that regressions are caught early on, learn more here.
    • Issues need fixing, some of them are related to the fact that WordPress uses “screen-reader-text” class. More info here.
  • Async mode for the data module
    • A big milestone in terms of performance improvements that is going to be included in 4.9.
    • Make sure to test it extensively with your custom blocks plugins. More info here
  • Ready to review:

Action Items

Open Floor

  • @chrisvanpattenwill have some free cycles this week to review docs PRs, particularly from a grammar/clarity/readability perspective. If anyone has PRs you want reviewed please DM him.
  • @luehrsen — would love to see a ‘blocks’ section on the ideas page: where people can propose blocks and plugin devs can pick that up. (Good case in point is @melchoyce’s Restaurant Design blog post)
  • Although @joostdevalk has expressed a desire to kill that ideas page in the past, and now that he’s in his new marketing position for the project he may very well follow through on that
  • @youknowriad — A premise of Gutenberg is to enable people to build custom blocks easily (for niche use-cases)
  • @ajitbohra — Perhaps a block library/pack as a plugin, for blocks that are not intended for core.
  • @paaljoachim — supports having options in blocks to create a top and bottom margin/padding, as we need space between blocks in the layout.

The meeting archive is here.

The agenda for the next meeting is here, please add anything you want to discuss.

#meeting-notes, #editor-chat

#core-editor, #editor, #gutenberg

What’s New in Gutenberg? (7th January)

Gutenberg 4.8 is the first plugin release after WordPress 5.0 that is not going to be backported entirely to the WordPress 5.0.x releases. The bug fixes and performance improvements have been cherry-picked into the upcoming WordPress 5.0.3 release.

The Changelog is a bit long as it includes a lot of PRs that were merged but not included in previous versions due to the more critical work needed for the WordPress 5.0.x releases.

I’d like to particularly thank all the persons that helped and continue to help improve our docs. There has been a lot of nice improvements lately, including a Getting Started with JavaScript tutorial, improvements to the design guidelines to build blocks and high-quality README files for our UI components.

Work on the performance of the editor is also continuing and we can expect more improvements in this area in the next releases as well.

Gutenberg Mobile

4.8 🚩

Performance

Enhancements

Bug Fixes

Various

Documentation

Chore

Mobile

#core-editor, #editor, #gutenberg

5.0.2: Editor Performance and Bug Fixes

With 5.0 released to the world, attention is now placed on preparing the follow up minor releases. The first one, scheduled for December 19th, focuses on performance improvements — particularly around typing with many blocks present on the page — and bug fixes.

The cumulated performance gains are around 330% faster for a post with 200 blocks. This might be even bigger for certain setups and plugin configurations — seeing the same test post be 540% faster with Yoast, for example.

The Gutenberg update can already be tested in the 4.7 plugin release and will be part of the upcoming 5.0.2 beta.

Performance 💨

Bug Fixes 🐛

Tests

#core-editor, #editor, #gutenberg