Naked Cat Plugins

Marco Almeida | Webdados

<p>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.</p>
<p>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.</p>
<p>The plugin also supports setting the language at the page or post level, both on the blocks and 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.</p>
<p>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.</p>
<p>For more context: this plugin helps you to make your website compliant with the Web Content Accessibility Guidelines (WCAG) success criteria:</p>
<ul>
<li><strong>3.1.1 – Language of Page</strong>: The default human language of each web page can be programmatically determined. Use the page-level setting when an entire page or post is written in a language other than the website’s default.</li>
<li><strong>3.1.2 – Language of Parts</strong>: 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>
<p>The purpose of these success criteria is to ensure that user agents can correctly present content written in multiple languages.</p>
<p>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.</p>
<p><strong>As per Web Content Accessibility Guidelines:</strong></p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>Banner photo by <a href="https://unsplash.com/@hannahwrightdesigner?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash" rel="nofollow ugc">Hannah Wright</a>.</p>
<h3>Supported block types</h3>
<ul>
<li><strong>Group</strong> (<code>core/group</code>): Group contents together and set a language for them</li>
<li><strong>Columns</strong> (<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><strong>Cover</strong> (<code>core/cover</code>): Set the language to all the contents inside a cover block</li>
<li><strong>Navigation</strong> (<code>core/navigation</code>): Create full navigation menus in different languages</li>
<li><strong>Submenu</strong> (<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><strong>Page List</strong> (<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><strong>Content</strong> (<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 for an entire 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</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, or to the whole page/post.

Ayuda WordPress

Fernando Tellado

<p>The most comprehensive solution to completely remove Gutenberg Block Editor and all its related features from your WordPress installation. This plugin doesn’t just disable the block editor – it eliminates every trace of block-related functionality for maximum performance and compatibility.</p>
<p><strong>What this plugin removes:</strong></p>
<h4>Core Gutenberg Features</h4>
<ul>
<li>Gutenberg Block Editor (completely disabled)</li>
<li>Full Site Editing (FSE) Global Styles and inline CSS</li>
<li>Block-based Widget Editor (reverts to Classic Widgets)</li>
<li>Block Patterns and Pattern Directory</li>
<li>Theme.json support and processing</li>
<li>Block Directory integration</li>
<li>Site Editor functionality</li>
</ul>
<h4>Performance Optimizations</h4>
<ul>
<li>Removes all block-related CSS and JavaScript files</li>
<li>Eliminates Global Styles inline CSS on every page</li>
<li>Removes unused block library assets</li>
<li>Disables block editor admin assets</li>
<li>Removes duotone and layout support filters</li>
</ul>
<h4>WooCommerce Integration</h4>
<ul>
<li>Disables WooCommerce block-based checkout and cart</li>
<li>Removes WooCommerce block editor for products</li>
<li>Eliminates WooCommerce block assets and styles</li>
<li>Forces classic WooCommerce experience</li>
</ul>
<h4>Admin Experience</h4>
<ul>
<li>Removes “Try Gutenberg” dashboard widgets</li>
<li>Disables Gutenberg-related admin menus</li>
<li>Removes Patterns submenu from Appearance menu (WP 6.5+)</li>
<li>Blocks access to Site Editor pages</li>
<li>Shows activation success notice</li>
<li>Adds support link to plugin actions</li>
</ul>
<p><strong>Zero Configuration Required</strong> – Simply activate the plugin and everything is automatically disabled. No settings page needed because it just works!</p>
<p>This plugin is perfect for:<br />
– Users who prefer the Classic Editor<br />
– Sites requiring maximum compatibility with legacy themes and plugins<br />
– Performance-focused installations<br />
– Users who want to eliminate block-related overhead completely</p>
<h3>Support</h3>
<h4>Need help or have suggestions?</h4>
<ul>
<li><a href="https://servicios.ayudawp.com/" rel="nofollow ugc">Official website</a></li>
<li><a href="https://wordpress.org/support/plugin/no-gutenberg/" rel="ugc">WordPress support forum</a></li>
<li><a href="https://www.youtube.com/AyudaWordPressES" rel="nofollow ugc">YouTube channel</a></li>
<li><a href="https://ayudawp.com/" rel="nofollow ugc">Documentation and tutorials</a></li>
</ul>
<p><strong>Love the plugin?</strong> Please leave us a 5-star review and help spread the word!</p>
<h3>About AyudaWP</h3>
<p>We are specialists in WordPress security, SEO, and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.</p>


No Gutenberg – Disable Blocks Editor and Global Styles – Back to Classic Editor

Simple, light weight and cool. No, I don't dislike Gutenberg that's cool too. 

Nice Plugin

Complete elimination of Gutenberg Block Editor, FSE Global Styles, Block Widgets, Patterns, and WooCommerce blocks. Back to Classic Editor.

Language Attribute for Container Blocks and Pages/Posts vs No Gutenberg – Disable Blocks Editor and Global Styles – Back to Classic Editor