WORDPRESS THEME COMPATIBILITY
Translate WordPress content without replacing the theme that presents it.
REEID Translate Pro works with supported WordPress and builder content while the active theme continues controlling templates, styling, headers, footers and responsive presentation.
SEPARATE RESPONSIBILITIES
The theme still owns presentation.
REEID translates supported visitor-facing content and connects language versions. It does not duplicate the active theme or take ownership of its templates.
- Theme templates and styling remain active.
- Supported content remains editable in WordPress.
- Theme-specific modules remain a separate QA responsibility.
Theme
Controls visual presentation and templates.
REEID
Handles supported multilingual content workflows.
No rebuild
Theme files and templates stay outside translation.
QA
Custom headers, menus and extensions still need testing.
THEME COVERAGE
Theme compatibility depends on what the theme controls.
Some themes have dedicated REEID handling. Others rely mainly on standard WordPress content and navigation behaviour and should be verified against the actual site configuration.
| Theme | REEID handling | What to verify |
|---|---|---|
| Astra | Dedicated compatibility logic for Astra menu behaviour and WooCommerce stylesheet handling. Astra is also used on the current REEID site. | Active-site verified; still review the final multilingual frontend. |
| Blocksy | REEID includes a Blocksy-specific translated-page loader. | Theme-specific navigation and visual behaviour should be checked on the target site. |
| Hello Elementor | Dedicated switcher and navigation handling is available for the standard Hello Elementor header workflow. | Review the dedicated Hello Elementor guide. |
| GeneratePress | Uses standard WordPress content and menu systems; no dedicated REEID theme adapter is currently required. | Verify custom headers and site-specific navigation behaviour. |
| Kadence | Generally relies on WordPress posts, pages and menus. | Test custom header elements, premium modules and extensions used by the site. |
| Standard block themes | REEID includes specific handling for Twenty Twenty-Five and follows standard WordPress content and block-rendering conventions. | Verify any custom templates, navigation blocks and theme-specific modifications. |
COMPATIBILITY MODEL
Theme compatibility and content compatibility are different questions.
The theme decides how a page is presented. The source that stores the content determines which translation workflow REEID needs to use.
01 / BUILD
Build the website normally.
Create templates, headers, menus, styling and responsive behaviour using the active theme and its normal WordPress workflow.
02 / TRANSLATE
Translate the supported content source.
REEID translates supported visitor-facing content stored in WordPress, Gutenberg, Elementor, SiteOrigin or WooCommerce according to the relevant integration.
03 / RENDER
Keep the same active theme.
The translated language version continues rendering through the existing theme rather than through a duplicated multilingual theme layer.
04 / VERIFY
Review the real multilingual frontend.
Check menus, switchers, custom headers, RTL behaviour and responsive layouts before publishing.
CONTENT BOUNDARY
A theme can display content it does not actually own.
Visitor-facing text may come from native WordPress content, a builder, WooCommerce, custom fields or a theme options panel. The storage source determines the correct translation path.
This is why a theme working correctly does not automatically guarantee compatibility with every builder, widget or custom data source displayed through that theme.
THE PRACTICAL RULE
Presentation source ≠ content source.
Standard post content, Gutenberg blocks, Elementor data, SiteOrigin widgets and WooCommerce products use different storage models even when the same theme renders all of them.
Bricks is not currently included because REEID does not yet support the Bricks builder content model.
PRACTICAL CHECKS
Review the places where themes add their own behaviour.
Most theme issues appear at the edges of the normal content workflow rather than inside ordinary page text.
01 / HEADERS & MENUS
Check navigation in every active language.
Confirm translated links, dropdown hierarchy, mobile navigation and any theme-specific menu icons or header elements.
02 / LANGUAGE SWITCHER
Verify placement and interaction.
Check dropdown visibility, stacking order, sticky-header behaviour and interaction on both desktop and mobile.
03 / RTL
Review direction-sensitive presentation.
Arabic, Hebrew and other RTL languages may expose spacing, alignment, icon-direction or navigation issues in the active theme.
04 / THEME EXTENSIONS
Treat extra data sources separately.
Custom fields, header builders, popups and premium theme modules may introduce content that needs its own compatibility path.
COMMON QUESTIONS
What theme compatibility actually means.
The active theme keeps rendering the website. REEID works with supported content sources inside that presentation layer.
Theme support therefore does not automatically mean that every builder, widget, header module or custom data source used by the theme is translatable.
Does REEID replace my WordPress theme?
No. The active theme continues rendering both the source and translated language versions. REEID does not create a second theme or duplicate its templates.
Does changing the theme remove existing translations?
No. Translations remain associated with their WordPress posts or supported builder data. A new theme can, however, introduce different headers, menus, templates or visual behaviour that should be reviewed.
Which themes have dedicated REEID handling?
REEID currently includes theme-specific handling for Astra, Blocksy, Hello Elementor and Twenty Twenty-Five.
Can GeneratePress and Kadence work without dedicated adapters?
Yes, much of their content and navigation relies on standard WordPress systems. Custom headers, premium modules and site-specific extensions should still be tested separately.
Does theme compatibility guarantee builder compatibility?
No. A theme presents the page, while Gutenberg, Elementor, SiteOrigin and other builders use their own content-storage models. Each supported content source needs the appropriate translation workflow.
Is Bricks currently supported?
No. Bricks builder support is deferred until REEID has a dedicated and tested content adapter.
What should I test before launch?
Review desktop and mobile navigation, dropdowns, sticky headers, language-switcher placement, RTL presentation and any theme-specific modules used by the production site.
RELATED GUIDES
Continue through the compatibility stack.
Theme compatibility is only one layer. Builder storage and multilingual architecture matter too.
BLOCK EDITING
Gutenberg
Translate supported WordPress blocks while preserving their hierarchy and attributes.
PAGE BUILDING
Hello Elementor
Review dedicated compatibility for Elementor content and the Hello theme workflow.
SYSTEM DESIGN
Architecture
Understand how source content, themes, builders and language versions fit together.
KEEP YOUR WORDPRESS THEME
Add multilingual content without rebuilding the website design.
REEID Translate Pro works alongside the active theme and keeps supported language versions editable inside WordPress.
BEFORE LAUNCH
Translate the content. Then verify the presentation.
- Check custom theme modules.
- Review desktop and mobile navigation.
- Verify language-switcher behaviour.
Theme compatibility should always be confirmed against the actual production configuration.