# Managing Languages in International Press Zone

Language setup for the first customer is intentionally narrow: choose target languages that the current verified product/backend contract exposes, persist those choices, and use them in the preview → publish workflow.

## Configure target languages

1. Open the International Press Zone language configuration surface.
2. Select one or more target languages that are currently available to the customer environment.
3. Save the configuration.
4. Leave the page and return to verify the selections persisted.
5. Use one of the persisted target languages for the acceptance translation flow.

Record the exact language names/codes shown by the verified environment. Do not replace that evidence with a fixed claim such as “50+ languages.”

## Translation behavior

First-customer acceptance is based on an operator-requested preview and publish flow. **Automatic or continuous translation is deferred and must not be presented as a launch promise.**

If a language choice or translation action requires Press.Zone backend capability, entitlement, tenancy, authentication, or availability, that dependency remains conditional. Record the actual state in the acceptance evidence rather than promising it locally.

## Scope boundaries

Language configuration does not imply support for every multilingual integration. In particular, first-customer scope does not require WPML migration/interoperability, imported Site Content, block templates/synced patterns, advanced teams/workflow, broad multisite, third-party builders, broad WooCommerce/multi-currency behavior, or unverified translation-memory/glossary functionality.

The complete scope authority is `../launch/FIRST-CUSTOMER-SCOPE.md`. Execute launch validation through `../launch/FIRST-CUSTOMER-ACCEPTANCE.md`.