Gutenberg archives

Last September, we released our first digital story; Diversity, inequality, and prejudice; a sociological exploration. This is the first in what will, hopefully, become a small series of stories that really define our mission, company culture, and broader vision. With these stories, we want to explore the possibilities the WordPress block editor has to offer …

If you have limited knowledge about JavaScript, building native Gutenblocks can be a challenge. All the documentation contains JavaScript. Yet, when you build a theme, most things are done with PHP. Advanced Custom Fields (ACF) built a great bridge to close this gap, allowing you to build Gutenblocks with just PHP! As ACF is an …

What’s it like building blocks for the new block editor for WordPress? Turns out it’s pretty hard. Our front-end developer Sjardo Janssen spent a considerable amount of time learning how to do this. The new editor is built on technologies unfamiliar for many front-ender, Sjardo found. He also found it incredibly hard obtaining what he …

In our previous post on how to theme our HowTo content block for Gutenberg, I explained the HTML structure of the block. I walked you through a few approaches to styling the generated block to make it blend in with your theme. With the release of Yoast 8.2 we've not only included the HowTo structured …

With the launch of Yoast SEO 8.0, we’ve released our first real integration with Gutenberg. Now, with Yoast SEO 8.2 we took the first step into how to combine the power of Gutenberg with the field of SEO. More specific: the user-friendly implementation and usage of structured data. I won’t go into the technicalities, so …

At Yoast, we organize a company-wide user testing session each month. In these sessions, we ask our employees to take a look at a product or feature. On October 12th we focused on user-testing Gutenberg. We did this to gain a better understanding of how different users work with Gutenberg. This knowledge is sure to …

In the upcoming weeks, WordPress will choose a UI rendering framework. I’ve heard many claims plugin / theme developers will still be able to use whatever they like, regardless of what WordPress chooses. I think we shouldn’t count on that, nor should we focus on providing interoperability at this point. Instead we should focus first …