CUSTOM FIELDS FOR GUTENBERG
Custom Fields for Gutenberg compatibility with REEID Translate
Custom Fields for Gutenberg compatibility with REEID Translate is being evaluated from available plugin evidence. Restores the “Custom Fields” meta box for the Gutenberg Block Editor. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Custom Fields for Gutenberg.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Custom Fields for Gutenberg is documented in the Other category with 6 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Custom Fields for Gutenberg compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Restores the “Custom Fields” meta box for the Gutenberg Block Editor.
- Provides plugin options configurable via a settings screen.
- Allows specifying which post types should display custom fields.
- Supports excluding custom fields based on protected/hidden status, empty values, and/or specific custom field names.
- Implements usage behavior for editing, adding, and deleting custom fields via the Gutenberg editor (mirroring the original “Custom Fields” meta box workflow).
- On uninstall, removes plugin settings from the WordPress database, while leaving existing custom fields intact.
CONTENT BOUNDARY
Custom Fields for Gutenberg capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Custom Fields for Gutenberg and REEID Translate FAQ.
What does Custom Fields for Gutenberg do according to the available plugin evidence?
Custom Fields for Gutenberg has 6 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Custom Fields for Gutenberg?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Custom Fields for Gutenberg?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Custom Fields for Gutenberg in a multilingual WordPress workflow.
REEID documents Custom Fields for Gutenberg functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.