In this video Brian Coords show the improvements to the Block Binding API. In the first half of the video he shows how it looks in the editor and in the second half he shows the code needed to implement it.

Here is a table showing the CSS options per Gutenberg block. If you compare it to the list from 6.1, which is linked in the post, it seems that most blocks got 2-3 additional style options.

Coming in a month, WordPress 6.6 introduces overrides in synced patterns. This brings a components-like feature to the block editor and is a very useful enhancement. In this article on the developer blog, Nick Diego gives a full walk-through of synced pattern overrides and how to use them.

For Plugin Developers – WordPress 6.6 standardizes the API for extending the Gutenberg editor so that the same API calls work in the content editor and the Site Editor. This should simplify the process of adding Gutenberg support.

This proposal on the Make blog using “Bits” as dynamic tokens as a replacement for shortcodes. Bits are placeholders for content and use an HTML comments syntax.

If you want to get up to speed on Gutenberg and the Site Editor, Brian Gardner has a 5 part video series that nicely explains: how to install Google fonts, adding a site icon, understanding list view, WordPress patterns, and getting started with global styles.

There is a push in the upcoming WordPress 6.6 release to make Gutenberg styles easier to override, even reducing the specificity down to zero. If I’m reading this correctly, it appears there may be some backwards compatibility issues.

It is good to see some progress on Phase 3 of Gutenberg, the collaboration phase. This is an experimental feature allowing for commenting on blocks, I imagine similar to Google Docs comments.

It seems they’ve changed with every WordPress release. This article gives a high-level overview of the history and evolution block patterns.