Visual Editor

Edit translations directly on the rendered website.

The Visual Editor opens the real website as a top-level page and overlays translation-editing controls.

It intentionally does not use an iframe because many production sites send X-Frame-Options or Content Security Policy headers that prevent embedding.

Launch behavior

The editor opens the original known-working WordPress permalink and securely carries:

• selected content ID
• target language
• editor nonce

The target translation is overlaid in editor mode. This makes the Visual Editor independent of whether a translated /zu/... route is currently resolving correctly.

Outline statuses

Typical visual states are:

• blue — translated / approved
• amber — draft / needs review
• red — known untranslated
• red dotted — visible text discovered on the rendered page but not yet tracked

Rendered-DOM discovery

The editor audits visible text nodes rather than only a fixed set of p, heading and button tags. This helps discover:

• generic div / span text
• theme/plugin cards
• dynamic post grids
• shortcode output
• form placeholders and labels
• select option labels

Translate all missing

The Visual Editor can queue all visible missing content, including normal tracked segments, global strings and newly discovered rendered text.

Role in v0.20.0

For large websites, Visual Editor is a QA and exception tool. Run Translate Entire Site first and allow automatic rendered-site discovery to finish before opening pages one by one.

License-aware automatic discovery

Manual visual review/editing remains part of the local translation workflow. Automatic Visual Editor missing-text capture/translation is treated as a premium commercial operation in v0.20.0.