Since the conclusion of WordCamp US in early December, there have been a number of Gutenberg related items published to the web.
The following is a collection of items related to Gutenberg that I came across throughout December. Feel free to add to this list in the comments below.
Getting Ready for Gutenberg is a community-run initiative to help users and developers prepare for Gutenberg’s inclusion in core.
GitHub repo filled with Gutenberg example blocks.
Although it was published in August of last year, WordImpress has a good guide on how to contribute to Gutenberg without code.
Human Made published a Gutenberg White Paper that introduces people to the project, goes over a number of blocks, and provides advice on how agencies can prepare for the transition.
Ben Gilbanks has added basic support for Gutenberg to his Granule starter theme.
Andrew Taylor created a Gutenberg block that enables embedding Pens from CodePen.
Advanced Custom Fields announced it will focus on making ACF compatible with Gutenberg in 2018.
Meta Box has also announced its Gutenberg compatibility plans.
John Hawkins published a good post on the WebDevStudios blog on how existing content will be affected by Gutenberg.
Kevin Hoffman started a conversation on how plugin conflicts can be handled and communicated.
Amanda Rush published her thoughts and concerns related to Gutenberg’s Accessibility.
Scott Kingsley Clark, of the PODS framework plugin, announced they’re doing some cool things in the next release specifically for Gutenberg.
We’re doing some cool stuff in this next @podsframework release for Gutenberg specifically. Lots to do, but I feel like there will be cases for meta boxes and cases for blocks. We’ll have a template editor too, which will be powered by Gutenberg itself #gutenception
— Scott Kingsley Clark (@scottkclark) December 11, 2017
Freemius takes a look at what Gutenberg means for the future of commercial WordPress products. The post includes quotes from Beaver Builder, Elementor, and Visual Composer.
In episode 297 of WordPress Weekly, Morten Rand-Hendriksen joined John James Jacoby and I in a detailed conversation about Gutenberg, its potential impacts, and the idea of forking WordPress.
GiveWP is opening up its design process for how its product will interface with Gutenberg.
Beaver Builder takes a look at Page Builders in a Gutenberg World, the future of WordPress, and how its product will embrace compatibility with Gutenberg.
Eric Mann on Gutenberg and the road ahead. Mann supports the idea of soft-forking WordPress to provide time and help for those who can’t immediately update to 5.0.
Help contribute to Gutenberg by processing the usability tests from WordCamp US 2017.
Michael Hebenstreit details the potential costs for small WordPress businesses and independent developers to transition to Gutenberg.
WordCamp Miami 2018 is having a developer workshop focused on Gutenberg.
I’m seeing talk of how clients will be lost and users will leave #WordPress when #Gutenberg drops. As a former freelancer, in-house developer, agency designer, custom theme developer, and now plugin developer, here’s a practical look at how Gutenberg affects each.
— Kevin W. Hoffman (@kevinwhoffman) December 21, 2017
I think we will look back at 2017 and see it as the year the #WordPress project started to fracture. As much as the community desperately wants to see WordPress as an enterprise CMS, projects like #Gutenberg show it is anything but.
— Ben Furfie (@frontendben) December 28, 2017
WP4Good explains how they’re preparing for Gutenberg.
Riad Benguella published a visual example that shows Meta Boxes mostly work in Gutenberg. Benguella created a sample plugin called Gutenberg Custom Fields that provides a similar user experience to existing Custom Fields plugins.
A live demo of Gutenberg during the 2017 State of the Word.
Gutenberg and the WordPress of Tomorrow by Morten Rand-Hendriksen