
GLOBALDEV FRONT-END CONTENT EDITOR
GlobalDev Front-End Content Editor compatibility with REEID Translate
GlobalDev Front-End Content Editor compatibility with REEID Translate is being reviewed using official plugin documentation. Indexes and enables front-end content editing for Gutenberg blocks, Classic content, static Elementor widget fields, and WPBakery shortcode elements. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What GlobalDev Front-End Content Editor does
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
GlobalDev Front-End Content Editor is documented in the Page Builder category with 5 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How GlobalDev Front-End Content Editor compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Indexes and enables front-end content editing for Gutenberg blocks, Classic content, static Elementor widget fields, and WPBakery shortcode elements.
- Scans posts and pages to build a stable map of editable content, including Gutenberg block paths, Classic HTML fragment positions, Elementor widget IDs with stored static content fields, and WPBakery shortcode paths with content-bearing parameters.
- Rebuilds the editable content map after post or Elementor saves, during an installation scan, and on demand when an indexed page is opened.
- Discovers WPBakery elements from the live WPBMap registry, including third-party elements registered through vc_map().
- Provides a settings area under “Front-End Editor > Settings” and includes a “Rebuild all content maps” option.
TRANSLATION BOUNDARY
GlobalDev Front-End Content Editor capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- No visitor-facing translation surface was established for this integration.
FREQUENTLY ASKED QUESTIONS
GlobalDev Front-End Content Editor and REEID Translate FAQ.
What does GlobalDev Front-End Content Editor do?
GlobalDev Front-End Content Editor has 5 documented features listed in its official documentation. See the Plugin Information section for details.
Does GlobalDev Front-End Content Editor have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from GlobalDev Front-End Content Editor?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate GlobalDev Front-End Content Editor in a multilingual WordPress workflow.
REEID documents GlobalDev Front-End Content Editor functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.