ab0f7da50d
- Add --color-accent-fill (#cc0230) / -hover / -ink tokens; repoint all solid yellow "button" surfaces (Button accent, IconButton accent, language-selector active pill, Navbar cart CTA, Kaiserhacks chip, accent Badge) to crimson fill + white ink. Yellow --color-accent kept for functional text accents. - Secondary button: transparent fill, white border, white text/icons, translucent-white hover (no longer mimics the primary default). - Surfaces to pure white: --color-cream and --color-surface -> #ffffff (cream-toned logo follows via text-cream); theme-color -> #ffffff. - Self-host Zeitung (Regular/Bold woff2, mirrored from production); point --font-sans/--font-serif at Zeitung; drop Google Fonts CDN. - Remove yellow highlighting on hero/title emphasis and hero eyebrows (text-accent-soft -> text-cream, eyebrows -> text-cream/75). - WaveDivider + homepage section dividers: straight diagonal (low-left, high-right) at double height for ~2x the right-to-left difference. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Kaiser Natron
Ecommerce frontend. Vue 3 + Vite + Tailwind v4. Backend (PHP / MySQL, Stripe for payments) is plugged in at the src/api/ boundary.
Setup
npm ci
npm run dev
Design system
Everything visual lives in src/design-system/:
tokens/— color, typography, spacing, radius (CSS custom properties consumed by Tailwind v4's@theme)primitives/— atomic components (Button, Input, Badge, Stack)patterns/— composed components (ProductCard, etc.)
Browse the full system at /design when running npm run dev. This is the single source of truth — new UI composes these, never one-off styling.
API boundary
src/api/ exposes a typed surface the backend dev fills in. Until then, fixtures in src/api/ drive the UI so frontend work is unblocked.
Endpoint specs for backend integration live under docs/api/:
docs/api/cart.md— cart endpoints, types, error codes, and how to swap the local implementation for HTTP.docs/api/checkout.md— Stripe handoff: PaymentIntent creation, client-side confirmation, and the webhook that finalises the order.docs/api/orders.md— order lookup and customer order history.docs/api/customers.md— account, login, and address endpoints used by the checkout and account pages.
Supply chain
All dep versions are pinned exactly (no ^/~). Use npm ci (not npm install) in CI and before builds. Run npm audit before adding any new dep.
Deployment (Portainer dev-showcase stack)
This is the showcase path, not real production — the dev machine is the source of truth for the built output. The container has no build step: it just copies a prebuilt dist/ into nginx.
Release flow:
npm run build # produces /dist
git add dist && git commit -m "build: <what changed>"
git push
Then in Portainer → Stacks → Pull and redeploy. The site comes up on host port 5555 (/health returns 200 ok).
Base image: nginx:1.27.3-alpine (pinned). When this graduates to real production, reintroduce the multi-stage Node build + the hardening (read_only, security_opt, resource caps) that lived in earlier revisions of this file.