Marco Almeida | Webdados

Naked Cat Plugins

This plugin aims to ensure that any language change in a page’s content is indicated to assistive technologies at the container block level, helping a website comply with WCAG guidelines.
This feature is available on the core block editor only at a text formatting level after code from <a href="https://wordpress.org/plugins/lang-attribute/" rel="ugc">Jb Audras plugin “Lang Attribute for the Block Editor”</a> was merged into core. The objective of this plugin is to provide the same functionality at a container block level (Group – including all its variants, Columns, Cover, and other specific block types) so that the language applies to all child elements, no matter the kind of content inside.
The plugin also supports setting the language at the page or post level, both on the blocks and the classic editor. When an entire page is written in a different language than the website’s default, you can override the HTML <code>lang</code> and <code>dir</code> attributes for that specific page directly from the Document Settings sidebar, without needing to wrap everything in a container block. 
For even broader coverage, the plugin supports setting the language at the template level in the Site Editor (Appearance → Editor → Templates). A language set on a template is automatically applied to all pages and posts using that template, unless a specific language is set at the individual post or page level — in which case the post-level setting takes precedence. 
This plugin is heavily inspired by the Jb Audras plugin (including this readme file). The development started at WordCamp Europe 2025 Contributor Day, by Marco Almeida from <a href="https://profiles.wordpress.org/nakedcatplugins/" rel="nofollow ugc">Naked Cat Plugins</a> / <a href="https://profiles.wordpress.org/webdados/" rel="nofollow ugc">Webdados</a>, and the help from <a href="https://profiles.wordpress.org/welcher/" rel="nofollow ugc">Ryan Welcher</a> on the code side and <a href="https://profiles.wordpress.org/alh0319/" rel="nofollow ugc">Amber Hinds</a> on the accessibility compliance side.
For more context: this plugin helps you to make your website compliant with the Web Content Accessibility Guidelines (WCAG) success criteria:
<ul>
<li>3.1.1 – Language of Page: The default human language of each web page can be programmatically determined. Use the template-level setting when all posts or pages sharing a template are in the same language, or the page-level setting when an entire page or post is written in a language other than the website or template default.</li>
<li>3.1.2 – Language of Parts: The human language of each passage or phrase in the content can be programmatically determined. Use the block-level setting when only specific sections within a page are in a different language.</li>
</ul>
The purpose of these success criteria is to ensure that user agents can correctly present content written in multiple languages.
Keep in mind that you should set the <code>lang</code> and <code>dir</code> attributes only on a container block or page if the content is written in a language different from the one set globally on your website.
As per Web Content Accessibility Guidelines:
This enables user agents and assistive technologies to present content according to the presentation and pronunciation rules of that language. This applies to graphical browsers, screen readers, braille displays, and other voice browsers.
Both assistive technologies and conventional user agents can render text more accurately if the language of each passage of text is identified. Screen readers can use the language’s pronunciation rules. Visual browsers can display characters and scripts appropriately.
This is especially important when switching between languages that read from left to right and languages that read from right to left, or when text is rendered in a language that uses a different alphabet. Users with disabilities who know all the languages used in the Web page will be better able to understand the content when each passage is rendered appropriately.
That’s not just good for accessibility. It’s also great for SEO. Search engines like Google can better understand your content when languages are clearly defined. That means improved indexing and potentially better rankings.
Banner photo by <a href="https://unsplash.com/@hannahwrightdesigner?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash" rel="nofollow ugc">Hannah Wright</a>.
<h3>Supported block types</h3>
<ul>
<li>Group (<code>core/group</code>): Group contents together and set a language for them</li>
<li>Columns (<code>core/columns</code> and <code>core/column</code>): Organize content into a set of columns and set a language for all the columns or a specific column</li>
<li>Cover (<code>core/cover</code>): Set the language to all the contents inside a cover block</li>
<li>Navigation (<code>core/navigation</code>): Create full navigation menus in different languages</li>
<li>Submenu (<code>core/navigation-submenu</code>): Set a different language on a sub-section of your menu (for example, if you have the default language pages on the first level and a sub-menu with pages in another language)</li>
<li>Page List (<code>core/page-list</code>): List all the pages on your website that are written in a different language and created as a child of the main page of that language</li>
<li>Content (<code>core/post-content</code>): Set the post content on a custom template to a different language</li>
</ul>
<h3>Features</h3>
<ul>
<li>Set the language and text direction at the template level in the Site Editor: a “Template Language” panel lets you define the default language for all pages and posts using that template, which is automatically applied unless overridden at the individual post or page level</li>
<li>Set the language and text direction for an individual page or post, both on the blocks and classic editor: a “Page Language” panel in the Document Settings sidebar overrides the HTML <code>lang</code> and <code>dir</code> attributes for that specific page, taking precedence over any template-level setting</li>
<li>Add <code>lang</code> and <code>dir</code> attributes to Group, Columns, Cover, and other specific WordPress Blocks, mentioned above</li>
<li>Show visual outline around blocks that have a language attribute set – For easy identification of blocks you have already set to a different language during your editing process, only for Administrators and Editors, and if enabled in Settings – Writing</li>
</ul>

Language Attribute for Container Blocks and Pages/Posts

Add lang and dir attributes to Group, Columns, Cover, and other specific WordPress Blocks, Templates, or to specific Posts/pages.

Jeff Starr

This plugin disables the new Gutenberg Editor (aka Block Editor) and replaces it with the Classic Editor. You can disable Gutenberg completely, or selectively disable for posts, pages, roles, post types, and theme templates. Plus you can hide the Gutenberg nag, menu item, and more!
<blockquote>
♠ The all-in-one, COMPLETE solution for handling Gutenberg 
 ♠ Hide ALL traces of Gutenberg and replace with Classic Editor 
 ♠ Restores original Edit Post screen (TinyMCE, meta boxes, etc.)
</blockquote>
The Disable Gutenberg plugin restores the classic (original) WordPress editor and the “Edit Post” screen. So you can continue using plugins and theme functions that extend the Classic Editor. Supports awesome features like Meta Boxes, Quicktags, Custom Fields, and everything else the Classic Editor can do.
Easy to Use
Just activate and done! The default plugin settings are configured to hide all traces of the Gutenberg Block Editor, and fully restore the original Classic Editor. Further options for customizing when/where Gutenberg is enabled are available in the plugin settings.
<blockquote>
♠ Disable Block Widgets and restore Classic Widgets 🙂
</blockquote>
Options
<ul>
<li>Disable Gutenberg completely (all post types)</li>
<li>Disable Gutenberg for any post type</li>
<li>Disable Gutenberg for any user role</li>
<li>Disable Gutenberg for any theme template</li>
<li>Disable Gutenberg for any post/page IDs</li>
<li>Disable Gutenberg admin notice (nag)</li>
<li>Option to restore Classic Widgets</li>
<li>Option to hide the plugin menu item</li>
<li>Option to hide the Gutenberg plugin menu item (settings link)</li>
<li>Adds “Classic Editor” link to each post on the Posts screen</li>
<li>Adds item to the WP sidebar menu: “Add New (Classic)”</li>
<li>Option to enable Custom Fields Meta Box for ACF</li>
<li>Choose which editor to use for each post</li>
<li>Whitelist any post title, slug, or ID</li>
<li>Option to enable/disable frontend Gutenberg stylesheet</li>
</ul>
<blockquote>
♠ Works same as Classic Editor plugin, but can do a LOT more! 
 ♠ Lightweight and super fast, built with WP APIs 🙂
</blockquote>
Fully configurable, enable or disable Gutenberg and restore the Classic Editor wherever is necessary.
Automatically replaces Gutenberg with the Classic Editor.
Features
<ul>
<li>Super simple</li>
<li>Clean, secure code</li>
<li>Built with the WordPress API</li>
<li>Lightweight, fast and flexible</li>
<li>Regularly updated and “future proof”</li>
<li>Works great with other WordPress plugins</li>
<li>Plugin options configurable via settings screen</li>
<li>Focused on flexibility, performance, and security</li>
<li>One-click restore plugin default options</li>
<li>Translation ready</li>
</ul>
<blockquote>
♠ Works great with Google AMP and the WordPress <a href="https://wordpress.org/plugins/amp/" rel="ugc">AMP plugin</a>
</blockquote>
Disable Gutenberg is developed and maintained by <a href="https://x.com/perishable" rel="nofollow ugc">Jeff Starr</a>, 15-year <a href="https://plugin-planet.com/" rel="nofollow ugc">WordPress developer</a> and <a href="https://books.perishablepress.com/" rel="nofollow ugc">book author</a>.
Super light & fast plugin, super easy on server resources!
Why?
Gutenberg is a useful editor but sometimes you want to disable it for specific posts, pages, user roles, post types, and/or theme templates. This plugin enables you to disable Gutenberg and replace it with the Classic Editor wherever you want. For example, lots of WordPress users already enjoy robust page-building functionality via one of the many great plugins like Composer or Elementor. So many options, no need to feel “locked in” to using Gutenberg!
If you like Disable Gutenberg, please give it a <a href="https://wordpress.org/support/plugin/disable-gutenberg/reviews/?rate=5#new-post" rel="ugc">5-star rating</a>, thank you!
Privacy
This plugin does not collect or store any user data. It does not set any cookies, and it does not connect to any third-party locations. Thus, this plugin does not affect user privacy in any way.
Support development
I develop and maintain this free plugin with love for the WordPress community. To show support, you can <a href="https://monzillamedia.com/donate.html" rel="nofollow ugc">make a donation</a> or purchase one of my books:
<ul>
<li><a href="https://wp-tao.com/" rel="nofollow ugc">The Tao of WordPress</a></li>
<li><a href="https://digwp.com/" rel="nofollow ugc">Digging into WordPress</a></li>
<li><a href="https://htaccessbook.com/" rel="nofollow ugc">.htaccess made easy</a></li>
<li><a href="https://wp-tao.com/wordpress-themes-book/" rel="nofollow ugc">WordPress Themes In Depth</a></li>
<li><a href="https://books.perishablepress.com/downloads/wizards-collection-sql-recipes-wordpress/" rel="nofollow ugc">Wizard’s SQL Recipes for WordPress</a></li>
</ul>
And/or purchase one of my premium WordPress plugins:
<ul>
<li><a href="https://plugin-planet.com/bbq-pro/" rel="nofollow ugc">BBQ Pro</a> – Blazing fast WordPress firewall</li>
<li><a href="https://plugin-planet.com/blackhole-pro/" rel="nofollow ugc">Blackhole Pro</a> – Automatically block bad bots</li>
<li><a href="https://plugin-planet.com/banhammer-pro/" rel="nofollow ugc">Banhammer Pro</a> – Monitor traffic and ban the bad guys</li>
<li><a href="https://plugin-planet.com/ga-google-analytics-pro/" rel="nofollow ugc">GA Google Analytics Pro</a> – Connect WordPress to Google Analytics</li>
<li><a href="https://plugin-planet.com/head-meta-pro/" rel="nofollow ugc">Head Meta Pro</a> – Ultimate Meta Tags for WordPress</li>
<li><a href="https://plugin-planet.com/rest-pro-tools/" rel="nofollow ugc">REST Pro Tools</a> – Awesome tools for managing the WP REST API</li>
<li><a href="https://plugin-planet.com/simple-ajax-chat-pro/" rel="nofollow ugc">Simple Ajax Chat Pro</a> – Unlimited chat rooms</li>
<li><a href="https://plugin-planet.com/usp-pro/" rel="nofollow ugc">USP Pro</a> – Unlimited front-end forms</li>
</ul>
Links, tweets and likes also appreciated. Thanks! 🙂

Disable Gutenberg

El mejor plugin fuera de webeo, que wea mas mala es gutemberg

Gracias por existir

Excellent plugin

Awsome


Thank you! I like using the plugin on my personal site.


Thanks


Very useful--restores Wordpress to the way I need it--clean and, easy-to-edit.


Very useful--restores Wordpress to the way I need it


I can't really imagine Wordpress without this plugin. The nonsense called Gutenberg reliably eliminates and nothing else is needed.


The most important plugin the wordpress world needs


Sometimes the block editor is fine to use, but glad this plugin was made. 



Cheers.


Annoying that this is still required in 2025


Whether you love or hate either editor, being able to switch between both feels like a major unlock to your workflow. Plus, you know anything by Jeff Starr is going to be good!


A must-have for full WP functionality

Disable Gutenberg Block Editor and restore the Classic Editor and original Edit Post screen (TinyMCE, meta boxes, etc.).

Language Attribute for Container Blocks and Pages/Posts vs Disable Gutenberg