Files

T

Kristian WindandClaude Opus 5 1a6adfd9d3 docs: screenshots that regenerate themselves, and eleven of them

They were many rounds behind — no settings, no task detail, no themes, no groups,
no colours, no calendar, no admin pages. The reason is in how they were made:
`tools/shots` needs a running instance and a session cookie pasted in by hand, so
it ran about as often as somebody felt like doing that.

`node scripts/generate-screenshots.js` starts the real binary, creates its own
account, fills it with Danish demo data and photographs eleven surfaces into both
`site/screenshots` and `docs/screenshots`. Nothing to set up and nothing to
remember.

A script rather than a test, for the same reason `generate-icons.js` is one: CI
must never rewrite a tracked binary file.

`tools/shots` stays. It is still the way to photograph an instance that is
already running rather than a fresh one.

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

2026-08-18 09:05:36 +02:00

e2e

fix(forms): Safari focused none of them, and a board could not make a section

2026-08-18 09:05:02 +02:00

scripts

docs: screenshots that regenerate themselves, and eleven of them

2026-08-18 09:05:36 +02:00

src

feat(gmail): the OAuth client can be entered instead of deployed

2026-08-18 09:05:18 +02:00

static

feat(pwa): the PNG icons the manifest and iOS have always wanted

2026-08-17 22:37:52 +02:00

jsconfig.json

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

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

package-lock.json

build: lift Vite to 8, and get the tree out of iCloud's way

2026-08-18 09:03:45 +02:00

package.json

build: lift Vite to 8, and get the tree out of iCloud's way

2026-08-18 09:03:45 +02:00

playwright.config.js

fix(forms): Safari focused none of them, and a board could not make a section

2026-08-18 09:05:02 +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

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