kristianwindandClaude Opus 5
6116ed2e21
Typing [[ did nothing. The toolbar hint offered "[[ another note" and the parser turned a fully-typed [[Title]] into a link on save, but the completion that makes it usable — the one # has for projects — was never there, so you had to know and type a note's title exactly, brackets and all. Now [[ opens the same picker # does, over the notes the page has loaded: the current note is left out (a note linking to itself is a loop nobody meant), and one without a title yet cannot be pointed at. Choosing a note closes its own brackets — the opener is already in the text — and leaves a space, so the next word is a word and not more of the tag. On save the link is real and shows in the note's links, not merely as text. The picker's two kinds are told apart where a project wears its colour: a note suggestion wears the brackets that open it. e2e: [[ offers a note by title, choosing it writes [[Title]] into the note, and the link lands in the note's links. Full Chromium suite green. 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