docs/ — the manual
The manual is part of the product
Eight guides written with the code they describe, a ten-minute tour of the architecture, and a log of every non-obvious decision. Published online — and shipped in the repository you buy, so your copy never goes stale behind ours.
guide/getting-started.md
Getting started
From clone to signed-in user in one sitting.
guide/tour.md
The ten-minute tour
One request followed through every layer: router, middleware, service, query, response.
guide/labs.md
The labs
The whole product on your machine — SSO, uploads, checkout, email — with nothing to configure.
guide/stripe.md
Stripe
Switching billing on from nothing, and removing it entirely.
guide/security.md
Security
The baseline and the reasoning: argon2id, CSRF, headers, rate limits, hardened egress.
guide/testing.md
Testing
Both database engines in CI, Playwright driving the real production binary.
guide/deploy.md
Deploy
A VPS, Traefik, Let's Encrypt — and one binary to run.
guide/customizing.md
Customizing
Renaming the module, rebranding the front, adding your first domain package.
Every page lives in docs/ in the repository — the same source publishes docs.govuekit.dev
DECISIONS.md
Why it is the way it is
DECISIONS.md records every ambiguous choice: the option taken, what it was weighed against, and why — including the features that were built and then removed to keep the kit a core. You inherit the reasoning, not just the result.
docs/TOUR.md
Ten minutes, every layer
The tour follows one request from the browser to the database and back. If the architecture cannot be walked in ten minutes, it is not simple enough — that is the bar the kit holds itself to.
Take the tour →Stop rebuilding the same foundation.
Accounts, teams, billing, emails, admin, security: the weeks that pass before you write the first line of your actual product. They are already written, tested and documented.