In WordPress 5.0, the editing experience will be changing dramatically. I’ve written information for my clients about this change in Prepare for WordPress 5.0 (Gutenberg).
With the editor moving from one general purpose editor field to a series of special purpose blocks, there will be a need for creating custom blocks. In another post, I’ve explored building WordPress Gutenberg blocks without npm.
In all of the information I’ve found on creating custom blocks, the examples define the
Through this tweet by Jason Bahl
Next step: custom block without writing and custom JS at all…just use the (not really existent) Server Side Registry to define blocks and let whatever client (Gutenberg, iOS/Android, WP-CLI) interact with the blocks. 😀…one day, hopefully 🤞
— firstname.lastname@example.org (@jasonbahl) May 17, 2018
Gutenberg as More Than an Editor
Moving Along this Path
In a first step towards this language-agnostic schema for blocks,