# Getting Started with International Press Zone

This is the scoped first-customer workflow. It does not expand the supported surface defined in `../launch/FIRST-CUSTOMER-SCOPE.md`.

## 1. Complete installation and connection

Install and activate the audited International Press Zone artifact, then connect it to the assigned Press.Zone backend/tenant with the supplied site key. Connected operations are conditional on real backend availability, tenancy, authentication, and service status.

## 2. Configure target languages

Open the language configuration surface and select the target languages currently allowed by the product/backend contract. Save the configuration, leave the page, and return to verify it persisted.

Do not rely on a fixed marketing claim about the number of supported languages. Acceptance is based on the choices actually exposed and persisted in the verified customer environment.

## 3. Choose a gold-path source page

Use a normal page built with core/handwritten WordPress blocks under the stock Twenty Twenty-Five theme for launch acceptance. Record the source post ID/URL before translation.

Imported Site Content, block templates, synced patterns, third-party builders, WPML migration/interoperability, and other deferred surfaces are not required for this first-customer path.

## 4. Preview a translation

Request a preview for one configured target language. Review the source/target identity and translated content before publishing. Preserve the request/job identifier and relevant status evidence when available.

A preview failure caused by backend/auth/service conditions must remain visible as the actual failure or external dependency; it is not a successful local acceptance result.

## 5. Publish the translation

Publish the reviewed translation through the supported flow. Record the target post/page identifier and terminal status, then reload the relevant status surface to verify the state is consistent.

## 6. Revisit the source page

Return to the source page after publication and verify the translation relationship/intent is still represented. Make only the small source edit defined by `../launch/FIRST-CUSTOMER-ACCEPTANCE.md` and record the resulting source revision and translation state.

Automatic or continuous translation is not part of the first-customer promise. Manual-translation protection is accepted only when its separate implementation lane has actually landed and been verified.

## 7. Check the outgoing translated page

Open the translated customer-facing URL in a clean browser session and perform the manual publish-and-look check. The launch contract requires translated-page **presence** for the gold path; it does not turn this check into an unconditional promise of exact template, thumbnail, or visual fidelity.

## What is not implied by this guide

This workflow does not promise pricing/packages/trials, SLAs, advanced teams/workflow, analytics, translation memory/glossaries, broad multisite, broad WooCommerce/multi-currency behavior, third-party builders, WPML migration, or imported Site Content/templates/patterns.

Use `../launch/FIRST-CUSTOMER-ACCEPTANCE.md` for the executable acceptance record and `../launch/FIRST-CUSTOMER-SUPPORT.md` for incident ownership and rollback boundaries.