kristianwindandClaude Opus 4.8
9d4a13c2c2
A task is plain text — the title is an input, the description a textarea — so a pasted URL just sat there as words. It is now caught at display time and shown as a link in the list and on the board, without the stored text ever being anything but plain text. The link cannot live inside the row's open-button (an <a> in a <button> is invalid), so the body is a container with the open action as an overlay behind it: plain text and the meta row still open the task, links are raised above and take their own click. Conservative about what counts — an explicit http(s):// or a bare www. host, not every dotted word. 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