“Try Gutenberg” is an initiative, currently scheduled for WordPress 4.9.8, to drive more usage of the Gutenberg editor plugin. A while back, I left an offhand comment listing issues I saw as blockers (those that caused data transformation that would be hard to recover from at scale). This comment apparently received more attention than I expected it to, so now we’re partially focused on making sure those blockers are resolved.
And have we been fixing blockers! A non-exhaustive list includes:
The reality is that no one is more concerned about the impact of AI on society than the people who are building it. Almost always, the more someone knows, the higher his or her concern level is.
Some might ask, “Isn’t it their fault? Aren’t they the ones building the technology that is going to replace workers?” But technologists, VCs, and entrepreneurs are simply doing all they can to push their companies and products forward. It is not their fault that the gains are being concentrated in the hands of a very few, and it’s nearly impossible for them to know and account for the downstream social and economic impacts. It’s OUR job—that is, it’s the responsibility of our government and leaders to account for the impact of innovation on human well-being.
Unfortunately, we are decades behind. And we need to speed up fast.
One investor said something to me on Tuesday that struck me as profound. “At this point, we don’t even need much more technological innovation. We could be busy for a long time just applying the tech we already have. What we really need is much more social innovation.” He’s on to something. He’s a good man who is supporting my campaign. And there are many others like him.
Looking for something to do at Contributor Day? We could use your help!
The Gutenberg Migration Guide is a crowdsourcing project to document WordPress Classic Editor customization points and their Gutenberg equivalents (if such exist). media_buttons is the quintessential example; whereas you might’ve used this action previously in the Classic Editor to register a button, it no longer exists in Gutenberg and the block inserter is its direct equivalent.
We want the migration guide to be as comprehensive as it can be. This is defined as:
Identifying as many integration points as we can find. For instance, there are already 14 actions / filters listed. Some are commonly used, while others are not. As long as we have a good example for how the integration point is used, it makes sense to include in the guide.
Whenever possible, documenting how feature parity can be achieved with Gutenberg. Some integration points do already have Gutenberg equivalents. Others don’t yet, and that’s alright.
You can help make the migration guide more comprehensive. If you don’t have any examples of your own to include, here are a couple of places you can start looking:
Everyone can contribute to the migration guide, regardless of skill set. All you need to do is open a new GitHub issue and report the incompatibility you’ve found. Screenshots and GIFs are tremendously helpful. If you know the underlying problem, then please include that too. If all you know is that a given plugin’s feature doesn’t work in Gutenberg, no worries; simply open an issue and we can help track down the cause. Identifying examples of breakage are what we need help with most.
Feel free to join #hosting-community in the WordPress.org Slack if you have any questions, etc. Thanks for your help!
It was a great event and I was really happy with my performance. Notably, I hit faster and faster splits in the last five miles: 8:19 (mile 9), 8:02 (mile 10), 7:44 (mile 11), 7:51 (mile 12), and 7:23 (mile 13).