Extended Support for WordPress Classic Editor Until 2022

Embrace or Evolve? Navigating the Extended Support for WordPress Classic Editor

The WordPress Classic Editor has been a staple of WordPress sites for over a decade, providing a simple and familiar editing experience. However, with the launch of the new block-based Gutenberg editor in 2018, the days of the Classic Editor seemed numbered. While its deprecation was announced for 2021, WordPress has now extended official support for the Classic Editor until 2022.

This leaves many site owners at a crossroads, debating whether to continue using the trusted Classic Editor or make the switch to Gutenberg. In this article, we’ll explore what the extended support means, who should consider sticking with the Classic Editor, the benefits of transitioning to Gutenberg, and how to prepare your site for the future, whichever path you choose.

What Does the Extended Support Mean?

The extended support provides ongoing security updates and bug fixes for the Classic Editor until January 2022. This ensures sites using the editor can continue running smoothly and safely in the short-term.

However, the Classic Editor is still slated for eventual removal from WordPress core. After 2022, it will enter an unsupported maintenance phase, with the community providing unofficial support and compatibility updates. Sites using outdated versions risk potential issues.

For developers, extended support means building and maintaining Classic Editor compatibility, at least through 2022. Themes, plugins, and custom code will need adaptation to prevent conflicts between the editing interfaces.

Who Should Stick with the Classic Editor?

The familiarity and simplicity of the Classic Editor may appeal to users like:

  • Beginners still learning WordPress.
  • Small business owners who rarely edit content.
  • Bloggers with minimal formatting needs.

For these groups, the Classic Editor avoids an unnecessary learning curve. With plugins extending support, sites with simple content workflows can potentially use the Classic Editor indefinitely.

However, those relying heavily on plugins and advanced features should be cautious, as compatibility issues may arise. Testing backups before updating is advised.

Why Consider Migrating to Gutenberg?

For users needing more robust formatting options, Gutenberg brings many benefits:

  • Intuitive visual editing with drag-and-drop blocks.
  • Increased layout flexibility and design control.
  • Growing library of block-based themes and plugins.

The block approach may feel unfamiliar initially. However, with Gutenberg now core to WordPress, official support and community resources will continue expanding.

Taking time to learn Gutenberg’s user-friendly interface can unlock more creative freedom in the long run.

Case Studies: Successful Migrations to Gutenberg

example.com – A small business site transitioned to Gutenberg to gain access to blocks for visually formatting service pages and blog posts. The learning curve was manageable with official tutorials.

example.net – A university department website performed extensive pre-launch compatibility testing before deploying a Gutenberg update. Despite hundreds of posts, the migration was seamless.

Preparing for the Future: Essential Steps

When considering a change in editors, thorough preparation helps ensure a smooth transition:

  • Back up your site through exports or plugins like UpdraftPlus.
  • Review plugins and themes for Gutenberg compatibility using developer resources.
  • Explore Gutenberg beforehand using test sites, tutorials, and the block library.
  • Consider supplemental plugins like Classic Editor, Gutenberg Ramp, or Disable Gutenberg.

For developers, preparations may involve refactoring custom code and updating theme files and templates to leverage Gutenberg functionality.

Resources and Community Support

The WordPress community provides extensive learning resources and support forums:

Conclusion

The WordPress Classic Editor’s extended support allows time for site owners to plan editorial workflows and developers to address compatibility concerns. For those embracing Gutenberg, ample resources like WordPress Charity and Non-Profit Themes exist to smooth the transition. And for lovers of the Classic Editor, options remain to prolong its use while the community rallies around it. With a thoughtful approach, site owners can choose the editor that best serves their needs and makes the most of WordPress’ ongoing evolution.

Frequently Asked Questions

What are the key differences between the Classic Editor and Gutenberg?

The Classic Editor uses a simple WYSIWYG interface for writing content linearly, while Gutenberg is block-based, allowing you to build pages modularly using a drag-and-drop visual approach.

Can I use both editors on my WordPress site?

Yes, the Classic Editor plugin allows restoring it even after Gutenberg becomes the default editor. The two can then be enabled for different pages or posts.

What if my plugins or theme don’t work with Gutenberg?

Compatibility has improved significantly since Gutenberg’s launch. But if issues arise, supplemental plugins like Classic Editor can restore functionality while you address conflicts.

Will my content look different in Gutenberg?

Existing content will remain visually intact. Creating new content in Gutenberg allows greater design flexibility, though some adjustments may be needed to match old and new styles.

Can I still customize my site if using the Classic Editor?

Yes, you can continue using themes and customization plugins for features like menus, layouts, colors, fonts, etc. The editor is mainly for content creation.”

Leave a Comment

Your email address will not be published. Required fields are marked *