skip to Main Content
WordPress 5.0: The Gutenberg Edition

WordPress 5.0: The Gutenberg Edition

On Monday, December 3, it was quietly announced that WordPress v5.0, the Gutenberg Edition, would have an official release date on Thursday, December 6. This effectively gave everyone about three days to be sure that their sites were ready for the upgrade.

Over the past several months, software, plugin, and theme designers alike have been working diligently to ensure that their products would meet the new standard and be fully functional with the new editor. It’s been a long haul for many, and like it or not, Gutenberg is coming and will be here to stay.

This article is not about “what you need to know about Gutenberg.” There have been plenty of those articles written, and if you’re interested in them, we’ve provided a link to some of our favorites at the end of this article. Instead, this is more along the lines of a “What You Need to Do” article.

The short answer is, “test.” The long answer is, “test with DesktopServer and WPSiteSync.”

There is no doubt that testing your site locally is an important step in a normal workflow, but now, more than ever, it’s vital that you test before you find your holidays ruined because something did not work.

In a site with various plugins and specialized themes installed, it’s possible that you’re going to run into a glitch or two. To that end, we have thoroughly tested both DesktopServer and WPSiteSync with the latest Release Candidate of Gutenberg and are confident that it will be fully functional with the final release.

So, give yourself some peace of mind, download your site with a backup plugin like Duplicator or BackupBuddy, import it into DesktopServer Premium and run all the tests you need to make sure you don’t get caught holding the bag.

If you’d like to test DesktopServer Premium with the latest version of Gutenberg, you can read about the “Latest Gutenberg Dynamic Blueprint” here. This blueprint will always download the latest version of Gutenberg, enable it, and configure it. If you aren’t ready to make the jump, you have the option to install the “Classic Editor” Plugin which disables Gutenberg, allowing you to continue to use the original content editor. We will have a dynamic blueprint for that once WordPress 5.0 is released, and many hosts have announced that they do not plan to perform the upgrades until after the New Year.

So, when it comes to Gutenberg, you do have options, but the first and foremost step in that transition is to test! With the proper workflow tools, like DesktopServer Premium and WPSitesync, it couldn’t be easier.

What You Need to Know About Gutenberg Articles:

Gutenberg: What You Need to Know (WPEngine)

The Gutenberg WordPress Editor: 10 Things You Need to Know (iThemes)

What You Need to Do to Prepare for Gutenberg  (StudioPress)

WordPress Gutenberg Guide: How to Build Your Next Site With the Revolutionary Editor (codeinwp)