DISABLE GUTENBERG
Disable Gutenberg translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Disable Gutenberg does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Disables the Gutenberg Block Editor and replaces it with the Classic Editor and original Edit Post screen.
- Can disable Gutenberg sitewide or selectively by post type, user role, theme template, and post/page IDs.
- Can restore Classic Widgets and disable the Gutenberg admin notice.
- Can hide the plugin menu item and the Gutenberg plugin menu item.
- Can add Classic Editor edit links and an Add New (Classic) menu entry.
- Can enable or disable the frontend Gutenberg stylesheet.
- Can whitelist specific posts so they still open in the Block Editor.
- Can reset the plugin to its default options.
Distinctive features
Provides selective Gutenberg disabling with multiple targeting options, plus Classic Editor restoration and related admin conveniences such as Classic Widgets restoration, menu-item hiding, Classic edit links, and a Classic Add New entry.
Dynamic content
The supplied evidence shows runtime control over whether Gutenberg is disabled sitewide or for selected posts, post types, user roles, theme templates, and post/page IDs. It also shows a whitelist for specific posts that should still open in the Block Editor. No broader dynamic content behavior is established.
SEO and metadata
The supplied evidence does not establish SEO metadata handling, generation, or modification.
URLs and navigation
The supplied evidence does not establish URL routing, permalink handling, redirects, or navigation behavior beyond adding Classic Editor edit links and an Add New (Classic) menu entry.
Forms and commerce
The supplied evidence does not establish forms or commerce behavior.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Disable Gutenberg does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This plugin changes WordPress editing behavior by disabling the Gutenberg Block Editor and restoring the Classic Editor and original Edit Post screen. Its effects can be applied sitewide or selectively by post type, user role, theme template, and post/page IDs. Specific behavior for content types or surfaces not listed in the supplied evidence is not established.
COMMON QUESTIONS
Disable Gutenberg and REEID Translate FAQ.
Does the current evidence establish translation scope for Disable Gutenberg?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.