kristianwindandClaude Opus 5
fcedab0b19
The landing page did not mention two things the app grew — sharing a note with a person, and task durations — and its screenshots were all in the dark theme. - Copy: a cell for sharing a note or a page (to a person, or by filing it in a project, with the Shared with me group), and one for how long a task takes (drawn to length on the calendar, dragged by its foot, kept when moved). - Two new screenshots in the light theme, at the top of the gallery: the calendar drawing timed tasks to their real length, and a note somebody shared gathered under Shared with me. English throughout, like the rest of the site — the capture account is English, so the interface is. The generator grew the demo data these need: a handful of timed tasks with lengths across the week, and a note the colleague shares back to the owner. Every other screenshot was recaptured from the current build in the same pass, so the whole set reflects what ships today (the tidied note footer, and the rest). Co-Authored-By: Claude Opus 5 <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