How to test Gutenberg and update to WordPress 5.0

After much anticipation and trepidation, WordPress 5.0 is here. The most visible change is the new Gutenberg editor, which replaces TinyMCE and also creates new headaches.

As with any major change that dramatically alters the user experience (UX), there are concerns about how people will react to it and what it’s going to inadvertently break. This article addresses the latter and explains what you can do about it.

  1. How to test new versions of WordPress
    1. Development environments
    2. Testing what works and what doesn’t
    3. What to do if a plugin breaks Gutenberg
  2. How to restore a broken WordPress site
  3. How to update your live site after testing and fixing it in a Development environment

Become a member to read the full article or sign in

The Pro Member subscription is $7/mo (billed annually)