Gutenberg Compatibility in SiteOrigin Page Builder
Gutenberg has made massive strides in 2018. It continues to evolve into what we hope will be a worthy core editor later this year with the release of WordPress 5.0.
We’re doing our bit for the Gutenberg future of WordPress by adding compatibility to all our products. This will be available as a free update before Gutenberg is merged into the WordPress core.
Just like we made our Widgets Bundle widgets available to other page builder plugins, we’re making all our widgets Gutenberg compatible. So you can add our buttons, tabbed layout, maps, etc. to your Gutenberg pages.
The thing we’re most excited about though, is that we’re making our Layout widget available as a Gutenberg block. The SiteOrigin Layout block gives you the full power of SiteOrigin Page Builder, so you’ll be able to create fully nested, columnized, widgetized content, with advanced row, column and widget styling right inside Gutenberg.
Why are we doing this? Gutenberg is taking a more conservative approach to page building, which means there are designs and layouts that you just won’t be able to achieve. The SiteOrigin Layout block fills all those gaps, by allowing you to create advanced sections inside your Gutenberg pages.
This is just the beginning, we’re planning on adding a lot more features by the time Gutenberg becomes the core WordPress editor. For example, we’ll give you a migration tool that’ll let you convert your existing Page Builder pages into Gutenberg pages.
We’re excited to bring Page Builder and Widgets Bundle plugins, with over 2 million combined installs, into the future of WordPress. It’s our way of guaranteeing that your content is safe, as WordPress evolves into a more modern content creation platform.
Editing Options for Existing Page Builder Content
Once WordPress 5.0 is released you can rest assured that your Page Builder content will be safe and editable. Existing Page Builder content will be editable in one of two ways. If you’d prefer not to switch over to Gutenberg you can install the Classic Editor plugin provided by WordPress. Once activated, your existing Page Builder pages will remain exactly as they were pre WordPress 5.0. Alternatively, if you’d like to move over to Gutenberg, existing Page Builder pages will offer the option to migrate Page Builder content into a single Layout Builder block.
Editing Options for New Pages
If you have the Classic Editor plugin installed and add a new page, you’ll be able to choose between a classic page with the familiar Visual, Text and Page Builder tabs or a Gutenberg page. If you don’t have the Classic Editor plugin installed, your new pages will be Gutenberg pages.
Once Gutenberg is integrated into the WordPress core there will be much more certainty. The above update and roadmap is based on the information that’s currently available.
Thanks for the update. I’ve been wondering about this. I’m excited about the possibilities of Gutenberg, and I’m glad I can still use Page Builder in it.
Hi Lucas. Thanks for reading. The choice will be yours. Keep things as they are with the Classic Editor or move over to Gutenberg. Both will be supported. As we move closer to the 5.0 release we hope to have even more to offer. All the best :)
At a glance, it seems like your approach for the layout widget inside Gutenberg is just So Smart. It’ll be interesting to see how other page builder plugins follow.
HI Kel, thanks for your support :)
Thanks Greg. There seems to be a lot of changes with WP. What I would like is to see are changes that are incorporated into better and a more sophisticated appeal. I feel that site origin is my security blanket. I don’t want to wander too far into new fields and then need costly changes to stay abreast in a land where I have to learn a new language. I am about to go with a new site so migration will be important. I want to be a mountain climber with site origin tackle. I will go premium with all the new sites but right now I am trying hard to find the right handle to sell. Hank
Hi Hank. Great to hear from you. Thanks for your interest. After 5.0 you’ll have the choice to use Gutenberg and if you’d like, use Page Builder in a block OR install the Classic Editor plugin and then continue using Page Builder as you did before.
All the best with your new sites this year :)
Thank you, thank you! I have not been terribly impressed with Gutenberg so far. Being able to use PageBuilder within Gutenberg is a huge step forward.
Super, glad to hear you’re liking the look of the integration. More to come as we approach 5.0 :)
thank you for the update – looking forward to your integration and changes! I have been thinking about the future of your product and Gutenberg. Especially with several organizations dumping theme/plug-in support because of this transition. This knowledge makes me feel more confident in continuing my premium subscription and utilizing them in future developments. Keep us informed.
Hello!
Thanks for the update. So, when will the Page Builder be ready for integrating with Gutenberg as a block?
Hi Wolfgang. Thanks for commenting. We’ll release with WordPress 5.0’s first beta. The develop is public on GitHub if you want to follow along. Here is the feature branch: https://github.com/siteorigin/siteorigin-panels/tree/feature/gutenberg-compat.
This is great news! Thank you for keeping us updated. Love your page builder!
Thanks Patty :)
That looks terrific. The primary obstacle to using SOPB right now for inserting simple columns is that it takes over the entire editor. I love that it will show as a block in the normal visual flow.
Hi Greg. For sure, that does introduce some awesome flexibility. Thanks for posting.
This is cool Greg. I can see which page builder plugin I will use with WordPress :) I normally don’t like to rely on page builder as they are always bug. SiteOrigin seem to be the most stable and to see it with Gutenberg it seem the best combination!
Thanks Emily :) We agree, nice to have options for any given page or project.
Just one more reason why SiteOrigin is our no1 WordPress Extension!
Thanks for the support Marc, really appreciate it.
Great! I will wait for WordPress 5.0 & enjoy the update.
Thanks
Thanks Holmes :)
This sounds great. You’ve just taken a worry off my mind.
Thanks Julia. Whether you want to use Gutenberg or stay with the Classic Editor, we’ll be here to support.
Thanks, guys. I was not sure how Page Builder and Gutenberg will, or even if, work together, but you have seemed to solved this issue very nicely. The video is very encouraging.
Looking forward to using Site Origin Page Builder and Site Origin themes for a long time to come.
Thanks Dave, great to hear from you. More to come as we approach 5.0.
Awesome!!!! I’m excited to see what it can do. SiteOrigin stuff is great to work with. Thanks!
Thanks Carrie :)
Great Work! Thanks
Thanks Andrea, good to hear from you.
I wonder why you chose to add PageBuilder widget as Layout, and not as a SiteOrigin Row? Isn’t this will be confusing for users to have similar entities inside a SiteOrigin Layout as Rows and outside as Gutenber blocks? Will it be possible to drag Row to a different block with SiteOrigin Layout?
I understand that this is a difficult decision and I have no idea about the internal structure, but, in my opinion, Gutenberg Block should be equal to SiteOrigin Row, and that can become a great solution, with extended possibilities of PageBuilder. Hope your great tool find a right place together with Gutenberg.
Hi Vladimir, thanks for reading and reaching out.
All layouts can be rows, not all rows can be layouts. To give Page Builder users as much freedom as possible we decided to go with full, unrestricted layouts as blocks.
Hope that helps explain our thinking a little :)
All the best.
Its really incredible what you guys do for us customers.
I like the page builder plugin from siteorigin, its just awesome work what you can do an create.
I just wanna say a big thank you for that and the future updates.
Greets Maze
Thanks Maze, really appreciate the feedback, we’re really lucky to have users like you. We’ll have more updates as we approach 5.0 and will provide as many options as we’re able to. All the best with your projects in 2018 :)
This is exciting news. So as an Organizer of the Toronto WordPress Meetup group I tried to replicate the results for a planned upcoming meetup – https://www.meetup.com/WPToronto/events/247117765/ . I used Gutenberg 2.2.0 and the latest downloads of Site Origin PageBuilder and Widgets Bundle. Unfortunately i could not get any sign of SO Widgets in Gutenberg blocks. See here – https://www.theopensourcery.com/keepopen/2018/site-origin-pagebuilder-comes-to-gutenberg/.
So the question – when will SO in Gutenberg be testable in the Wild… so to speak.
Thanks for this development. as Gutenberg arrives it creates as many concerns as it promises through GutenBlocks so much design opportunity.
Hi Jacques
Thanks for your interest. Really glad to hear you’re jumping into this already. Unfortunately, we won’t have this branch integrated until the first WordPress 5.0 beta release is out. In the mean time, if you’d like to follow along, you can do so here: https://github.com/siteorigin/siteorigin-panels/tree/feature/gutenberg-compat. If you have a little experience with using Git then you could clone this branch and take a look. If not, we’ll have this out with the first 5.0 beta release. Sorry it isn’t included at the moment.
Thanks for your valuable suggestions, it is a must read guide for every developer.
Glad it helped :) More to follow.
Thanks so much for the post.Really thank you! Keep writing.
Thanks for reading :) All the best.
Thanksa lot for the post.Really thank you! Much obliged.
For sure :) Thanks for the support.
The release 2.6.2 – 23 January 2018 states:
” Prevent Gutenberg from taking over existing PB pages.
Remove PB metaboxes from Gutenberg editor.”
This appears to not allow testing of your page builder with the Gutenberg plugin on a test/development site.
Hi Roy
Thanks for reading. Unfortunately, we won’t have this branch integrated until the first WordPress 5.0 beta release is out. In the mean time, if you’d like to follow along, you can do so here: https://github.com/siteorigin/siteorigin-panels/tree/feature/gutenberg-compat. If you have a little experience with using Git then you could clone this branch and take a look. If not, we’ll have this out with the first 5.0 beta release. Sorry it isn’t included at the moment.
Thanks for the github link. Glad to see your folks working on integration with Gutenberg.
Super stoked about this. Great work Siteorigin team.
Hey Collins, thanks for reading and watching :) Appreciate the support.
When can we start testing siteorigin with gutenberg ? is there a beta somewhere? Im building new products that rely on Siteorigin and would like to get the Gutenberg side tested and implemented too.
Hi Bilal
Thanks for reading. Unfortunately, we won’t have this branch integrated until the first WordPress 5.0 beta release is out. In the meantime, if you’d like to follow along, you can do so here: https://github.com/siteorigin/siteorigin-panels/tree/feature/gutenberg-compat. If you have a little experience with using Git then you could clone this branch and take a look. If not, we’ll have this out with the first 5.0 beta release. Sorry, it isn’t included at the moment.
Very nice! Thanks for the hard work and dedication to keeping SOPB compatible with Gutenberg.
For sure :) Thanks for reading/watching. More updates to follow as we approach the 5.0 beta releases.
Hi Andrew,
Very nice! We use Site Origin on quie a few sites, so really glad to see this. Also not a fan of Gutenberg at all, so as hoped, SIte Oriign will be a solid fallback for us. Nice work!
Cheers
Avrom
Hi Avrom, thanks for watching and reading. We’ll have more updates as we approach the 5.0 release. You can definitely keep using Page Builder as is. Chat soon, cheers :)
Nice announce. I used always your excellent plugin and I hope nice things usinn this new options of siteOrigin.
Thanks for your support Reglero.
Hi,
I created a stage site today using Page Builder and Gutenberg.
I also had the Classic Editor activated as well.
The SiteOrigin Page Builder did not show up as an option in the editor, only Gutenberg came up.
I had to disable Gutenberg and then the Page Builder option would appear in the editor.
I just thought you should know this about the compatibility issue.
Thanks
Can’t get this to work running G 3.1.0 and your plugin 2.6.9 on a local install. Your plugin and G are working but just not together.
Any ideas?
Hi Bud
Thanks for posting.
Unfortunately, we won’t have this branch integrated until the first WordPress 5.0 beta release is out. In the meantime, if you’d like to follow along, you can do so here: https://github.com/siteorigin/siteorigin-panels/tree/feature/gutenberg-compat. If you have a little experience with using Git then you could clone this branch and take a look. If not, we’ll have this out with the first 5.0 beta release.
This sounds good. I look forward to seeing it in action.
I have tried Gutenberg and liked it. I backed off it for the moment because of the lack of integration.
For me the issue is how effectively the editor works on mobile platforms and, to a large degree, with Markdown. Gutenberg starts to look good on that score. On an older iPad it’s just not viable, but on newer tablets and mobile phones (who write posts on mobiles? – I do! :)) it’s looking good.
Hi Jerry, great to hear your feedback and what you’re looking forward to from Gutenberg. We’re full steam ahead on Gutenberg final touches this month. Updates to follow soon.
Hi, I want use Gutenberg with plugin siteorigin, but not works it, how I can use it? I need make my template for sell on themeforest. Thanks.
Hi Jerika, thanks for reaching out.
Unfortunately, we won’t have this branch integrated until the first WordPress 5.0 beta release is out. In the meantime, if you’d like to follow along, you can do so here: https://github.com/siteorigin/siteorigin-panels/tree/feature/gutenberg-compat. If you have a little experience with using Git then you could clone this branch and take a look. If not, we’ll have this out with the first 5.0 beta release.
I love you guys. When I heard about Gutenburg coming out I had two thoughts. 1. What a great idea. 2. Fuck me, please don’t take away my Page Builder. So glad to hear you guys are still going to be pushing through to the future and staying strong. I have come to “think” in rows and columns, and I couldn’t do what I have done for myself without you guys. Thank you so much for all your hard work. I’m a big fan in my own little way. It was you guys who made WordPress useable for me in the first place, and in turn, your plugins and work has taught me so much about this coded world we are all living in. Thank you so much. HagwonHelp will be open in the fall of this year. Thank you for making our little hobby/dream possible.
Hi Robert, thanks so much for your detailed feedback and support, we really appreciate it! When WordPress 5.0 is released you can also consider installing the Classic Editor plugin and keep your editor as it is now. For existing sites that you’re looking to keep nice and stable, that’s probably the best bet. Let us know if any questions arise :)
Hi.. so I’m a tad confused. I have installed both plugins (Gutenberg and Classic Editor) but can’t yet see any impact on Page Builder. I understood from your blog that I won’t see any difference until Gutenberg is part of WP release 5.0 but then the comments below seem to imply that you can use Gutenberg and Page Builder right now.
If so, what am I doing wrong.??
Hi Erica
Thanks for posting.
With the Classic Editor plugin enabled, everything remains the same. If you want to experiment with the Gutenberg plugin, go to Plugins, deactivate the Classic Editor, enable Gutenberg plugin and then go to Pages and create a new page. Your new page will be in Gutenberg.
We’ve merged our Gutenberg compatibility branch with Page Builder’s develop branch: https://github.com/siteorigin/siteorigin-panels/pull/561. The next Page Builder release will contain this compatibility.
Thanks for that Andrew. I guess I will wait until Page Builder and
Gutenberg are 'united' :-)
Thanks for your understanding :) We’re ironing out one small challenge and will release ASAP. (Please, keep in mind that Gutenberg is currently in beta, it’s best not used for important pages at this stage.)
There is no rush :-) Thanks for the update.
Hi Erica, the update has been released, it should be available in your dashboard in the next hour. A friendly reminder that Gutenberg and our compatibility are both in beta. If you’re testing, we suggest doing so on new pages :)
I installed the Classic Editor Plugin yesterday to disable Gutenberg, and noticed the Page Builder update today with Gutenberg support changes. I was wondering how the Classic Editor Plugin was going to work with SiteOrigin products and came across this article. Thanks for making it an option in your products to either go with Gutenberg or not. I will eventually enable Gutenberg, but like any major change to anything like operating systems, application software, BIOS updates, etc., past experiences and disasters made me smart enough and patient enough to wait a while for things to stabilize before upgrading.
Hi. Thanks for your feedback and support. For sure, that’s definitely a sensible and prudent approach to the situation. As questions arise, please feel free to leave a comment here or post on the forum. All the best :)
Thanks for the tip! Waiting with baited breath. It hasn't arrived yet :-)
Apologies, we’ve run into a problem with old versions of PHP. Servers using PHP 5.2 are showing an error. As a result, we’ve rolled back the stable version for Page Builder. We’ll release another update tomorrow to fix this problem. (WordPress recommends PHP 7, for most users this old version PHP error won’t be an issue.)
Think twice before supporting Gutenberg…
@photomatt: “Gutenberg will definitely be a whole-page builder, that’s the entire point of phase 2. All of the infrastructure is built to support that, so it will happen much faster than phase 1.”
https://twitter.com/photomatt/status/1037843717070057472
Hi Herb, thanks for reaching out. We do our best to provide options. For example, the Widgets Bundle works in Beaver Builder, Elementor and Visual Composer. Gutenberg is another choice. As they’ve always done, users should continue to evaluate the editing options provided by the market and choose the editing option that best suits their project. Gutenberg being bundled does provide it with an advantage. If Page Builder by SiteOrigin without Gutenberg best suits your project then it’s best to install the Classic Editor plugin which will be maintained. We’re here for any questions that may arise. In summary, Gutenberg is another editing / Page Builder option just like Page Builder by SiteOrigin, Beaver Builder, Elementor, Visual Composer and many others, you can opt out of it by using the Classic Editor plugin. Choose the Page Builder that best suits your site and preferences.
> you can opt out of it by using the Classic Editor plugin
That appears to be correct for phase 1 of Gutenberg which will come with WordPres 5.0.
As soon as Gutenberg is in core and enough people have updated to 5.0, they will add phase 2 of Gutenberg to core, the page builder.
The “Classic Editor” plugin won’t be able to opt out “phase 2”, you would need another “Classic WordPress” plugin (or something like “ClassicPress”).
Gutenberg is a trojan horse, wait and see.
When will the converting widget be ready. I’ve recently taken over our companies website and would like to get it all converted to Gutenberg. I’d be willing to beta test what you have so far. Our site is simple, just static pages.
Hi John. Thanks for reaching out :) We’ll start work on the migration tool as soon as Gutenberg has reached a stable state and dates are confirmed for the 5.0 release. At the moment, Gutenberg is still very fluid; in the last month, we’ve twice had to re-work sections of our integration due to changes in Gutenberg. At the moment, you could perhaps manually migrate a page over by creating a new page in Gutenberg, adding a Layout Block and then using the Layouts button > Clone Pages section. You could also use Layouts > Import/Export to download the page layout and then import it again. (Gutenberg is still in beta so we don’t recommend it for live sites).
Thank you for the video
For sure, thanks for watching :)
thanks for useful article
Thanks for reading. All the best.
Hi
Love Site Orgin Cudos to you!!!
I’m a little concerned with guttenberg and siteorigin will the both work?
Currently I have the Guttenberg plugin installed and the widgets show up
as a Guttenberg Block. As soon as I select that I feel it’s the good Old Site Origin
Will this continue to be the case?
Thanks
Tony
Hi Tony,
SiteOrigin Page Builder and SiteOrigin Widgets Bundle compatibility with Gutenberg are very important to us and we will continue to ensure compatibility between all three plugins. Please note that Gutenberg is still in development so it’s possible that a Gutenberg update may break compatibility. If this does happen, we’ll release an update to restore compatibility asap.
Due to the in-development nature of Gutenberg, I wouldn’t actively recommend using Gutenberg until it’s official release in WordPress 5.0.
Hi,
I made a staging website to install the gutenberg option on there. And non of the links that are on our pages (behind pictures) are working.
Is this because it’s still the beta version of gutenberg?
Thanks!
Evi
Hi Evi :) I’m not sure. Can you perhaps open a support thread and let me know once that’s done? We can assist further on the forum. https://siteorigin.com/thread.
“For example, we’ll give you a migration tool that’ll let you convert your existing Page Builder pages into Gutenberg pages.”
When will the migration tool for Page Builder into Gutenberg be available?
Thank you.
Hi, once Gutenberg makes it into the core as a beta release we can start work on that feature.
Is there an update on this? Doesn’t WP 5.0 with Gutenberg come out in a few days?
Hi James, thanks for reaching out. If you’re specifically asking about the migration tool, that isn’t ready just yet. As soon as we’ve ironed out the challenges with our core products we can focus on it. The situation is extremely fluid at the moment with changes often being made to Gutenberg that require us to rework sections of our integration. The release date for 5.0 was pushed back eight days, that’s the current situation, it might change. However, everything else is good to go. We’ve just released an update for Page Builder that resolved several challenges, we have an update for the Widgets Bundle out shortly. You can use Page Builder and the Widgets Bundle in Gutenberg or edit existing pages as they were before. You can also install the Classic Editor plugin and keep all pages in classic editing mode.
Is there any update on this? It seems very time critical now…
Hi Amy. Thanks for reaching out. Page Builder is available in Gutenberg as a SiteOrigin Layout Block and the Widgets Bundle is available as a SiteOrigin Widget Block. Hope this helps. If you have any technical usage questions, please open a support thread on the forum: https://siteorigin.com/thread where we’re actively assisting with WP 5.0 or email us on [email protected] if you’re using SiteOrigin Premium.
Hi,
I have a site with Site Origin builder installed but with the update to WordPress 5.02 and their Gutenberg editor, I am not able to edit content that I created using Siteorigin builder. I tried installing classic editor instead of Gutenberg that you guys suggest in the article, however, I do not get shown any options to edit content via Siteorigin builder and only see shortcodes, e.g.
. Can you please help me what to do? I tried it in Gutenberg editor as well but the same thing happens.
Thank you for your help,
Tomas
Hi Tomas,
I’m sorry to hear that you’re having issues after updating to WordPress 5.0. Please ensure you’re using the latest version of Page Builder by SiteOrigin and SiteOrigin Widgets Bundle.
If you are, please open a support thread on the forum: https://siteorigin.com/thread where we’re able to directly assist you with this issue or email us on [email protected] if you’re using SiteOrigin Premium.
Most of my site is done with siteorigin page builder. What do I do to make sure it is totally ready for Gutenberg? How do I install everything I need to install so it’s completely compatible when everything switches to Gutenberg permanently? I don’t want to risk losing my site by not having all the proper updates updated.
Hi Holly
If you want to keep your site in the Classic Editor you can install the Classic Editor plugin before upgrading to 5.+. If not, no preparation is required. Once upgraded, if you have the Gutenberg plugin installed, please deactivate and delete it.
And as Provo People advised below, it’s recommended to make a backup before any major updates. This can often be done via your hosting control panel.
For me, not speaking officially, just a guy not affiliated with Siteorigin,
based on cutting over a single site:
1) make sure siteorigin plugin is up to date
2) install the official "classic editor" plugin from WordPress
That's all, I upgraded to 4.9.9 before upgrading to 5.0.2.
Thats my experience but, not knowing what other stuff you have installed,
if possible setup a test site and test the upgrade process there. I don't do anything significant to the site I run without testing on a non –
production site.
Of course be sure you have a backup, I would say SiteOrigin has done well here, I'd be more worried about Genesis and other plugins.
Did I mention to make sure you have a backup? Haha
Hi Provo People, thanks so much for adding a helpful reply. Your advice is spot on!
do i need a special version from when it is fully compatible? i have two sites, where it is not compatible. i dont see the editor icons in the visual editor anymore. i also cannot switch from text to the visual view back, after i entered some code.
Hi Andreas
If you’d like to use the Classic Editor in WordPress 5+ you’ll need to install the Classic Editor plugin: https://wordpress.org/plugins/classic-editor.
Hope that helps.
Just FIY. After the last WordPress update ( December 2019 – version 5.3.1 ) I could not access my PB pages anymore. I did have Classic Editor installed. So I tried deactivating it (Classic Editor) and it worked as a charm: PB was live again on all pages. I still left the Classic Editor installed, I may reactivate it if I see an update to it… But for now I’m fine. Just wanted to give this suggestion for others struggling with PB “not working”.
Hi Linda
Thanks for reaching out.
At the moment, I can’t replicate the issue you’ve described. If you’d like us to investigate, please, open a support thread, we’d be happy to assist.
No thank you, Im fine, I solved my problem.
I THINK it must have been a Classic Editor compatibility problem, not yours.
PB showed up fine and dandy once I had deactivated Classic Editor.
This was with Vantage free theme.
And possibly a fringe situation, who knows. With this latest super upgrade of WP where Gutenberg was modified and implemented.
If everything doesnt work, you can propose to people that they deactivate
Classic Editor and voilà.
In other cases they must install it, whatever works, works!
Usually all SiteOrigin stuff upgrades without a glitch, keep up the good work!
Do well :-D
linda
Super, really glad to hear you’ve resolved the issue. We aren’t able to locate any issues with the Classic Editor so there is most likely something else that’s part of the problem. We’re here to assist if any questions arise in the future. Cheers for now :)
Hi there,
For some reason in my Multisite installation I just can’t switch a Page builder page to Block editor. I click the “Switch to Block Editor”, nothing happens. I’ve disabled the Classic editor plugin and activated again. I’ve clicked the “Revert to editor” button and then “Switch to…” but no help. The page just sticks to be under Page builder.
Any hints what to do/try?
Hi Katja
Thanks for posting.
It isn’t possible to automatically migrate classic Page Builder pages to the Block Editor. You can manually migrate a layout by editing the page then going to Layouts > Import/Export > Download Layout. Once the JSON file is on your desktop, switch the page to the default editor and delete the contents. You should then be able to switch the page over to the Block Editor where you can insert a SiteOrigin Layout Block and repeat the process but this time importing the JSON layout. It’s recommended you make a backup of your site before making changes of this nature.
Hi Andrew, thank you, works perfectly!
Super, thanks for the update, I’m glad to hear you’re making progress :)
This comes up pretty high in a Google search, any updates? I’m trying to decide whether to pull the Classic Editor plugin.
Hi Jim
You can use Page Builder in its traditional form or via the SiteOrigin Layout Block in the Block Editor. Pages built in the Page Builder tab should be able to hold that format without the need for the Classic Editor plugin.
Kind regards
Andrew