If all goes well, WordPress 5.0 with “Gutenberg” will be officially released on 19 November 2018.
If you own a WordPress website, chances are that you've heard about Gutenberg. What you might not have noticed is that last week Gary Pendergast, a WordPress core contributor, shared a proposed schedule that will see WordPress 5.0 “Gutenberg” officially released on 19 November 2018.
In fact, the proposed schedule looks more like this:
- 19 October 2018: WordPress 5.0 Beta 1 will be available for beta testing.
- 30 October 2018: WordPress 5.0 Release Candidate 1 (RC1) - this marks the end of changes to the upcoming release.
- 12 November 2018: If needed, a Release Candidate 2 (RC2) could be released.
- 19 November 2018: WordPress 5.0 “Gutenberg” should be officially released if no serious issues are discovered with RC1.
If additional time is needed, then the previous dates could change and, WP 5.0 could be released up to 8 days later on 27 November 2018. If, however, the WordPress team need even more time, then the release of WordPress 5.0 will be delayed to 2019. The schedule would change to the following:
- 08 January 2019: Another WordPress 5.0 Release Candidate.
- 22 January 2019: WordPress 5.0 “Gutenberg”.
In case you're wondering what Gutenberg is.
In a nutshell, Gutenberg is a new visual content editor that uses the power of blocks to enable the creation of all types of content in WordPress. These blocks aim to transform how you interact with WordPress by streamlining the editor with modern CSS and HTML coding standards.
So what's the big deal?
Well, Gutenberg, this new visual content editor for WordPress, will be merged into the WordPress core platform with the release of WordPress 5.0. In other words, Gutenberg will become the default visual editor on your WordPress website.
Try it beforehand.
You can test how Gutenberg will work on your website now, by installing the Gutenberg and Classic Editor plugins on WordPress 4.9.8: if your website continues to work as expected, then you should install the Classic Editor plugin on your site now, and any subsequent upgrade to 5.0 will cause the Classic Editor to remain the default.
Are you ready for Gutenberg?
If you’re worried that the new visual content editor could disrupt your WordPress website, or whether it is compatible with your current themes and plugins, you can also disable it. That’s probably the safest thing to do if you’re not ready for whatever reason. You'll need to make sure to install the Classic Editor plugin before WordPress 5.0 is released, to keep using the current editor, as Gutenberg will be enabled by default in WordPress 5.0.
Install the Classic Editor plugin to keep using the current editor until you’re ready to make the switch.
And for e-commerce websites...
If you run a WordPress powered e-commerce website (WooCommerce, etc.), consider that these November release dates are so close to the biggest sales season of the year. You might want to consider waiting until after the January sales period before enabling Gutenberg; so you don't risk throwing a wrench in your (and everyone’s) festive sales season.