WordCamp Europe 2021 took place this past week and this year’s event was head and shoulders above last year’s online event thanks to the Hublio app, which brought a real sense of “being there” without actually being there. A huge thank you to the organizers and sponsors for all their work bringing this event to life. But that’s not the focus of this post.
Like last year, the highlight of WCEU (at least for me) was the conversation between Matt Mullenweg and Matias Ventura, the Gutenberg project lead discussing the future direction of the Block Editor. As a part of his presentation, Matias shared this video that covered upcoming changes to the block editor as it moves towards full-site editing, including:
- Patterns: more options for creating, saving and sharing them.
- Transitions: a smoother, more integrated way to change from one type of block to another type directly in the Editor.
- New and enhanced design tools.
Take a moment and watch the video below:
I don’t know about you, but I felt a little dizzy after watching this. 😉 Some of the highlights shown are already integrated here on WordPress.com.
For the adventurous, you can get a taste of the full block editing experience right now by heading to your site’s WP Admin Themes dashboard (yoursite.wordpress.com/wp-admin/themes.php) and activating the Blockbase theme. It’s only available via WP Admin and, because it is experimental, I strongly recommend trying this out on a test site and not your public WordPress.com website.
On the other hand, if you are still trying to get to grips with the Block Editor itself, I’m here to help! Here are some previously published posts on this site:
- Getting One’s Head Around the Full Block Editor
- Behind the Wheel of the Block Editor’s Classic Block (understanding tools and sidebars)
- The Block Editor: A Block Management Guide
- Need some background? The Block Editor-A Fireside Chat
If the block editor is still not making sense to you and you’d like some one-on-one help, leave a comment and I’ll be in touch.
As always, the information in this post is correct as of publication date. Changes are inevitable.