Gutenberg 1.2 Released with New Features and Improvements

Gutenberg 1.2 Released

The Gutenberg Editor is here with its new version, Gutenberg 1.2. The newest version was released over the weekend with some interesting enhancements.

This time, the changelog had around 30 improvements along with some addition of features like added postmeta support, extended settings placeholder, and more. Now, let’s have a quick look at the improvements in Gutenberg 1.2.

This release offered initial support for postmeta in block attributes. Gutenberg contributor, Gary Pendergast has tweeted an example plugin for those who want to experiment with it.

The updated version of Gutenberg has provided a better experience resolving block conflicts when switching between the “classic editor” and Gutenberg. In the previous versions, if a user had created some paragraph blocks in Gutenberg but switched to the classic editor, the tags would get stripped out, making the blocks invalid when moving back to Gutenberg. Gutenberg 1.2 merges a pull request that detects whether the post contains blocks and then disables the wpautop behavior in the classic editor to prevent it from stripping the tags.

The new version is also ready to support metaboxes and has added a placeholder for the proposed Extended Settings panel. The metabox placeholder shell currently sits beneath the content with a “coming soon” message.

Extended Settings. Image Source: WP Tavern

Another new feature in Gutenberg 1.2 is the addition of word and block count to the table of contents. The value of knowing how many blocks are in play on the page or how many headings have been used is not immediately evident. Gutenberg users claim it to strike as a rather large and obstructive display of non-essential information, which for some reason has been given priority placement at the top of the editor.

word and block count. Image Source: WP Tavern

Version 1.2 has also made few other improvements as well. Some of them are listed below:

It may have seemed like Gutenberg development has been on hold due to the delayed JavaScript framework decision, but development is still ongoing. It slowed over the past couple weeks while most of the project’s chief contributors were attending the Automattic GM.

Pendergast has also said that even once a JavaScript framework decision is made, Gutenberg will only require one or two developers to work on the necessary changes, but all other contributors will be able to continue on without any issues.

You can subscribe here to keep up with the weekly updates of the Gutenberg editor. And if you have anything to add or share, kindly use the comments section.


Reference: WP Tavern

Leave a Reply

Your email address will not be published. Required fields are marked *