WordPress 5.0 will bring the biggest and most exciting change to the WordPress editor experience, ever, and we want you to be ready. Much of this post will be useful for anyone running enterprise WordPress applications, anywhere, but it also mentions some things we’re doing specifically on the VIP platform or for our customers. Wherever possible we’re taking the tools we’ve developed for our own systems, and making them available for the community to take advantage of as well.
- Try out the Gutenberg editor as a front-end experience. At our TestGutenberg.com site, you can easily try out the latest version of the Gutenberg editor on a standard WordPress site to get a feel for what it’s like to compose and edit with blocks. If you don’t already have a test environment with Gutenberg set up, this is an easy way to introduce your whole team and everyone who touches the WordPress admin to the new interface. This site is free and available for anyone to use.
- Prepare your teams.There are a wealth of learning materials across the community thanks to the work of countless creators, including both free resources and videos and courses offered for a fee. Our documentation page points to a number of community resources and write-ups, and Gutenberg.news tracks just about everything that comes out across the community.
For VIP clients, we’ve partnered with well-known WordPress educators Zac Gordon and Joe Casabona to develop our own videos on the Gutenberg project. VIP clients can get all the details on how to access these videos on the related Lobby post.
- Test your customizations. No matter where your projects are hosted, you’ll want to start testing and planning now. We recommend developers to set up a local testing environment in which you can test all customizations and integrations to see how they work with Gutenberg prior to exposing it to users. To assist with that effort, we are working on compiling Gutenberg readiness information from partners and will share it when available. There is also a recently released Gutenberg compatibility library that may be helpful: https://github.com/danielbachhuber/gutenberg-plugin-compatibility#gutenberg-plugin-compatibility
- Plan for a smooth transition. Based on testing and conversations with your teams, determine how and when you want to implement the new interface in your workflows. As mentioned previously, installing the Classic Editor Plugin will allow you to maintain the legacy editing experience after you install WordPress 5.0.
For VIP clients, we’re developing a tool that will give our clients fine control over how Gutenberg surfaces at the Post and Page type level, both before and after 5.0 is deployed. This will give teams the ability to test more granularly ahead of time and phase the new editor in as needed based on team needs. It will also allow them to easily set a state that will persist after 5.0 launches, and we will have it set it to keep the legacy editor on by default.
We are working on a public version of this plugin as well and will aim to release it shortly after we have it squared away for use on our own systems. More on this soon!
We’ll keep this documentation page updated with all of the latest information about Gutenberg at VIP.