# Installing International Press Zone

This guide describes the first-customer installation path governed by `../launch/FIRST-CUSTOMER-SCOPE.md`.

## Requirements

The current plugin metadata requires:

- WordPress 6.5 or later;
- PHP 8.1 or later;
- an International Press Zone release artifact supplied for the customer;
- a Press.Zone site key and a reachable, authorized Press.Zone backend/tenant for connected operations.

The first-customer gold path uses the stock Twenty Twenty-Five theme and ordinary WordPress blocks. Third-party builders and other deferred integrations are not part of this installation acceptance path.

## Install the audited artifact

The release archive convention is:

`international-press-zone-<version>.zip`

Use the exact artifact provided for the customer and preserve its SHA-256 and source Git SHA in the acceptance record. Do not rebuild or rename an artifact and treat it as the already-audited package.

In WordPress:

1. Open **Plugins → Add New → Upload Plugin**.
2. Select the supplied `international-press-zone-<version>.zip`.
3. Choose **Install Now**.
4. Activate **International Press Zone**.
5. Open the International Press Zone onboarding/connection flow.

For first-customer acceptance, follow `../launch/FIRST-CUSTOMER-ACCEPTANCE.md` rather than treating a successful activation screen as complete acceptance.

## Connect to Press.Zone

Use the supplied **site key** through the supported onboarding/connection flow. Do not substitute WordPress credentials or invent a separate API credential-management requirement.

Connected translation, status synchronization, and related service-backed actions depend on the real Press.Zone backend, tenancy, authentication, and service availability. If those external dependencies are unavailable, record the actual `WAITING_EXTERNAL` or `FAIL` state in the acceptance evidence; do not turn it into a local pass.

## Support

Use the actual Press.Zone contact route supplied for the customer deployment and recorded in `../launch/FIRST-CUSTOMER-SUPPORT.md` / the acceptance record. This repository does not establish a generic support email, package-specific support entitlement, response time, trial, or SLA.

## Next step

Continue with `getting-started.md` for the scoped language → preview → publish workflow.