Gutenberg is going to be the new default WordPress editor after the release of WordPress 5.0. For now, WordPress provides 2 plugins:
Both “Gutenberg” and “Classic Editor” can be installed and used simultaneously. At the same time, you can choose to have only one of them.
Classic Editor will allow you to restore the previous WordPress editor and the Edit Post screen and make it possible to use the plugins that extend it.
- you can experience Gutenberg Live Editor before installing it. This will help you to understand how it works.
- with Gutenberg, you can easily create “block based” content. See Gutenberg Live Editor.
- Gutenberg and SiteOrigin Page Builder are compatible with each other at this point (although they both are in beta stage), and are gonna work with each other in the future just fine.
- Gutenberg is not affecting pages, which are already created with SiteOrigin, in any way.
- SiteOrigin already provides a “block” called “SiteOrigin Layout” for Gutenberg which will allow you to create pages/content based on SiteOrigin widgets in Gutenberg.
- Gutenberg works well with Classic Editor.
- Gutenberg is still in beta stage and is laggy.
- Gutenberg is not working well with Advanced Custom Fields (ACF) for now (according to this article they’re gonna be compatible with each other in the future).
- Custom fields (and code), created before, using ACF, might need change (if you choose Gutenberg over Classic Editor).
- Gutenberg is laggy with the old TinyMCE (WYSIWYG) editor.
Our suggestion is to continue with the idea of creating/having module based content management (using ACF) and stick with the Classic Editor until Gutenberg is stable.
Once Gutenberg is stable you can also think about switching from ACF to Gutenberg – since it’s giving us an opportunity to create custom blocks.