Categories
Uncategorized

Gutenberg 9.2 Adds Video Tracks, Improvements to Columns and Cover Blocks

Gutenberg 9.2 was released this week and is the last release of the plugin to be rolled into WordPress 5.6. It features the long-awaited video tracks functionality, closing a ticket that has been open for more than two years under development.
Video tracks includes things like subtitles, captions, descriptions, chapters, and metadata. This update introduces a UI for adding video tags, which can contain multiple track elements using the following four attributes:
The ability to edit tracks is exposed in the video block’s toolbar:
This update closes a major gap in video accessibility and greatly improves the user experience of videos.
Gutenberg 9.2 also introduces the ability to transform multiple selected blocks into a Columns block. For example, users can select three image blocks and instantly change them into a three-column section. Columns can be created from any kind of block, including InnerBlocks. The transform option will appear if the number of selected blocks falls between 2-6. (The maximum number is derived from the maximum number of columns allowed by the Columns block.)
Another notable feature in 9.2 is the expansion of Cover blocks to support repeated background patterns. This gives users more flexibility in their designs, opening up a new set of possibilities.
This release brings in more than a dozen improvements to the new Widgets screen, as well as updates to the Query Block and Site Editor experiments. The most notable smaller enhancements to existing features include the following:
Since the Gutenberg 9.2 release was delayed by a week, it includes many more bug fixes and code quality improvements than most releases. Check out the full changelog for more details.
I still think the experience is subpar and the development should drastically change direction into building two different modes – build and write. First would be suitable for designers, geeks, coders and devs to build the overall look of the website and the second mode should be for this who write the content on an ongoing bases. Writers can’t deal with blocks, it’s an unfamiliar experience which alienates them from the platform. I am hearing more and more people to jump out of the ship due to the second one.
Report
This is exactly right. The Gutenberg team don’t appreciate that most writers come from ms word or google docs. When they try to use Gutenberg they find it confusing and clunky
Gutenberg is great, but having one mode and trying to be all things to all people will alienate half the users.
Report
And it is not just home staying bloggers or small businesses, it’s about professional journalists, news editors, reporters, professional writers. They all need a known text experience.
Don’t get me wrong, I am all for blocks, I am in favor of blocks, but Gutenberg needs modes. A journalist doesn’t build the website. No journalist from CNN edits the design, the widgets, the navigation of CNN.com. His job is to write a story.
Gutenberg team should understand that journalists, writers, editors, they are not web builders most of the time. We need Iceberg-like modes that work well without performance hit like Iceberg.
Report
Well Page builders are in and Gutenberg is one of them. At least this gets constant updates.
Report
Which is exactly point. Page builders may be great for designing a site but they are terrible for writing content.
Report
It’s highly encouraged to upgrade to 9.2.1. Especially for those interested in the experimental Full Site Editing feature.
Gutenberg version 9.2 contained a lot of bug fixes, but not enough 😉
Report
Using Markdown for writing content would easily solve that issue. There are quite a few plugins offering that. We live in a modern world and learning new skills is necessary.
Report
This is not about learning new “skills”, it’s about professionals expecting to have a known UI/UX for writing, not managing blocks. If you open your source code editor tomorrow and it’s block based, how would you react?
Iceberg is an idea that is a good idea, but the implementation is a huge performance hit. That’s why this “write” experience should be built-in Gutenberg.
Report
Your email address will not be published. Required fields are marked *









This site uses Akismet to reduce spam. Learn how your comment data is processed.
Enter your email address to subscribe to this blog and receive notifications of new posts by email.


WordPress Tavern is a website about all things WordPress. We cover news and events, write plugin and theme reviews, and talk about key issues within the WordPress ecosystem…read more →
Proudly powered by WordPress.

source

Leave a Reply

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