PAGE COMPOSER
Page Composer — Basic translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Page Composer — Basic 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
- Replaces the default editor on Posts and Pages with the Page Composer visual editor.
- Composes Posts and Pages from components (including Text and Image, plus WooCommerce blocks) and renders them via the bundled PCEditor library.
- Stores composed content as JSON in post meta and compiles it into `wp_posts.post_content` as an HTML snapshot on every save.
- Provides native revisions that cover both the snapshot and the JSON composition (WP 6.4+ revisioned meta).
- Includes a Google map component that embeds a map via an iframe using the Google Maps Embed API when a key is configured, or a keyless classic embed when it is not.
- Detects conflicting page builders (e.g., Elementor, WPBakery, Divi, Beaver Builder) and disables the editor with a notice while any is active.
Distinctive features
Replaces the default editor on Posts and Pages with the Page Composer visual editor. Composes Posts and Pages from components (including Text and Image, plus WooCommerce blocks) and renders them via the bundled PCEditor library. Stores composed content as JSON in post meta and compiles it into `wp_posts.post_content` as an HTML snapshot on every save. Provides native revisions that cover both the snapshot and the JSON composition (WP 6.4+ revisioned meta). Includes a Google map component that embeds a map via an iframe using the Google Maps Embed API when a key is configured, or a keyless classic embed when it is not. Detects conflicting page builders (e.g., Elementor, WPBakery, Divi, Beaver Builder) and disables the editor with a notice while any is active.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Page Composer — Basic 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
- No visitor-facing translation surface was established for this integration.
COMMON QUESTIONS
Page Composer — Basic and REEID Translate FAQ.
Does the current evidence establish translation scope for Page Composer — Basic?
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.