# KLIGO — start here

Read `LAUNCH_SCOPE.md` first: website first, all four categories, subscriptions and paid placements only. Buyer/supplier deals and payments happen directly between the parties. See `MATERIALS_HANDOFF.md` for new stock and site surplus.


## 1. Choose the complete project

**Download complete project** at `/design-system#resources` is the main handoff. It includes source code, assets, translations, docs, tests, the dependency lockfile and build tools.

The **component kit** is optional. It contains design/component references and guides, but is not a runnable application. Everything needed to run the website is in the complete project.

Extract the ZIP. Open the `kligo-website/` folder. The following commands run from that folder, not from the outer folder containing this guide.

## 2. Run locally

Requirements: Node.js 22.13 or newer, npm, Bash, network access and GNU coreutils (`timeout`). Use Linux or WSL2 on Windows. On macOS, install GNU coreutils and make `timeout` available on PATH. Native Windows without Bash is not supported by these scripts.

```bash
npm ci
npm run dev
```

Open the address reported by the development server. Inspect `/design-system` first, then follow its links to the actual screens.

To create and check the production build:

```bash
npm run build
node --test --test-concurrency=1 tests/developer-handoff.test.mjs
```

The test verifies the downloadable archives. It does not prove that a production backend exists. Additional workflow tests are in `tests/`.

## 3. Understand the boundary

This is a responsive web prototype, not an operating commercial marketplace. Sample listings, identities, reviews, prices and reports are illustrative. Some interactions persist in this browser or tab; they are not shared server records. Messages, support requests, payments and report drafts do not reach real operational services.

The public website link gives viewing access only. Real application authentication, database persistence, permissions, uploads and subscription/placement billing must be implemented.

English, Hebrew and Arabic presentation is implemented. Independent native-speaker/RTL acceptance and production locale/SEO handling remain open. Technical guides are in English.

Native iOS/Android source and app-store binaries are not included. Use `MOBILE_APP_HANDOFF.md` if a native app is commissioned. Figma is optional; the responsive website and source are the implementation reference.

## 4. Where to look

| Need | Location |
| --- | --- |
| What each feature does now and what remains | `docs/FEATURE_STATUS.md` and the kit's Functionality section |
| Decisions before kickoff | `docs/HANDOFF_READINESS.md` |
| Work sequence and exit criteria | `docs/INTEGRATION_CHECKLIST.md` |
| Current pages and redirects | `docs/CURRENT_ROUTE_INVENTORY.md` |
| Proposed API and permissions | `docs/API_AND_AUTHORIZATION_CONTRACT.md` |
| Proposed data structure and migrations | `docs/DATA_MODEL_AND_MIGRATIONS.md` |
| Detailed implementation behavior | `docs/IMPLEMENTATION_REFERENCE.md` |
| Language rules | `docs/HEBREW_LOCALIZATION.md`, `docs/ARABIC_LOCALIZATION.md` |
| Native app scope | `docs/MOBILE_APP_HANDOFF.md` |
| Visual reference and online guides | `/design-system` |

Older architecture and route audits describe earlier snapshots. The generated current inventory and actual source take precedence. Proposed contracts still need developer review against the agreed launch scope.

## 5. Source and assets

| Folder | Purpose |
| --- | --- |
| `app/` | Routes, shared layout and styles |
| `components/kligo/` | Approved reusable interface controls |
| `components/marketplace/` | Search, cards, maps and listings |
| `components/customer/`, `components/provider/`, `components/profiles/` | Customer and provider journeys |
| `components/i18n/` | English, Hebrew and Arabic presentation |
| `components/developer/`, `content/developer-handoff.json` | Developer view and handoff content |
| `public/` | Logos, representative images, credits and downloads |
| `docs/`, `tests/` | Implementation guides and verification |

Keep the supplied KLIGO SVGs unchanged. Brand colors are #FBB104, #0A0A09 and white. Reuse existing controls and `app/globals.css`. Font configuration is included; Heebo, Assistant and Noto Sans Arabic font binaries and their licenses are not bundled. The website currently loads fonts externally. Review asset credits before production reuse and replace sample company identities with authorized real data.

## 6. Package identity and ownership

Each ZIP includes `export-manifest.json`, which fingerprints its payload. The kit shows export time, size and download checksums under Package details. Exports regenerate during the build; they are working snapshots, not a frozen approval record.

The ZIP excludes Git history, environment files, secrets, generated builds and hosted project bindings. Its sanitized hosting file does not grant access to the existing KLIGO hosting account. The owner and developer should arrange a separate owner-controlled repository and hosting access. Never put credentials into the ZIP or source control.

## 7. First developer milestone

Confirm the local build and the first release scope. Then demonstrate real sign-in → company membership → draft listing → review → publication → public listing, with records surviving reload and another device, and access denied to the wrong account.

Viktor supplies business decisions and appoints account/operational owners. The developer supplies implementation estimates and acceptance evidence. No real payment, legal approval, vendor selection or launch sign-off is implied by this handoff.

## Light and dark appearance

Both responsive website designs are included. Use the moon/sun switch or Developer Kit → Color. Both ZIP downloads include the theme source; the CSS token download contains both palettes. Read `docs/DARK_MODE_HANDOFF.md` for setup, reuse and acceptance checks.