--- title: 19 Methods to Avoid Gutenberg on Your WordPress Website date: "2018-11-14" author: "Birgit Pauli-Haack" url: "https://gutenbergtimes.com/10-methods-to-avoid-gutenberg-on-your-website/" categories: ["News", "Using Gutenberg"] --- - Updated November 14, 2018: Added link to plugin “Disable Gutenberg” (#18). Added link to CalmPress (#19)  Living in Florida, I am contemplating a recount of my own for this post. Who needs 20 methods to avoid something…. haha. — Birgit x💕 - Updated October 9th, 2018 – Added Mika Epstein’s Selective DeGutenberging (#17) - Updated August 31, 2018 – Added “Reading List: What the Fork (WTF) - Updated August 27th, 2018, added the option of leaving WordPress ecosystem and community altogether, highlighting four alternative CMSs. - Updated August 2nd, 2018 added a 12th method to the Gutenberg Call-out section. - Updated August 1, 2018 added an 11th method to the Gutenberg Nag section. --- Gutenberg, the new visual editor for WordPress will be merged into  Core as the default editor later this year, when [WordPress 5.0 will be released](https://gutenbergtimes.com/mullenweg-on-gutenberg-roll-out-plan/). In August  a “Try Gutenberg” call out was released with WordPress 4.9.8 with a button to to install the Gutenberg plugin for post and pages or install official Classic Editor. If you install the [Classic Editor](https://wordpress.org/plugins/classic-editor), you will be able to keep using the current editor beyond the merge of Gutenberg into Core. Beyond this global opt-out method,  developers, consultants and site admins can make more nuanced decisions on how Gutenberg is implemented on their sites. Here is a list. If you find one missing, feel free to post a link in the comments and we’ll update the post. *Caveat: Use at your own risk. We did not test the latest versions of mentioned plugins.* ## Built-in Methods and Plugins maintained by Core Contributors Gary Pendergast, summarized built-in Methods that will be available when Gutenberg is merged into Core. **Note: There is not a single method. It’s all depends on context.** The[ Classic Editor plugin](https://wordpress.org/plugins/classic-editor/) is the option for reverting to the classic editor** across an entire site**. It’s being advertised prominently in the upcoming WordPress 4.9.8 release as an option to install now, in preparation for WordPress 5.0. If you’re a **site builder** who wishes to opt your clients out of the block editor, installing the Classic Editor plugin (and[ contributing with bug reports or fixes](https://github.com/wordpress/classic-editor/)) is the best long term solution to ensure the classic editor will continue to be available. For **metaboxes**, it’s already possible to[ opt-out of the block editor](https://wordpress.org/gutenberg/handbook/extensibility/meta-box/), this API will be merged into Core. For **CPTs**, the `gutenberg_can_edit_post_type` filter will be renamed when it’s merged (probably to `block_editor_can_edit_post_type`, or something of that nature), but will also be available as a code-based option. ## Methods to avoid Gutenberg nag or modify it. ### Built into Core with with 4.9.8  **For site – owners**,  the easiest way is to just use the **“Dismiss”** link on the right side. Once you dismiss the prompt it won’t show up again. Wow, that was easy:-) *Via code in a plugin or in a file stored in /mu-plugins folder* ``` add_action( 'init', function() { remove_action( 'try_gutenberg_panel', 'wp_try_gutenberg_panel' ); }); ``` The is also a new filter  `try_gutenberg_learn_more_link`  “that allows hosts or site owners to change the link, to provide extra information about Gutenberg, specific to their service or site. ” (*[Quoted from the trac ticket](https://core.trac.wordpress.org/ticket/41316#comment:176)*) *More details on both can be [found on the Core Make blog](https://make.wordpress.org/core/2018/08/02/try-gutenberg-callout-in-wordpress-4-9-8/)* ![WP Buffs](https://i0.wp.com/wpbuffs.com/wp-content/uploads/2017/11/Care-Plan-Wide.jpg?w=652&ssl=1) *Affiliate link* ### Plugins to disable the notice There are a few plugins available that suppress the so called “Gutenberg Nag”. - Paul Biron, release lead for 4.9.8 created a plugin to hide the Gutenberg Nag for different user capabilities. At the moment, it’s only available on GitHub - David Decker made his available on GitHub. - Luciano Croce published the “Dismiss Gutenberg Nag” on the WordPress plugin Repository - Jeff Starr’s plugin “Disable Gutenberg” does a lot more (see below) and it also disables the Gutenberg admin notice. ## Additional Plugins available on the WordPress Plugin Repository Over the last four months, plugin developers also created various solutions to have a more granular control over Gutenberg editing experience. - Gutenberg Ramp – published by WordPress VIP team, allows you to enable Gutenberg on a post level basis for CTPs if they support the editor. - Jeff Starr’s plugin “Disable Gutenberg”  completely disables Gutenberg editor, and gives us the choice to do it by post type or user role. - Sara Gooding on WPTavern reviewed the Classic Editor Addon Plugin, that also implemented a feature to disable the 4.9.8 nag, but also needs the Classic Editor plugin installed. - Gutenberg Manager by the unCommons Team, also allows you to disable Gutenberg for selected Custom post types. - With Lee Rickler’s plugin GutenBeGone – you can disable individual Blocks that come with Gutenberg - LittleBizzy published yet another plugin: Disable Gutenberg ## WordPress Fork Proposals ### ClassicPress A recent start-up, intending a fork of WordPress 4.9.8, probably one of the last versions without Gutenberg. At the time of this writing (8/27/28), it’s not ready for anyone to jump on board. Stay in the loop via [the website.](https://classicpress.net)  [“Forking is a features”](https://pento.net/2018/08/26/forking-is-a-feature/) Gary Pendergast, a WordPress Contributor blogged in August. ### CalmPress *CalmPress* is the name of another WordPress 4.9 fork. “to get a more stable and **calm** experience to all of its users” writes Mark Kaplun, the initiator of CalmPress. It’s not intended as a “one-man hobby”, but it’s what it looks like at this moment. You can [follow along the progress via its blog](https://blog.calmpress.org/) ## Leave WordPress – Community and Ecosystem There are plenty of options to leave the WordPress eco sytem, depending on your needs and goals. [W3Tech covers approximately 300+  Content Management Systems.](https://w3techs.com/technologies/overview/content_management/all) There are the commercial walled-garden options: [Shopify](https://www.shopify.com/), [SquareSpace](https://www.squarespace.com/), [Wix](https://www.wix.com/) or the proprietary software [Adobe Experience Manager](https://www.adobe.com/marketing/experience-manager.html). Below, you find three examples of modern CMS to check out as developer.  ### Ghost 2.0 Founded by John O’Nolan, a former WordPress Core contributor, and Hannah Wolfe, Ghost’s 1st version was released in 2013. It’s a blogging platform entirely written in server-side JavaScript based on nodejs. The open-source software is available for self-hosters as well as a hosted solution, maintained by the Ghost Foundation. ## Drupal Drupal, is the other major PHP-based open-source content management system with a large community. Lately, it made headlines, for [efforts to integrated Gutenberg](https://wptavern.com/first-look-at-live-demo-of-the-gutenberg-content-editor-for-drupal-8) in its own code base. ### Craft CMS Craft is another PHP/MySQL based Content Management System, just released in it 3rd version. Back in April, the [Craft Plugin Store](https://craftcms.com/news/introducing-the-craft-plugin-store) was opened, integrated with GitHub and annual updates for residual income for the developers. *Photo by [Jamie Street](https://unsplash.com/photos/dQLgop4tnsc?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on *[Unsplash](https://unsplash.com/search/photos/road-construction?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)