Frontend applications¶
The initial implementation is merged. The selected product image architecture adds URL-based rendering and admin image management, with S3 integration deferred to the future Product service. Upload controls are enabled only in explicit fixture mode until then.
Three independent Next.js repositories are integrated as Git submodules and implemented for static CDN export. The local Docker setup serves them on one origin. This is an educational mock store: no real payments or transactions occur, and no goods are shipped. Demo orders are API records, not purchases.
Agreed decisions¶
- English UI, shared modern branding and the existing project logo.
- Public catalog browsing; authentication to create or read own demo orders.
- Next.js, TypeScript, MUI/Emotion, Tailwind and the approved TanStack/form/test tools.
- antislop applied during implementation; reference research and defaults authorized.
- Each app has a Dockerfile for local testing; no frontend Kubernetes manifests.
- Grafana Cloud is selected for observability; Cloudflare for DDoS/WAF/Tunnel security.
- A dedicated Redis Cart service is selected with seven-day expiry after writes; implementation is pending.
- Domain name and static CDN provider remain open.
- Production will use CDN hosting with separate per-app environment values. Ask the owner about provider, origin routing and variables before deployment.
- Additional libraries always require owner approval. No date library, queue framework, animation stack or 21st.dev runtime dependency was added.
Sites and content¶
| Repository / submodule | Path | Implemented experience |
|---|---|---|
Microsserv52/landing / web/landing |
/ |
Demo introduction, live catalog preview, platform explanation, privacy/diagnostic controls and documentation links |
Microsserv52/store / web/store |
/store/ |
Public search/sort catalog, product details, guest cart, login/register, authenticated review, demo order creation/history/details and read-only own account |
Microsserv52/admin / web/admin |
/admin/ |
Role-gated overview with API-derived counts, searchable/sortable/paginated products/accounts, create/delete product dialogs, account detail dialog and configured observability links |
Detail URLs use /store/product/?id=<uuid> and /store/order/?id=<uuid>.
These work for arbitrary runtime IDs without a server-rendered Next.js route.
Admin accounts are read-only in the UI. No product editing, all-orders admin
view, stock, shipping, payment fields or revenue reports are invented.
Every screen has appropriate loading, failure and empty/access states. Shopping copy uses “Add to demo cart” and “Create demo order”; confirmation says that no payment was taken and no goods will be shipped. Product images support optional URL metadata, with explicit fallbacks. Admin upload controls remain fixture-only until the future Product backend is accepted.
Documentation¶
| Page | Contents |
|---|---|
| Design | Defaults, visual decisions, real UI references and antislop |
| Architecture | Static zones, API-owned sessions, authorization and current contract limits |
| Dependencies | Approved packages, exact resolved versions and official setup |
| PWA and observability | Online-only store installation, Faro/Umami behavior and environment map |
| Local development and delivery | Real-service versus fixture Docker modes, commands, CI and remaining integration work |
| Verification | Actual checks, browser evidence and limits |
The initial implementation is merged and all ten source repositories are public. No CDN deployment or production telemetry endpoint has been configured.