Gutenberg is an upcoming reality for all WordPress users. Please take your time to understand how this new core functionality works and discuss the implications with your developer.
What is Gutenberg?
If you’re familiar with page builders (like Beaver Builder or Divi), you’ll notice some similarities in the new “block” setup of the Gutenberg text editor.
(It’s worth noting that Gutenberg is touted as the first step in a giant, 3-part WordPress revision project, which is supposed to include page templates and a full site customizer.)
Currently, Gutenberg has been released in a beta plugin mode for testing purposes (try it here).
When development is totally finished, however, a new version of WordPress (5.0) will be released, with the Gutenberg page builder included.
Recommended: Create a Staging Site Before Installing Gutenberg
In the meantime, we recommend that you create a staging copy of your website to test its compatibility with Gutenberg.
How to Use Gutenberg With AccessAlly
There are two options to use AccessAlly’s shortcode adder with the Gutenberg interface:
Option 1: Use the AccessAlly Block
Click on the “+” symbol on the top left and select the AccessAlly option.
Option 2: Use the Classic Block
Select the classic block (it is in the “formatting” section, you may have to scroll down a little to locate it).
Inside the classic block, you’ll see the shortcode adder appear in the toolbar.
Methods to Disable Gutenberg
Gutenberg will soon become a standard part of WordPress. However, if you need more time to work through plugin compatibility and functionality issues, you might wish to use one of these methods to disable Gutenberg on your site.
Once again, please take the time to discuss this topic with your developer to ensure a seamless transition with the new WordPress release.