Gutenberg 16.4 Introduces Experimental Auto-Inserting Blocks

Gutenberg 16.4 has been released with a new auto-inserting blocks experimental feature. It allows developers to specify a location in which the block will be automatically inserted, such as before or after a template. The block can then be repositioned after insertion using the editor tools.

“This applies both to the frontend and to the Site Editor (via the REST API), allowing for further user customization,” Automattic-sponsored engineer Sarah Norris said in the 16.4 release post. She posted a video demonstrating how it works with an example “like” block:

video source: Gutenberg 16.4 release post

Although the auto-inserting blocks is still behind the experimental flag, developers can try it by adding an __experimentalAutoInsert field to the block.json file of a dynamic block. Example code is available in the release post.

“This feature aims to improve the extensibility of block themes through plugins and continues to be actively developed,” Norris said.

The GitHub ticket for auto-inserting blocks describes a common scenario from the days of classic themes where a plugin would use a filter to auto-append a login/logout link to a navigation menu. This is no longer possible with block themes, so contributors have devised auto-inserting blocks as a creative solution that retains ease of use offered by simply activating a plugin and preserves the ability of the user to modify the blocks once inserted.

Gutenberg 16.4 also introduces a new, horizontal ProgressBar component that can be used throughout the interface. It may soon replace the Spinner component that is currently used in the Site Editor loading experience. An indeterminate version (indicates that a process is occurring but with no specific progress measurement) and a determinant version (a progress bar that indicates the progress made, moving towards 100%) are included in this component.