There are around 810 million WordPress websites, and the majority of them are using the latest version of WordPress. Gutenberg was released as the default editor with WordPress 5.0 in December 2018, changing how content is structured by replacing a singular long text area with a series of content blocks. While Gutenberg offered users and developers several advancements, not everyone was on board when it was introduced. Many still aren’t on board with the change years later. It is estimated that more than 7 percent of WordPress sites still use the classic editor rather than Gutenberg blocks.
Why Many WordPress Sites Still Use the Classic Editor
To be certain, there are several logical reasons why many WordPress sites still use the classic editor, including familiarity. Users and developers are comfortable with the classic editor and may hesitate to learn a new, block-based system. It’s more than familiarity and fear, however. There can be hassles with plugins and themes that don’t work with Gutenberg, as well as how to replace or update those. Users often don’t have the time to ensure that all elements work smoothly when the transition is made or that their staff has the training and support needed to maintain the site. There can also be difficulties with translating custom workflows and meta boxes, and recreating those customizations can be complex. Existing content may have to be converted to blocks, and manual adjustments may have to be made even after the conversion.
Some users have serious concerns about performance, believing that the classic editor is faster and less resource-intensive. They feel that the classic editor gives them more control over content layout and that Gutenberg’s block-based approach is more restrictive. The migration to Gutenberg could result in the need for optimization to maintain the site’s speed and responsiveness. In short, migrating from the classic editor to Gutenberg is no small feat.
Benefits of Gutenberg Blocks
Sure, there are challenges involved in migrating to Gutenberg. However, there are many benefits that this newer technology can provide. Some of those benefits include:
- An enhanced editing experience resulting from the more intuitive and visual interface. Users do not have to know coding to create a complex layout.
- Flexibility and customization with a wide range of blocks available for different content types and the ability to create reusable blocks and templates.
- Compatibility with future WordPress updates and improvements. Remember, there will come a time when the classic editor is no longer fully supported, leaving you at risk of privacy and security issues over time.
- Improved SEO and performance due to cleaner HTML output and built-in support for responsive design and modern web standards.
- Increased creativity, as users have the freedom to experiment with different layouts and designs without the need for extensive technical knowledge.
In short, while the classic editor has been good for quick content creation and easy to learn, it offers fewer design options, fewer editing capabilities, and lacks future support. For most users, it’s time to move on.
The Five Steps to Migrating to Gutenberg Blocks
Migrating to Gutenberg blocks can be complex, but it is very possible.
Step 1: Assessment
The process starts with an assessment of your existing site to evaluate the current setup, plugins, and themes. You must identify which areas need to be updated or replaced, as any of them can make for a more complicated migration. You should also check the compatibility of your themes and plugins with Gutenberg and budget for development work if your custom functionalities won’t translate to blocks.
Step 2: Backup
Once your assessment is complete, creating a full site backup, including the database and files used, is important. You should also create a rollback plan to use if you need to revert to classic. This is your safety net against losing your site design if your migration is unsuccessful.
Step 3: Conversion and Testing
The codebase and content identified in the assessment process must be converted to run properly on Gutenberg. Custom codes and scripts are often needed to help with this process.
With the peace of mind of having your site fully backed up, you’re now ready to play with the possibilities. Set up a staging site where you can test the migration process.
Step 4: Deployment
Once you’re satisfied with the look and feel of your staging site, back up your files before implementing the changes on the live site. You should monitor the site closely for any post-migration issues with performance or SEO metrics. Optimize your site as necessary to maintain or improve performance.
Following these steps will generally result in a successful migration. However, you should have a rollback plan at the point of deployment. This helps you revert to the classic editor if critical issues arise. Keep your backups handy if you need to restore your site quickly.
Step 5: Training
Provide training and resources for your personnel to familiarize themselves with Gutenberg. Offer support during the transition period to help users more readily adopt the change.
Need Help With Your Migration From Classic Editor to Gutenberg Blocks? Contact Ndevr
Are you just starting to brainstorm the notion of switching to Gutenberg? Perhaps you’ve needed to make the change for a while, but you’re unsure how to begin your assessment, or you simply need technical support from your staff during the migration process. Wherever you are with changing from classic editor to Gutenberg, Ndevr can help. We are a WordPress development agency providing custom solutions to help ease the difficulties users and developers face with migrations and to help them grow through their WordPress sites. We handle your technology so you can focus on your business.
Contact us to learn more about our services and how we can help you get the most out of migrating to Gutenberg.
