kristianwindandClaude Opus 4.8
7066e2e06e
The landing page and the docs now show and describe what has landed since the last site update: - the delegated-task marker (an arrow to whoever has it) — visible now in the board, list and Waiting-on-others shots - snooze — one seeded task is parked so the board shows a card greyed at the foot of its column - Web Push reminders to iPhone and Mac, dated tasks in a subscribed calendar, task durations on the calendar, and per-person note sharing Screenshots regenerated against the current UI (PNG for docs/README, WebP for the landing page, from the one capture). "Lately" brought current. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
web
The SvelteKit PWA. Not written yet — this directory holds its place so the Docker build has something to copy, and so the frontend stage can tell "not built yet" apart from "the build failed".
The Dockerfile builds this directory when it finds a package.json here, and
otherwise emits a placeholder page. So adding the real app is exactly: put a
SvelteKit project in this directory whose npm run build produces build/.
What it needs to be
- SvelteKit,
adapter-static, output inbuild/. The Go binary embeds that directory at compile time and serves it, falling back toindex.htmlso client-side routes survive a reload. - A PWA: installable, offline reading of already-cached lists, swipe gestures for complete and schedule.
- Nordic minimalism. Dark by default, light available. One accent colour, everything else neutral. Runic mark for Verdande.
- Optimistic on every local action. No spinner ever appears for something the browser could already know the answer to.
Talking to the backend
Same origin — the Go binary serves both. /api/v1 for REST, /api/v1/ws for the
live sync. Session cookie is httpOnly, so the frontend never handles the token
itself.
During development, run the backend on 8080 and point the Vite dev server's proxy at it:
VERDANDE_DATA_DIR=./data VERDANDE_DEV=true go run ./cmd/verdande