First of all, as opposed to what has been the development and integration of Gutenberg in WordPress core, this new functionality of ACF recovers the WordPress way of doing things.

That is to say, a way that makes accessible what, at the outset, is a complex process. That's what made WordPress what it is, a powerful tool that almost anyone can use and transform on its own, without necessarily being an experienced programmer.

ACF expands WordPress functionality by enabling a user-friendly interface to create specific content types in a very accessible and inclusive way. And with ACF Blocks, it extends that inclusiveness to the new WordPress editor. So, thank you Elliot Condon for this brilliant effort, which gives hope to many users who, not being developers, want to create their own sites with special features.

Thanks also to all those who have sought to find simpler and within reach ways of building blocks for Gutenberg.

Gutenberg is an innovative and challenging project that can effectively facilitate page creation and offer an experience far beyond a WYSIWYG editor, shortcodes or even page builders. But, at the same time, it creates a split between the average user and the advanced developer.

I believe that, if there is anything that can save the Gutenberg experience, it will be a way to control the building of blocks without having to dominate several programming languages, development environments, etc.

Before being merged into core, Gutenberg should ensure this flexibility. It should not be a developer-centered project, with its doctrines and theories. It should be a project centered on the average WordPress user and its needs.