{"id":21615,"date":"2019-02-18T12:04:08","date_gmt":"2019-02-18T10:04:08","guid":{"rendered":"https:\/\/themeisle.com\/blog\/?p=21615"},"modified":"2019-02-18T13:03:00","modified_gmt":"2019-02-18T13:03:00","slug":"how-we-prepared-themes-plugins-for-wordpress-5-0","status":"publish","type":"post","link":"https:\/\/themeisle.com\/blog\/how-we-prepared-themes-plugins-for-wordpress-5-0\/","title":{"rendered":"How We’ve Prepared Our Themes & Plugins for the New Block Editor in WordPress 5.0"},"content":{"rendered":"

Here at Themeisle, we started building themes and plugins six years ago. To be more exact, Themeisle’s first theme was published in the WordPress repo in July 2013. Back then, we were on WordPress 3.6 and people were doing the Harlem Shake. A lot of changes have happened in WordPress (and music) since then, and we’ve gotten better at making themes and plugins.<\/p>\n

Changes happening with the WordPress CMS are influencing our users, our products, and our business. And the recent release of WordPress 5.0<\/a> was no different.<\/p>\n

The new block editor pushed us to reconsider our product portfolio and come up with a plan to integrate the new block editor (AKA Gutenberg<\/em>)<\/a> into our themes<\/a> and plugins<\/a>.<\/p>\n

While the block editor was undergoing testing, we watched the community talking about it, bashing the initiative and the adversity it created. But as the release rolled out, developers found that most end-users were quite content with it.<\/p>\n

\n
At the time that we’re publishing this post, over 30% of users have updated their sites to 5.0, which is a considerable amount<\/a> even if some of them are still using the old editor.<\/p>\n

So here’s what we did to prepare a smooth transition to the new editor and a few considerations for users who are faced with the challenge of whether or not to use the block editor.<\/div><\/div>\n

\n\t\t
<\/div>\n\t\t\t
\n\t\t \t
\n\t\t \t\tHere's how @Themeisle prepared their themes and plugins for the new #WordPress block editor...<\/a>\n\t\t \t<\/div>\n\t\t \t
\n\t\t \tClick To Tweet \n\t\t \t\t<\/span>\n\t\t \t<\/a>\n\t\t <\/div>\n\t\t<\/div><\/div><\/div>\n<\/div>\n

Detailed block editor compatibility for our themes<\/h2>\n

Hestia<\/a>, Neve<\/a>, and ShopIsle<\/a> are our most popular themes at this moment, so we’ve paid special attention to integrating the themes’ options with the new editor. This results in a better UI and better control over how the changes in the backend translate to the frontend. The editing experience in our themes is more accurate and more similar to how a page actually looks.<\/p>\n

Neve<\/a> has integrated the Gutenberg editor seamlessly into the backend. Now your edits will look almost identical to the frontend.<\/p><\/div>\n

We’ve also looked at what we can offer within the blocks<\/a> and how we can bring more of each theme’s flavor into the blocks’ styling. We’ve made sure that all typography, color, and layout options (including both those from the theme or from the new editor<\/em>) make for a smooth transition between the backend and frontend, alongside default and custom blocks that beautifully match the theme’s styles.<\/p>\n

“We’ve made it our primary mission to make sure they have the best user experience possible. This is why, with the WordPress 5 in place, we’ve focused on paying special attention to the new editor and ways of integrating it in the themes.”Rodica Andronache, Theme Lead at Themeisle<\/span><\/div><\/div>\n

New block templates for Hestia and Neve, powered by Otter<\/h2>\n

Both Neve and Hestia recommend our new free plugin called Otter<\/a>.<\/p>\n

<\/div><\/div><\/div><\/div>\n\n