Another Roundup of resources, discussions and news around Gutenberg – the new visual editor coming to WordPress in 2018 – Covered: Getting ready for site owners, photos from meetups and WordCamps and block development
Gutenberg Development Updates
If you don't like change, you're going to like irrelevance even less.
On Friday, hundreds of WordPress developers spent a few hours learning how to develop Gutenberg blocks at the Developers Workshop prior to WordCamp Miami.
If you make a living out of building solutions for clients with WordPress, then you need to follow along with these development resources.
We'll add videos from the livestream when they become available on WordPress.tv
Future of WordPress Development
Setup & Introduction to Gutenberg: Tooling And Terminology
Next up was Zac Gordon who walked us through the Gutenberg repository and gave insight into the overall architecture of Gutenberg and the development process for you own Gutenblocks.
Creating Your Very First Gutenberg Block
Brian Richards is the creator of WPSessions.com and has been using WordPress since 2007 and training and leading development teams since 2011. In addition to investing his time into training, Brian has had the opportunity to work with many amazing WordPress agencies and experts over these last several years. This has allowed Brian to help develop sites for Microsoft, Disney, TIME, YMCA, and numerous others. Brian has an affinity for self-directed learning and helping others to develop skills and workflows to better solve important and complicated problems. He can’t resist helping good people do great things.
Building Custom Gutenberg Blocks: From Static to Dynamic
Josh Pollock is the founder and lead developer of Caldera Labs, creators of Caldera Forms, a drag and drop responsive form builder for WordPress. He is also a WordPress core contributor, author of two books about WordPress development and a member of The WPCrowd.
Mark Wilkinson hosted a show with Tammie Lister (design lead), Matias Ventura(dev lead) and Miguel Fonseca (gutenberg dev). The discussed roll-out and community input around Gutenberg as well as design issues and answered questions from viewers.
Gutenberg's Github repository is now listing three distinct milestones
Featured Complete – Remaining high-level features to conclude the first version of Gutenberg. (7 open issues)
Merge ProposalTracks progress and tasks towards a merge proposal candidate. (71 open issues)
5.0 Items to work on for a 5.0 initial release but which don't have to be part of merge proposal. (16 open issues)
The total number of open issues right for Gutenberg are 589. You can follow along weekly meeting on the WordPress Slack channel #core-editor Wednesday's at 14:00 UTC
During Monday’s AMA with Matt Mullenweg, the question came up, “When is Gutenberg considered ready to be released in Core?” What does it look like? Another listener asked if Matt could narrow down the release date for WordPress 5.0 apart from “Not April” — You need to watch the video to hear Matt’s answers, but you’ll find a few links where the relevant discussions happen on the GitHub repository. — Birgit
What does it take to make Gutenberg ready for WordPress Core?
On GitHub you can review what's listed for the milestone "Feature complete". The team will work on this list for the next few updates of the Featured plugin. Once the features are released, the team might decide to do a couple of bug fix releases before starting on the Merge Proposal.
After Feature complete phase comes the Merge Proposal covering all the issues that need to be resolved to integrate Gutenberg as the default editor in WordPress 5.0. You can follow along with the Merge Proposal milestone on GitHub.
Some of the issues on GitHub have the label "Backwards Compatibility". Add what you find missing. This is particular important to make the switch experience bearable for users. Ideally those issues need to be fixed before the merge proposal. But it's not entirely clear where these issues fit into the timeline, as they also cover plugin compatibility issues and discussions on how to handle those.
What's missing? What do you need?
Gutenberg and WordPress Themes
Converting old posts to Gutenberg
About Plugins compatibility with Gutenberg
Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! — Elliot Condon
Yesterdays the core team released Gutenberg version 2.2 with a big new feature: a "Columns" block, introducing nested blocks. Matias Ventura writes: "it is labeled experimental, though, as it needs further work and has some browser hiccups." – There are – again – a ton of other changes in this release. Matias added sections to his change log and added links to the respective Github issues. This is important if one wants to research the history of a decision.
Sending Greetings from Merida, Mexico: The colors of the houses reminded me of background-colors for Gutenberg Blocks — Birgit
I tested a two column layout on one of our development sites and we were quite successful. Take a look:
From the podcast & video world:
At Conferences and WordCamps
News from Plugins Developers
Gravity Forms started transition to Gutenberg
Elliot Condon shares screenshot of Gutenberg blocks for Advanced Custom Fields (ACF)
Information for Users and Bloggers
A thorough introduction to Gutenberg published by FireCask
In this interview, Nathan Latka and Matt Mullenweg discussed an array of topics, leading Automattic, investing, and his life around WordPress. We transcribed the part about Gutenberg. You can listen to rest of it on Soundcloud.
At timestamp 23:50 Nathan Latka’s asked Matt Mullenweg:
Gutenberg. Why make it your first project when you get back, what is it and how can my listeners go and use it?
Matt Mullenweg's answer
First what I am going to say is Gutenberg is still in beta. It’s an open beta. When you search for it in the plugin directory. Search for Gutenberg. You’ll see it and you will be able to install it.
The big idea is that we can move editing post and pages from kind of a document model, where you type a bunch of text in a box, to a model where you take this building blocks. Text, lists, but also things like maps, videos, contact forms, products, and you can rearrange them in blocks, like building things with Legos. So this is how the best websites and the best layouts and everything work. And just we wanted to make something in core of WordPress that made it easy for everyone to do this.
Changing the editor, since that really in many ways the heart of WordPress, is by far the most controversial thing you can do; and the hardest. Because, lots of people are very used to how WordPress worked for the past 14 years and there is lots of opinions on it. And it’s also just technically difficult, what we are building. To build it a way, that works; for the you know, many, many, many, many of tens of million WordPress sites out there. It just tough. It’s much harder than doing it in a plugin.
That’s part of why we decided to tackle it. WordPress has a great set of developer, has a great set of leaders over the many years, particular Helen Housandi, who’s been super incredible. But for this, well, let’s tackle the very, very hardest thing. It’s definitely a stretch both leading core and leading Automatic the company. Both are practically full time jobs. I am working with great folks on both sides, and i am able to have a foot in both.
My hope is once we get some of the most really, really hard things out of the way, that we will setup WordPress for the next decade of what going to happen with it.
Are you optimistic about the future of open source? What are the things that you see that drive your optimism about WordPress? It seems like there’s a lot of focus on weaknesses and threats, especially around legacy elements in WordPress and now change resistance over Gutenberg, which presents a big unknown.
Dan Krauss, Post Status
Steve Burge, PublishPress
That’s a big question. Let me quickly describe another couple of open source projects [that] went through a massive change like Gutenberg.
In the Drupalworld, we just went through Drupal 8. It was done with the best of intentions. Everyone wanted to update Drupal for the modern marketplace. But scope creep set in, and before anyone knew it, years had passed. The goal posts had shifted. The technology chosen at the beginning of the process wasn’t so hot by the end of the process. The upgrade path was very difficult, and both developers and end-users were reluctant to migrate.
In the Magento world, we just went through Magento 2. All the things I said about Drupal 8 can also be said about Magento 2. Except for some reason, it kind of worked. Magento was a struggling platform for several years, but [now it] has a new energy behind it. The community seems re-energized by the fresh technology.
But the alternative is stagnation
So don’t trust anyone who says they know what the impact of Gutenberg will be on WordPress. This could go in any number of directions, both positive and negative. Big challenges lie ahead – and Daniel is tackling many of them! – but the Gutenberg is team is making enormous progress too.
I think everyone involved with Gutenberg knows that this is a major roll of the dice. It’s perhaps the major roll of the dice in WordPress’s history. But the alternative is stagnation, and the Gutenberg team are open about the risks and the rewards.