With Gutenberg nearing an official release in WordPress 5.0 we wanted to shed some light on common questions we’ve been seeing as it relates to our products.
As an X or Pro user, what does the Gutenberg release mean for me?
Surprisingly, not much at all. Nothing in the X, Pro, or Cornerstone workflow is changing. If you build your pages with our Content Builder, the only difference is that the “Edit” button to launch the builder is in a different spot. While Gutenberg is replacing the native WordPress post editor, it doesn’t change anything in our products or how you would use them.
Are X, Pro, and Cornerstone fully compatible with Gutenberg?
Indeed! We’re always committed to making our products work flawlessly with WordPress core. The latest versions of X, Pro, and Cornerstone are full compatibility with Gutenberg.
I would like to start creating pages in Gutenberg. What does this mean for me if I’ve been using the Content Builder?
As a theme provider, some of our customers use our Content Builder alongside other page builders. You simply choose which builder to use when you create a new page. Things will be no different when it comes to Gutenberg. Just start building with Gutenberg and that page will use it on the front end as well. The only thing to consider is that you won’t be able to switch between builders - saving a page in our Content Builder will overwrite what you built in Gutenberg. There are appropriate warnings to prevent you from losing your work and it follows the same process it did with the WordPress classic editor.
I have a bad feeling about this. Can I avoid Gutenberg altogether?
While this isn’t directly related to our products, we’ve seen some negative feedback from those who are not impressed with the new interface. You can install the Classic Editor Plugin to restore the original post editor and opt-out of Gutenberg if you wish.
Will there be any kind of “integration” with Gutenberg?
At this time we are ensuring that our products are free of any conflicts, but we’re not adding anything to Gutenberg or using any of its features directly in our themes. We’ve never altered the native WordPress editing experience, and Gutenberg is the next generation of that editor.
Fundamentally, this is a non-event for the majority of Themeco users. It is significant from a WordPress core perspective, however the experience you've grown accustomed to in X and Pro is already significantly ahead of the curve with regards to page building especially when you take into account our near term development timeline. Much of what WordPress is trying to do with Gutenberg we have already addressed in our products.
How will Gutenberg blocks be styled in X and Pro?
Many of the Global Theme options like typography and colors, along with the base theme styling, will be applied. For example, your selected body and heading fonts will be used on your Gutenberg blocks. We’ve also enabled support for the default block styling. This way your blocks will look as close as possible on the front end as they do in the builder.
Will X and Pro support full and wide width images?
Yes. We’ve added styling to allow for these Gutenberg options. One caveat is that when enabling “wide width” it assumes you have a narrow enough container. Our themes allow you to adjust the site container size, so if your container is rather wide you won’t really get much of a visual effect. You can go to “Layout & Design” in Theme Options to reduce your “Site Width” (container size). A value below 80% should make the wide effect more pronounced.
I'm testing Gutenberg and see an issue. What should I do?
Remember that Gutenberg is still in beta so it is not ready for prime time. If you are seeing what you think is an issue after the official release, please do the following:
First, remember that with any new release there is the potential for issues to arise when updating. We’ve seen some cases where the Gutenberg editor doesn’t work. If this is you, try momentarily switching to the default WordPress theme and deactivate Cornerstone (if using X) to see if the problem persists. If it still happens with our products deactivated, you’re likely experiencing another plugin conflict, caching problem, or server configuration issue.
If the problem only happens when our products are active, please reach out to support and we’d be happy to look into it. Any issues that arise that are confirmed to originate in our products will be considered bugs and be addressed in an a official update. In our testing so far we’ve not run into anything, but we wanted to express our commitment to keeping things running smoothly in this time of transition.