Files

T

Kristian WindandClaude Opus 5 d288606827 feat(web): open a task

TaskRow has had an onedit prop that nothing passed. There was no way to
see a task's description, sub-tasks, comments, files or reminders, all of
which the API has supported from the start.

A drawer rather than a page, so the list you came from stays behind it
and ticking a sub-task off and closing lands you where you were rather
than at the top of a re-fetched list. Mounted in the root layout and
driven by an id in the store, so a task opens the same way from Today, a
project, a label or a saved filter — and so an edit arriving over the
socket reaches the drawer without a second source of truth to keep in
step.

Text fields save on blur. A PATCH per keystroke is forty requests for one
sentence, and the last to arrive is not necessarily the last one sent.

The navigation shortcuts are suppressed while it is open: with a task in
front of you, "t" means the letter t.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-17 10:56:33 +02:00

src

feat(web): open a task

2026-08-17 10:56:33 +02:00

static

fix(web): the label route was written outside the routes tree, and the PWA promised icons that do not exist

2026-08-17 08:47:29 +02:00

jsconfig.json

feat(web): SvelteKit PWA with the Nordic design system

2026-08-17 00:03:20 +02:00

package-lock.json

feat(web): SvelteKit PWA with the Nordic design system

2026-08-17 00:03:20 +02:00

package.json

feat(web): SvelteKit PWA with the Nordic design system

2026-08-17 00:03:20 +02:00

README.md

fix(docker): give web/ a tracked file so the build stage can copy it

2026-08-16 23:09:09 +02:00

svelte.config.js

feat(web): SvelteKit PWA with the Nordic design system

2026-08-17 00:03:20 +02:00

vite.config.js

feat(web): SvelteKit PWA with the Nordic design system

2026-08-17 00:03:20 +02:00

vite.config.js.timestamp-1786947770614-506f9339d94dd8.mjs

docs(site): real screenshots, an English example, and the Rune said plainly

2026-08-17 08:37:10 +02:00

README.md

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 in build/. The Go binary embeds that directory at compile time and serves it, falling back to index.html so 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