NO GUTENBERG?
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor does, but does not yet establish specific visitor-facing content values that REEID should translate.
Visit No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor ↗
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 block editor and restores the Classic Editor across the site by default.
- Can narrow block-editor disabling by post type, user role, page template, or individual entry.
- Supports per-entry editor switching between Classic and Blocks for selected post types.
- Removes block-related site features such as Global Styles, block widgets, block patterns, theme.json processing, and the Site Editor.
- Removes block CSS and JavaScript assets from the frontend and related admin contexts when the Classic Editor is used.
- Includes WooCommerce-specific behavior for the block-based product editor and WooCommerce block assets.
- Can be configured from wp-config.php, including locking or hiding the settings screen and applying settings across multisite networks.
Distinctive features
Site-wide Classic Editor restoration with granular control by post type, role, template, or individual entry. Includes block-feature removal beyond the editor itself, plus WooCommerce-specific handling and wp-config.php-based configuration options.
Dynamic content
The evidence shows editor availability can be adjusted by post type, user role, page template, or individual entry, and settings can be applied across multisite networks. No broader runtime content behavior is established.
SEO and metadata
The evidence shows removal of theme.json processing and block-related site features such as Global Styles. No broader SEO or metadata behavior is established.
URLs and navigation
No URL or navigation behavior is established in the supplied evidence.
Forms and commerce
WooCommerce-specific behavior is documented for the block-based product editor and WooCommerce block assets. No broader forms behavior is established.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor 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 editor availability and block-related site features, but the available evidence does not establish broader compatibility beyond those documented behaviors. Per-entry editor switching is described only for selected post types. WooCommerce-specific behavior is documented for the block-based product editor and WooCommerce block assets. Evidence for translation-surface behavior is not established.
COMMON QUESTIONS
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor and REEID Translate FAQ.
Does the current evidence establish translation scope for No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor?
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.