I am generally seen as a critical voice to WordPress’s Gutenberg editor. It is true that I feel there are many places where criticism of Gutenberg is valid, such as in timeline, scope of initial releases, and methods of post storage. However, there has been a lot of criticism of Gutenberg recently that is based on misunderstandings or miscommunication of the project goals and the definition of a “block.” To that end, I’m going to try to distill down what the “block” paradigm is all about, and why it is crucial to WordPress’s future. Note: I am not a core part of the Gutenberg team, and have as much chance of misinterpreting things as anyone else. To that end, upon publishing this, I will be reaching out to the team leads, Matias Ventura, Joen Asmussen, Tammy Lister, and Matt Mullenweg to fact check me and correct anything I have gotten wrong. Blocks are not the visual editor Blocks, conceptually, are not a visual way to represent and edit post content, they also don’t have to be part of a content-picker menu, or drag/droppable. They can be used for those things, of course, and that is the workflow that much of the visible parts of Gutenberg
Share This