# Marketplace Frontend

Angular 21 multi-tenant marketplace platform frontend. Standalone components, signals, no NgRx. One codebase serves unlimited tenants ("marketplaces") via a per-tenant `bootstrap.json` fetched at runtime — no tenant-specific code paths.

Three surfaces on this one codebase:
- **Storefront** (`/`) — the public shopping site: catalog, product pages, cart, static/CMS pages.
- **Builder / Project Editor** (`/edit/**`) — in-app editor that edits the tenant's `BootstrapConfig` (theme, nav, homepage sections, widgets, footer, languages, static pages).
- **Backoffice / Admin** (`/:lang/backoffice/**`) — products, categories, orders, transactions, users, moderation, media, monitoring, analytics.

## Architecture

`Component (container) → Facade → Domain Service → Repository/Provider (DI token, swappable mock↔API) → Mock | API`

Enforced by `npm run arch:check` (import boundaries + circular deps), not just convention. Full detail: [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md), governance ADRs at `docs/architecture/foundation/**`.

## Frontend status

**Release Candidate — feature-complete.** See [`docs/PROJECT_STATUS.md`](docs/PROJECT_STATUS.md) for the honest current-state breakdown (completion %, known limitations, readiness for demo/production/backend).

## Backend

**Not implemented yet — fully specified.** Every domain currently runs against an in-memory/mock gateway except Categories (the one domain wired to a real HTTP API). The complete contract a backend engineer needs — every endpoint, DTO, auth flow, error model, upload contract, and a step-by-step implementation checklist — lives in one canonical document:

**[`docs/BACKEND.md`](docs/BACKEND.md)**

## How to switch Mock ↔ API

Toggle `useMockData` in `src/environments/environment.ts` (or `environment.production.ts`). `RuntimeProviderStrategyService` (`src/app/core/providers/runtime-provider-strategy.service.ts`) reads this flag per-domain to decide whether a facade gets the mock or real gateway. On `localhost` with `useMockData: false`, some domains (bootstrap, categories) still fall back to mock automatically so local dev never silently hits a real backend by accident — see that service for the exact per-domain logic.

## Development

```bash
npm install       # install dependencies
npm start         # local dev server
npm run build     # production build -> dist/dexarmarket/
npm run arch:check   # import-boundary + circular-dependency check
```

## Folder structure

```text
src/
├── app/
│   ├── components/       # Shared storefront components (header, footer, product-card, etc.)
│   ├── core/              # Auth, admin-auth, config/tenant resolution, DI providers, interceptors
│   ├── dynamic-renderer/  # Bootstrap JSON -> section/widget rendering pipeline (live homepage engine)
│   ├── facades/           # Runtime, website, builder, and backoffice facades
│   ├── features/          # Domain features: admin/*, project-editor, content-management, website/*
│   ├── guards/            # Route guards (language, admin-auth, dirty-state, etc.)
│   ├── i18n/              # Translation service, pipe, and locale packs (en/ru/hy)
│   ├── pages/             # Top-level routed pages: home, cart, static-page
│   ├── services/          # API, cart, auth, SEO, Telegram, and language services
│   ├── shared/             # Shared UI primitives (button, dialog, confirm-dialog, table, etc.)
│   └── widgets/            # Dynamic-renderer widget components
├── assets/mock/            # Local mock configuration and catalog data
├── environments/           # Development and production environment settings (incl. useMockData)
└── styles/                 # Shared global styles and themes
```

## Documentation map

Full index: [`docs/PROJECT_INDEX.md`](docs/PROJECT_INDEX.md). Key entry points:

| Doc | What it covers |
|---|---|
| [`docs/PROJECT_STATUS.md`](docs/PROJECT_STATUS.md) | Current completion status, honest limitations, demo/production readiness |
| [`docs/BACKEND.md`](docs/BACKEND.md) | The one canonical backend spec — endpoints, DTOs, auth, security, errors, uploads, checklist |
| [`docs/NEXT_PHASE.md`](docs/NEXT_PHASE.md) | Roadmap: backend integration → testing → performance → monitoring → v2 |
| [`docs/TODO.md`](docs/TODO.md) | Release blockers only |
| [`docs/KNOWN-ISSUES.md`](docs/KNOWN-ISSUES.md) | Real, reproducible, currently-open frontend bugs |
| [`docs/PRODUCT_BACKLOG.md`](docs/PRODUCT_BACKLOG.md) | Items needing a client/business decision |
| [`DESIGN.md`](DESIGN.md) | Visual design system |
| [`PRODUCT.md`](PRODUCT.md) | Product positioning |

## Notes

- Authentication and payment integrations are on their existing contracts — see `docs/BACKEND.md` for the auth/security contract a real backend must satisfy.
- Client-facing content should avoid placeholder names, mock labels, and temporary routes.