Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
Can you clarify future plans for SiteOrigin’s integration with Gutenberg? I have a number of clients whose sites I built using the SiteOrigin page builder and as I update them to WP 5.0 I need to explain how things work and how they might change.
So far, I really appreciate the functionality allowing a page builder row as a Gutenberg block. Will there be a way to transform existing Page Builder layouts to Gutenberg blocks at a later date? If I create a new block editor page, could it be changed to a siteorigin page builder page at some point in the future? Are there any other behaviors that I should be on the lookout for that might complicate current websites?’
Thank you!
Hi Adam
Thanks for reaching out.
If you’re running the latest version of Page Builder you can now go to Pages and use the Add New drop-down arrow to choose between adding a Page Builder page or a Gutenberg page. This offers the choice of adding a Classic Editor page without the need for the Classic Editor plugin.
For complete client sites where users are familiar and happy editing with Page Builder, installing the Classic Editor plugin is a viable option. There is no change to the editing the experience if the Classic Editor plugin is activated.
It currently isn’t possible to automatically migrate classic or block editor pages in either direction. With the rate at which Gutenberg has been changing and the various issues that have been coming up, we didn’t feel it was safe to put your existing Page Builder content at risk with automatic migrations. You can manually migrate pages using the JSON layout downloaded from LayoutsImport/ExportDownload Layout. At this stage, I, unfortunately, can’t say whether there will be an automatic migration option in either direction in the future or when that might take place.
Hope this helps. Let us know if you need a hand with anything.
Thanks for the reply! It’s definitely an interesting transition. So far so good on my end, though I have no idea how receptive my clients will be to such a dramatic change with WordPress. Thankful they provided the classic editor option and that you all at SiteOrigin have clearly worked hard to integrate intelligently with Gutenberg.
It is indeed!
It’s worth considering all of your options for client sites. There are time (learning) and budget constraints to be considered. Each project is at a different stage in its life cycle. All of those aspects influence the choice of editing option. It’s also an option to remain on WordPress 4.9.8, allow the work year to conclude and tackle upgrades/choices in January.
Thanks for your support. The team has been working tirelessly on our Page Builder and Widgets Bundle blocks. We’re on GitHub if you ever want to take a direct look at the work being done: https://github.com/siteorigin.
As questions arise, please let us know, we’ll do our best to assist :)