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

Editor Chat Agenda: February 6th

This is the agenda for the weekly editor chat meeting on Wednesday, 6th February 2019, 14:00 GMT.

Housekeeping

  • Release: Gutenberg 5.0
  • Project Update: Porting Widgets to Blocks

Call for Collaboration (REST API and Media teams)

Tasks Coordination

Open Floor

  • @nerrad: Handling support type requests in the slack #core-editor chat. I notice sometimes they are just getting ignored. Should we start actively directing people to the forums for them now? What ways could we make it more visible that the channel is not the place for general support?

If you have anything to propose to add to the agenda or specific items related to those listed above, please leave a comment below.

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

#agenda, #editor-chat

Dev Chat Summary: January 23rd

This post summarizes the weekly dev chat meeting from January 23rd (agendaSlack archive).

5.1 updates

Beta 2

5.1 beta 2 went out earlier this week.

There are a few tickets still open, most of them are related to fine tuning the WSOD handling.

Schedule update

Beta 3 is scheduled for January 29, this is also the soft string freeze. All string changes must be committed by then (except for the About page).

See also: WordPress 5.1 Development Cycle

Dev notes status report

5.1 is being accompanied by a nice collection of dev notes, mainly from Make/Core but also from Make/Polyglots.

@desrosj is continuing to coordinate 5.1 dev notes. There are also plans to construct a 5.1 Field Guide that summarizes collects all dev notes.

Updates from focus reps and component maintainers

Meeting notes and summaries

Other calls/proposals

Open floor

The Gutenberg Team is looking for more pull request reviewers. If you’re interested, please touch base with them in the #core-editor Slack channel. Details to be shared soon in a Make/Core Post.

About including recent Gutenberg changes in the currently scheduled release: the WordPress 5.1 cycle is being a bit stricter about non-regression bug fixes landing during the beta period, but WordPress 5.2 is expected to be able to take bug fixes during the WordPress beta period.

About the recent Post concerning the bulk edit process: many relevant opinions and thoughts were shared during the meeting.

  • @matt expressed a desire to reopen the tickets closed in the recent bulk edit.
  • @desrosj and @jeffpaul will work on a strategy for reverting closed tickets that have not been changed since the bulk edit, to allow the tickets to be properly evaluated for closure.
  • Component maintainers to review related tickets (via this custom query). However, the 5.1 release is probably going to delay the ability to do that.
  • Contributors can also use this Trac report (replacing “myusername” with their username and scrolling to those updated on January 4th) to find the tickets they have been involved with that were affected by the bulk closing.
  • A stale keyword and/or status was discussed as a good way to leave tickets open long term and avoid closing them as wontfix and maybelaterstatuses.
  • A post on Make/Core is coming next week to kick off the efforts of the new Triage Team.

This Dev Chat Summary post is open for further comments and discussions.

#5-1, #dev-chat

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

How to get involved in Gutenberg Phase 2

Having trouble figuring out how to get involved in the Gutenberg Phase 2 effort? Understandable! There are a lot of teams (and channels and blogs) to keep up with. This post will help you find the posts that are helping to define upcoming work as well as identify the places you can follow the conversation.

Development Information

Now that the 5.0 ship is sailing, it’s time to start looking at the second phase of Gutenberg. The 9 projects for 2019 include a few items we’ll be working on in Phase 2:

  • Creating a block for navigation menus.
  • Porting all existing widgets to blocks.
  • Upgrading the widget-editing areas in wp-admin/widgets.php and the Customizer to support blocks.
  • Providing a way for themes to visually register content areas, and exposing that in Gutenberg.

Work on these projects will continue throughout the year. An overview of tasks included in the current scope and features is outlined in this Github issue. It is a living document that evolves as progress is made toward achieving these goals.

Design Information

The second phase of Gutenberg required a lot of initial user research. Synthesizing this research is happening now.  Details about how to get involved with this effort are outlined in this post.

Work on the research and subsequent design will also continue throughout the year. Regular updates will be shared on the Design P2.

Getting involved

While user research is in progress, there are a lot of development tasks that we can work on without additional design information. This includes improvements for phase 1 features, porting widgets to blocks and a lot more, as outlined in the “Actionable items” section of the Github issue linked above.

The main place to get involved is the Github repository. The #core-editor Slack channel is where developer coordination and live day-to-day discussions happen. The weekly developer meetings are held Wednesdays at 14:00 UTC.

Each meeting will have an agenda posted beforehand, so you can see if the topics up for discussion are relevant to your interests. Once completed, meetings will be summarized in a post, so that people who can’t participate synchronously, can catch up and comment asynchronously.

If you want to contribute to Phase 2 and still have questions about how to do that, please ask your questions in a comment on this post so we can make this resource even more useful!

#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

Gutenberg commits and merge status update

In the last weeks, we froze merging PRs in the Gutenberg repository to allow us to strictly control what gets shipped in 5.0 and 5.0.x releases.

This has served us well to ensure the stability of the releases. At the same time, the number of approved and unmerged PRs kept growing in the repository. After some discussions and feedback, it’s time to make some adjustments to our merging workflow:

  • A g-minor branch has been created in the Github repository based on the last package release.
  • Critical bug fixes can be cherry-picked to this branch in order to be integrated into 5.0.x releases.
  • Package releases can be performed from the branch.

In parallel:

  • We’ll start merging approved PRs to the master branch iteratively. Initially, let’s limit merging PRs to those explicitly assigned to the 4.8 milestone.
  • The merged PRs will be shipped in the next Gutenberg plugin releases.
  • No package release will be performed from the master branch.

As a consequence, the plugin releases and the WordPress release will diverge more and will be aligned for each major WordPress release.

#core-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