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

5.0 / Gutenberg Status Update – Dec 6

Current PRs for review:

Open issues in 5.0.0: 1 (=)
Open issues in 5.0.1: 28 (-1)
Open issues in 5.0.x (fast follow): 123 (+1)
5.0 status: RC3, released December 4.
Current plugin: 4.6, released November 30.
Next 5.0 milestone: WordPress 5.0, to be released December 6

In Trac:

  • Ready to commit:
    • N/A
  • Has patch, needs review:
    • N/A
  • Opened bugs:
    • N/A
  • Opened tasks:

#core-editor, #editor, #gutenberg

5.0 / Gutenberg Status Update – Dec 5

Current PRs for review:

Open issues in 5.0.0: 1 (=)
Open issues in 5.0.1: 29 (-5)
Open issues in 5.0.x (fast follow): 122 (=)
5.0 status: RC3, released December 4.
Current plugin: 4.6, released November 30.
Next 5.0 milestone: WordPress 5.0, to be released December 6

In Trac:

  • Ready to commit:
    • N/A
  • Has patch, needs review:
    • N/A
  • Opened bugs:
    • N/A
  • Opened tasks:

#core-editor, #editor, #gutenberg

5.0 / Gutenberg Status Update – Dec 4

Current PRs for review:

Open issues in 5.0.0: 1 (=)
Open issues in 5.0.1: 34 (+1)
Open issues in 5.0.x (fast follow): 122 (+1)
5.0 status: RC2, released November 30.
Current plugin: 4.6, released November 30.
Next 5.0 milestone: RC3, to be released today

In Trac:

  • Ready to commit:
    • N/A
  • Has patch, needs review:
    • N/A
  • Opened bugs:
    • N/A

#core-editor, #editor, #gutenberg

5.0 / Gutenberg Status Update – Dec 3

Current PRs for review:

Open issues in 5.0.0: 1 (=)
Open issues in 5.0.1: 33 (-1)
Open issues in 5.0.x (fast follow): 121 (-1)
5.0 status: RC2, released November 30.
Current plugin: 4.6, released November 30.
Next 5.0 milestone: TBC

In Trac:

  • Ready to commit:
    • N/A
  • Has patch, needs review:
    • N/A
  • Opened bugs:
    • N/A

#core-editor, #editor, #gutenberg

What’s New in Gutenberg? (30th November)

This should be the final “what’s new” installment for 5.0 — the 46th overall — accompanying the second release candidate which is also just released.

The Gutenberg plugin has also been updated to match core. The changelog here is a bit longer as it updates from 4.5.1:

4.6 ⌛️

#core-editor, #editor, #gutenberg

5.0 / Gutenberg Status Update – Nov 30

Current PRs for review:

Open issues in 5.0.0: 1 (-14)
Open issues in 5.0.1: 34 (-18)
Open issues in 5.0.x (fast follow): 122 (+17)
5.0 status: RC 1, released November 23.
Current plugin: 4.6, released today.
Next 5.0 milestone: RC 2, targeted for today.

In Trac:

#core-editor, #editor, #gutenberg

5.0 / Gutenberg Status Update – Nov 29

Current PRs for review:

Open issues in 5.0.0: 15 (=)
Open issues in 5.0.1: 52 (-1)
Open issues in 5.0.x (fast follow): 105 (-1)
Current beta: RC 1, released November 23.
Current plugin: 4.5.1, released November 21.
Next release: RC 2, November 30.

In Trac:

#core-editor, #editor, #gutenberg