
GREENSHIFT
Translate Greenshift pages without rebuilding the layout.
REEID Translate Pro processes supported Greenshift content while preserving the original builder structure.
AWAITING VERIFICATION
Keep Greenshift responsible for the page layout.
REEID manages supported multilingual content and language relationships while Greenshift remains responsible for builder structure, presentation and configuration.
This integration has not yet been manually verified by REEID.
Supported visitor-facing fields are processed without replacing Greenshift builder structure.
Generated language versions remain available for normal WordPress review and refinement.
PRACTICAL WORKFLOW
Translation workflow
01 · Build the source page
Create the original page with Greenshift structure and supported content fields.
02 · Choose a target language
Select the language and translation settings through the REEID workflow.
03 · Generate the language version
REEID processes supported visitor-facing fields while preserving the original builder structure.
04 · Review and publish
Verify content, layout and frontend presentation before publication.
SUPPORTED CONTENT
Translation scope
heading text
Default heading typography for headings (H1–H5).
paragraph text
Default body text typography.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Gutenberg-based page building with blocks for layouts, containers, grids, sliders, tabs, popups, and other page elements.
- Animation-focused design tools including scroll animations, hover transitions, motion effects, and GSAP-based animation options.
- Dynamic content features for query loops, repeaters, custom fields, and other data-driven blocks.
- Responsive design controls with custom breakpoints, device-specific values, and mobile-oriented layouts.
- Template and conversion tools for reusable templates, HTML-to-blocks conversion, Figma conversion, and webpage-to-WordPress conversion.
Distinctive features
Strong focus on animated page building, with GSAP-based motion options, scroll and hover effects, responsive breakpoints, and tools for reusable templates and content conversion.
Dynamic content
Supports dynamic placeholders and data-driven blocks, including query loops, repeaters, and custom fields.
SEO and metadata
SEO or metadata behavior is not established beyond the supported content surfaces listed here.
URLs and navigation
URL or navigation behavior is not established beyond the supported content surfaces listed here.
Forms and commerce
Commerce-related support is limited to core button block styles and WooCommerce button blocks; broader forms or checkout behavior is not established.
CONTENT BOUNDARY
Greenshift structure and translatable content remain separate.
Builder structure and configuration remain controlled by Greenshift while REEID targets supported visitor-facing fields.
Third-party widgets, dynamic output and additional builder extensions may require separate compatibility testing.
LIMITATIONS & QA
Verification notes
- Typography settings cover heading and body text defaults only. They do not describe broader page content, layout behavior, or other block types.
COMMON QUESTIONS
Greenshift – animation and page builder blocks and REEID Translate FAQ.
Does REEID Translate support Greenshift?
Yes. REEID Translate Pro includes tested compatibility for supported visitor-facing content created with Greenshift.
Does REEID rebuild the Greenshift layout?
No. Greenshift remains responsible for layout and builder configuration while REEID translates supported content.
Are third-party Greenshift widgets automatically supported?
Not necessarily. Third-party widgets and extensions can use separate storage paths and should be reviewed independently.
RELATED GUIDES
Continue through the compatibility library.
WORDPRESS PAGE BUILDERS
Translate Greenshift content without rebuilding the page.
REEID Translate Pro adds multilingual content workflows while your page builder remains responsible for structure and presentation.
Greenshift remains responsible for layout, widgets and builder configuration.