Do I need separate templates for each language?
No. Templates keep base slugs like header. You create locale-specific template parts (header-en, footer-de, etc.) or map custom slugs in the admin table.
questions
No. Templates keep base slugs like header. You create locale-specific template parts (header-en, footer-de, etc.) or map custom slugs in the admin table.
Swapping runs on the front end (and is suspended during admin/REST). Editors still manage all parts in the Site Editor; admin tabs help map, clone, and audit coverage.
Version 0.2 adds pattern language scope and filters the block pattern inserter via REST so editors see patterns relevant to the active language.
It resolves base FSE template part slugs (header, footer, and custom parts) to language-specific versions on the front end, based on the active Polylang or WPML locale.
The resolver falls back to the base slug so the site keeps working. The Design System tab highlights missing variants so you can clone them in one click.
Polylang and WPML via built-in providers. The plugin auto-detects which one is active and reads the current language slug from that stack.
No questions found. Try another search.