What’s new in Gutenberg? (12th November)

This update gathers a big number of fixes and improvements. It also completes many accessibility tasks — the original milestone for blockers is now closed.

Version 4.3 is fully released and Beta 4 will be coming later in the day.

Showing integration with the 2019 theme

4.3 / WordPress 5.0 (Beta 4) 🐺

Bug Fixes

Other Changes

Testing

Documentation

Mobile Apps

Deprecations removed with this version.

Status Update

  • Current PRs for review: 35 in 4.4 Milestone.
  • Open issues in 5.0 RC: 162.
  • Open issues in 5.0.0: 2.
  • Open issues in 5.0.1: 2.
  • Open issues in 5.0.x (fast follow): 15.
  • Current beta: Beta 3, November 5.
  • Current plugin: 4.3, released today.
  • Next beta: Beta 4, planned for today.

#core-editor, #editor, #gutenberg

What’s new in Gutenberg? (31st October)

4.2 is at the release candidate stage and can be grabbed here.

This update includes several fixes, refinements, performance improvements and other updates to the user experience and the different layers of APIs. Notably, it concludes the cycle for the formatting API to extend Rich Text components allowing to extend its controls more easily.

Adding a new formatting control to inline formatting toolbar.

The inserter between blocks has been tweaked so that the experience is consistent with all “add block” buttons — it opens the full inserter now.

Show full inserter when clicking + button between blocks.

Plugin developers can also register their own block categories and supply them with an icon for better clarity in the block library list.

Block categories can display an icon now.

4.2 🎲  / WordPress 5.0 (up to Beta 3)

Bug Fixes

Other Changes

Mobile

Deprecations removed with this version.

#gutenberg

What’s new in Gutenberg? (19th October)

This update is considered to be the feature complete for starting the WordPress 5.0 cycle.

Highlights include a block navigation system that can be used to access child and parent blocks within nested blocks easily. It also works as a way to navigate quickly through all the blocks in post. This is a top level affordance that works as a “path” finder and would be the basis for many of the phase 2 layout implementations.

Alternative mechanism for selecting nested groups.

There is also a new block, new style variations for Table, support for video backgrounds in the newly renamed Cover block, accessible date and color pickers, better visibility for style variations, and an “options” modal similar to the former “screen options” to toggle document and meta-boxes on and off.

And this one shows a convenient block for splitting media and text in two columns with mid resizing. In phase 2, this can be the base for internal resizing of columns:

The next step is going to be to freeze the numerous APIs while bugs and outstanding backwards-compatibility issues are addressed.

4.1 is at the release candidate stage, which can be grabbed here.

4.1 🎾

Bug Fixes

Other Changes

Mobile Native

Deprecations removed with this version.

#core-editor, #editor, #gutenberg

What’s new in Gutenberg? (11th October)

4.0 is at the release candidate stage, which can be grabbed here.

Our 40th release is going to be a long one. Main changes are the introduction of a new data structure for RichText that will allow building sophisticated interfaces for inline content that we can make portable and relevant to mobile too.

It also has improvements for blocks, a way to set a different color as the overlay for Cover Image, a new font size picker that is clearer to use and scales much better, a cool Pullquote style variation, etc. This crosses a lot of the pending items.

There are also several interface improvements, including the ability to search categories, post locking when multiple people interact with the editor, better handling of floats, and many more.

Updated Font Size Picker component

4.0 🍯

Bug Fixes

Other Changes

Mobile

Deprecations removed with this version.

#core-editor, #editor, #gutenberg

Dev Chat Summary: October 10 (5.0 Week 2)

This post summarizes the dev chat meeting from October 10th (agenda, Slack archive).

5.0 planning

  • See @pento’s WordPress 5.0 for Contributors and Committers post:
    • “If you’re an experienced contributor or committer who has time available during the WordPress 5.0 release cycle, and want to be able to make meaningful contributions towards making WordPress 5.0 awesome” … “Please reply to this post with information about your availability, what components of WordPress you have experience in, and (if you haven’t got involved with Gutenberg yet) what you feel has been getting in the way.”
    • In that post are some direct actions you can take to help contribute to 5.0, otherwise please review and comment if you’ll be around during the 5.0 release cycle… thanks!
  • Also see review @pento‘s 5.0 commit/branch details if you plan to contribute during the 5.0 release cycle
  • @pento: if you have time to help, please review tickets in the 5.0 milestone to determine whether to keep it in 5.0 (Gutenberg-related), or move to 5.0.1 (other bug fix) or 5.1 (other feature)
  • @kadamwhiterequest for help testing Lazily Evaluate Translation Strings (#41305) with input requested by the end of this working week to help remove the blocker to further Gutenberg localization work
  • Plans for an updated readme.html to be committed with contributions open until RC
  • @chanthaboune: collecting blocker items and dates across team reps, will post listing to Make/Core, if you have items to add to the listing please ping @chanthaboune directly
    • @matt: 5.0 baseline and goal is 4.9.8 + Gutenberg, thus a lot of things that may have been considered blockers in past major releases are probably going to be reclassified as “nice to have”
  • @matveb: last JS package included in the Gutenberg 4.0 RC, on track and could be ready for end of the week

Updates from focus leads and component maintainers

General announcements

  • See @matt‘s post for details on the Gutenberg Phase 2 Leads, @alexislloyd (design and product) and @youknowriad (technical)
    • Phase 2 is about thinking outside the box, namely the post and page box, to allow Gutenberg to handle entire-site layouts. We will replace widgets with blocks, so any block will be able to be used in any registered “sidebar” for legacy themes, and we will upgrade “menus” to a navigation block.
    • Phases 3 and 4 of Gutenberg at WordCamp US in December.
  • @audrasjb: a11y team reorganizing, will discuss during next week’s meeting
  • @chanthaboune: as teams identify new/updated team reps, please follow notes on team rep orientation

Next meeting

The next meeting will take place on October 17, 2018 at 20:00 UTC in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#5-0, #a11y, #core, #core-editor, #core-js, #core-media, #core-php, #core-restapi, #dev-chat, #gutenberg, #summary, #team-reps

Dev Chat Summary: September 26th (4.9.9 week 7)

This post summarizes the dev chat meeting from September 26th (agenda, Slack archive).

4.9.9 and 5.0 updates

  • @schlessera: just about time to begin work on the 5.0 release cycle
    • @antpb and I will step back as release leads and wind down the 4.9.9 release
    • Over the next couple of weeks we will start coordinating the transition to ease into 5.0 release cycle
    • Will review the work that teams are already in the middle of and determine how best to proceed
    • Announcing this change as soon as possible to provide a longer transition period to smoothly transport as much work over as possible
  • @chanthaboune: “I lead the open source teams at Automattic and am a full time sponsored volunteer to the WordPress Project.”
    • We will reach out to team reps, discuss what you’ve been working on, and what we can do to keep things moving forward so that we can make sure everyone is heard as we settle in for 5.0
    • Current understanding is that @matt is leading 5.0 and any other leads are yet to be determined
  • @jorbin: concern with canceling 4.9.9 due to upcoming PHP7.3 release, some things need to be done to make sure WordPress runs fine on this new version of PHP, I want to ensure the version of WordPress in use on December 13th is compatible with PHP7.3, a very small scoped 4.9.9 may still be needed from myself and ideally @sergeybiryukov @pento @schlessera as well
  • @desrosj: #44416 and #44771 appear to be the open PHP 7.3 compatibility tickets in Trac
  • @pento: seems possible to wrangle a small 4.9.9 release with PHP 7.3 related bug fixes, while 5.0 is ramping up
  • @matveb: Gutenberg leads are near ready to start planning merge proposal for Gutenberg, currently focused on finishing the core Gutenberg tasks, @youknowriad has made a proposal for how JS packages could work
  • @youknowriad: recommend iterative merge vs. a big merge proposal, technical proposal on how this would work was shared in #core-js meetings
  • @sergeybiryukov: some new hooks or enhancements already backported to the 4.9 branch, will need to determine whether or not that should be reverted
  • @jeffpaul: in summary… (1) it appears like a possible agreement with @jorbin @pento (and possibly others who’ve been “voluntold” but yet to confirm) to work on a 4.9.9 focused solely on PHP 7.3 support and (2) @chanthaboune will review existing 4.9.9 work with team reps to see how that should be handled with the 5.0 cycle likely starting shortly

Updates from focus leads and component maintainers

  • The Editor / Gutenberg team released v3.9 last week including the ability to create reusable templates of blocks and exporting them to a JSON file
  • The JavaScript team posted this week’s meeting summary and specifically called for help looking for npm maintainers, so please let them know if you’re interested and available. Related to that, @youknowriad shared #44987 and is looking for review there.

General announcements

  • @psykro continues to look for review and feedback on the alternate devchat proposal
  • @joyously: Theme Review Team discussing what to allow theme authors to put in the admin, possibly allowing themes the same interface as plugins do with a readme.txt file and a View Details link to enhance the theme documentation, change logs, screenshots, upsells. Will look to have discussion in Core Trac ticket or Make/Themes post (and cross-post to Make/Core).

Next meeting

The next meeting will take place on October 3, 2018 at 20:00 UTC in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#4-9-9, #5-0, #core, #core-editor, #core-js, #dev-chat, #gutenberg, #summary

What’s new in Gutenberg?

This new release completes some cool additions to the editor. It includes the ability to create reusable templates by selecting multiple blocks in the editor. It then allows exporting and importing these templates using a JSON file transport. There’s also a visual diff mechanism for comparing options when a block was detected as invalid (which could scale in the future to improved UX for revisions as a whole), toolbar groups can be defined as collapsible into a dropdown to better organize available block controls.

Showing visual comparison and reusable templates

There’s also the addition of a much clearer drag handle for drag and drop block operations next to the block arrow controls. It’s also possible to convert an image into a cover image and back, retaining the caption as the main text among many other small improvements and fixes.

3.9 🍒

Mobile Native

Deprecations removed with this version.

#core-editor, #editor, #gutenberg

Dev Chat Summary: September 19th (4.9.9 week 6)

This post summarizes the dev chat meeting from September 19th (agenda, Slack archive).

4.9.9 planning

  • @westonruter: highlighted this discussion about the scope of HTTPS support to target in 4.9.9
    • Looking for wider visibility on those items to get thoughts on what makes sense to include in 4.9.9
    • Relates to umbrella ticket #28521
  • @audrasjb: Accessibility team has a spreadsheet where we sort all the tickets on the focus a11y in order to facilitate lead’s work (see this week’s meeting notes)
  • Bug scrubs not scheduled yet, when they are it’ll be posted to Make/Core

Updates from focus leads and component maintainers

  • @kadamwhite from the REST API team wants to propose the inclusion #41305 in 5.0
    • This covers altering how we evaluate translation strings, originally with the intent of deliberating a performance improvement to the REST API. In discussions about how Locale can be applied to REST API responses for Gutenberg this issue resurfaced, because the current order of operations precludes evaluating string translations based on a passed flag (required to permit the API to provide translations in a user’s locale). To support these localization needs and to improve overall performance at the same time, we intend to milestone this ticket for 5.0.
    • @schlessera: There are two proposed solutions in the above ticket: one that fixes REST API schema translations only, and one that generally optimizes translations (REST API component team’s strong recommendation). The latter is highly preferable, but includes breaking changes for edge cases (as noted in the ticket), so might need a check against plugins first. We otherwise would like more eyes on the forthcoming patch to validate the approach and to help test it.
  • The Editor / Gutenberg team released v3.8 last week including “full screen” mode, improved mechanisms for styling blocks from a theme perspective, and exposes the custom post type used to store reusable blocks from the block inserter as a way to manage saved blocks in bulk.
  • The JavaScript team published notes from their last meeting including documentation of available Gutenberg scripts, reducing exposure of Moment.js in the `wordpress/date` module, and a couple announcements on introducing a formal asynchronous data flow as part of `wordpress/data` and the new `wp-polyfill` script added to Gutenberg.

General announcements

  • @psykro posted about alternate devchat options. Please give that a review and feedback, as ideally we get to a conclusion during next week’s devchat.
  • @whitneyyadrich & @dkotter looking for eyes on / update to Gutenberg issue#7762 as they are running into an issue where they need to be able to insert and manipulate media attachments within the Classic Block, but that’s not currently possible
    • Also imagine this being a bigger issue when migrating sites over to Gutenberg and all their existing content will be thrown into that block. There’s currently not a great way for them to modify/add to that content, if they need to do things with images.
    • Will review with Gutenberg team in next #core-editor weekly chat

Next meeting

The next meeting will take place on September 26, 2018 at 20:00 UTC in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#4-9-9, #a11y, #accessibility, #core, #core-editor, #core-https, #core-js, #core-restapi, #dev-chat, #gutenberg, #javascript, #summary

What’s new in Gutenberg? (12th September)

The release this week, apart from numerous improvements and fixes across the board, includes a new “full screen” mode, and improved mechanisms for styling blocks from a theme perspective. It also exposes the custom post type used to store reusable blocks from the block inserter as a way to manage saved blocks in bulk — an often requested feature. There are plans to expand on the possibilities here so stay tuned for the next series of updates.

Showing Toolbar improvements and Full Screen Mode

It brings news in the data parsing flow as well. Having a formal specification of the Gutenberg block grammar has allowed us both to maintain a stable core during the almost 40 releases of the plugin and lately to allow competing parser implementation to evolve and be compared in terms of performance and correctness. In concrete terms, we are shipping a new default implementation that is hundreds of times faster than the spec and has been stress tested with really long posts (including Moby Dick). These tests are also available for anyone to run against. Memory consumption has also gone down dramatically for server side operations. I’d like to specially thank Dennis Snell and Ivan Enderlin for their great work improving this area.

3.8 🥖

Deprecations removed with this version.

#core-editor, #editor, #gutenberg

What’s New in Gutenberg? (31st August)

Our final update for August aims to add further clarity to some core interactions, as well as fixing many issues. Notably, we are expanding on the previously called “Fixed Toolbar” mode — now named Unified Toolbar — as an optional mode for a more traditional writing environment. In our testing, this mode tends to be preferred by more experienced users who don’t mind the disconnect between the tools and the content blocks. There’s also an additional setting which focuses the editing experience on a single block at a time, as well as de-emphasizing some of the block boundaries. These tools can be combined at will to better suit personal preferences and creative workflows.

There are many improvements to individual blocks, conversions, templates, and interactions. We want to say thank you again to everyone who is engaging, raising concerns or making suggestions, and collaborating in making the project better with each release.

Updates to the Block Switcher Menu

3.7 🛵

Mobile Native

3.6.2

3.6.1

Deprecations removed with this version.

#core-editor, #editor, #gutenberg