# Maintaining Zendi Brand

## Keep the resources consistent

Edit `index.html` for guideline content, `tokens.css` for shared design values, `brand-layout.css` for presentation and `brand.js` for behavior. Keep the public guide, visual examples, `design.md` and `MIGRATION.md` consistent whenever a standard changes.

Maintain stable asset paths and use the supplied logo artwork. The archive category is excluded from the default asset filter but remains available. When changing an export, update the inventory metadata and visible total, then validate dimensions, padding and byte counts.

Navigation arrows follow actual behavior: down for a jump within the current page, right for same-site navigation or a CTA in the current tab, and diagonal up-right exclusively for a new tab. Check copied snippets, illustrative components and downloads as well as ordinary links.

## Local preview

```sh
python3 -m http.server 8000
```

Visit http://localhost:8000. Opening `index.html` directly can prevent features that fetch local files from loading.

## Cloudflare Pages

Cloudflare Pages publishes this repository’s `main` branch through its Git integration. The website is static output at the repository root. No npm installation or application build is required; use the existing static-root configuration.

After publishing, check the Cloudflare Pages deployment for the committed revision and verify the live site at https://brand.zendi.dev. Validate navigation, responsive layouts, interactive examples and asset downloads.

The `_headers` file restricts scripts to the same origin and permits the font and image hosts used by the site. Update specific host permissions when adding an external resource. Keep scripts, images and fonts within the declared content security policy.

## Dependencies and privacy

The deployed site has no JavaScript packages, runtime API, login, forms backend, database or telemetry. Inter loads from Google Fonts with a system fallback. The architectural photograph loads from Cloudinary with a text fallback. Font binaries are not redistributed.

The browser ZIP builder fetches only the selected assets, retains relative paths and uses stored entries with CRC32. ZIPs containing native icons include the complete selected platform family and configuration files. Selection data stays in the browser.

## Validation

```sh
python3 scripts/audit.py
node --check brand.js
```

Browser checks use a development-only environment:

```sh
python3 -m venv .venv
. .venv/bin/activate
pip install playwright==1.63.0
python -m playwright install chromium
python3 scripts/browser_check.py
python3 scripts/regression_check.py
```

On Linux, `python -m playwright install --with-deps chromium` also installs browser dependencies. The scripts start local HTTP servers, exercise the guide, capture screenshots and verify ZIP contents. Reports are written to the ignored `review-output/` directory. External-resource failures are reported separately from local failures.

Inspect rendered desktop and mobile layouts, font and photo availability, keyboard focus, screen-reader names and new-tab announcements. Automated browser checks do not replace accessibility testing with assistive technology.

## Export specifications

`ASSET-GUIDE.md` documents padding, crop behavior and web/native icon integration. `asset-index.json` and `asset-index.csv` describe the supplied exports. Check destination requirements when uploading; export metadata describes the file itself.
