Earlier today, I started a Storify to collect all the resources and blog posts about the Gutenberg Editor. It was released in it 0.2 version just around WordCamp Europe. Matt Mullenweg ran a demo video during his interview with Om Malik on WordCamp Europe Second Day.
The Storify has all the links and post from all corners of the WordPress Community. If you don’t enjoy working with unfinished software just read through some of the blog posts to get an idea of how big the changes will be for you as a user of WordPress. Just read some of the blog posts.
It will not be in the next version 4.9. And it’s not clear when WordPress 5.0 will come out.
It definitely depends on how far the Gutenberg Editor can be pushed forward.
Head-first into Gutenberg Testing
Install the Gutenberg plugin on your non-production site. As long as Gutenberg is not officially released I would not use it on any production site. Be warned. If you don’t have a testing site or development site at your disposal but still want to test it, scroll further down to request access to our test site.
Are you an Accessibility Expert? WordPress needs your help
— WordPress Accessibility Team (@WPAccessibility) July 5, 2017
— Scott Vinkle (@svinkle) July 8, 2017
The design team around Gutenberg Editor published a few questions from the community. For instance: “How do I make my own block?” Or “How will old metaboxes (PHP) work?”. You can read the answers on GitHub.
For Developers creating your own Blocks for Gutenberg
- James Nylen from Automattic published on Github: Gutenberg Examples
- Amad Awais, WordPress Cord Contributor published on Github: Gutenberg Boilerplates
First Steps w/ Gutenberg editor
On our Testing & Training site, I posted small notes about my first steps with Gutenberg.
If you’d like to get an opportunity to test Gutenberg, but don’t have a testing site available, enter your information in this form and I’ll set-up an account on our test site. The only requirement beyond the form is that you answer a few questions via our user survey.