WORDPRESS BLOCK EDITOR
Translate Gutenberg blocks without breaking the page structure.
REEID understands WordPress block content and translates supported customer-facing text while preserving block hierarchy, attributes and layout.
BLOCK STRUCTURE
WordPress remains responsible for page layout.
REEID focuses on translatable content stored inside Gutenberg blocks while preserving reusable blocks, nested layouts and editor structure.
- ✓ Block hierarchy preserved
- ✓ Visitor-facing text translated
- ✓ Native WordPress workflow
100%
Native Gutenberg workflow
0
Custom block conversion required
∞
Supported block-based pages
PRACTICAL WORKFLOW
From one Gutenberg page to multiple language versions.
REEID processes supported block content while keeping the original WordPress editing structure available to site editors.
STEP 1
Build the source page
Create the original page with Gutenberg blocks, patterns, columns and supported reusable content.
STEP 2
Choose the language
Select the target language and the available REEID translation options for the page.
STEP 3
Translate supported blocks
REEID extracts supported visitor-facing text without translating structural block configuration.
STEP 4
Review and publish
Inspect the translated page in WordPress, refine the content and publish when it is ready.
SUPPORTED BLOCK CONTENT
Translate the words while preserving the block machinery.
REEID focuses on supported visitor-facing text. Block types, nesting, alignment, spacing and layout attributes remain part of the Gutenberg structure.
Headings
Translate supported heading text while preserving heading level, alignment and block position.
VISITOR-FACING CONTENT
Paragraphs
Process paragraph content without rebuilding the surrounding Gutenberg page structure.
VISITOR-FACING CONTENT
Buttons
Translate supported button labels while preserving links, alignment and visual settings.
SUPPORTED FIELD
Lists
Translate supported list items while retaining ordered, unordered and nested list structure.
STRUCTURE PRESERVED
CONTENT BOUNDARY
A Gutenberg block contains both visible content and structural configuration.
REEID translates supported text intended for the visitor while leaving layout attributes, responsive behavior and block relationships under WordPress control.
Custom and third-party blocks may introduce proprietary fields that require explicit compatibility testing.
DESIGNED TO SCALE
A repeatable translation workflow for a growing Gutenberg site.
The number of pages may grow, but the editorial model remains familiar: build with Gutenberg, translate supported content, review and publish.
CONTENT LIBRARY
1
source page
10
pages
100
pages
1,000
pages
More content. The same Gutenberg editing model.
COMPATIBILITY BOUNDARIES
Native blocks are predictable. Third-party blocks must be tested.
Gutenberg provides a standard block model, but plugins can introduce proprietary attributes, nested data and custom rendering logic.
Core blocks
Standard headings, paragraphs, lists, buttons and supported native blocks follow predictable WordPress structures.
Nested content
Columns, groups and nested blocks remain structural containers while supported text inside them can be translated.
Reusable content
Patterns and reusable blocks should be reviewed according to how the site stores and reuses their content.
Third-party blocks
Custom block fields and proprietary data structures require explicit compatibility testing.
COMMON QUESTIONS
Gutenberg and REEID Translate FAQ
Answers about supported blocks, structural preservation and multilingual Gutenberg workflows.
Can REEID Translate Gutenberg pages?
Yes. REEID processes supported visitor-facing block content while preserving the surrounding Gutenberg structure.
Does translation rebuild the block layout?
No. Block hierarchy, layout relationships and structural attributes remain under WordPress control.
Which Gutenberg blocks are supported?
Supported content includes common visitor-facing fields such as headings, paragraphs, buttons and lists. Exact coverage depends on the installed REEID edition and active configuration.
Are columns and groups translated?
Columns and groups are structural containers. Supported text inside their nested blocks can be translated while the container structure remains intact.
What happens to links and button URLs?
Supported button labels can be translated while link destinations and structural settings remain preserved unless a language-specific URL workflow explicitly changes them.
Are reusable blocks and patterns supported?
Compatibility depends on how the reusable content is stored and referenced. It should be tested within the active WordPress configuration.
Do third-party Gutenberg blocks work automatically?
No. Third-party blocks can introduce proprietary fields and rendering logic that require explicit compatibility testing.
Can translated Gutenberg pages be edited afterward?
Yes. Generated language versions remain editable so teams can review, refine and publish intentionally.
NATIVE WORDPRESS WORKFLOW
Translate Gutenberg content without replacing Gutenberg.
REEID works with supported WordPress block content while preserving the editor structure your team already uses.
Third-party and custom blocks may require dedicated compatibility testing.