10. Ship it
The build directory is the site. Serve it from anywhere — the files are plain HTML, CSS and a little JavaScript, with no runtime to install.
One thing worth knowing before deploying: the layout writes /style/style.css and /projects/ — fine at a domain root, wrong under a subpath (GitHub project Pages serve from /repo/). If your site will live under a subpath, resolve URLs with Ctx.Asset/Ctx.Link and build with RelativeURLs: true; the same build then works from disk, at a localhost root, and deployed — see The Node tree.
That's the whole framework: a tree of nodes, pages as templ components, collections from markdown, locales derived not written, and interactivity compiled at build time. Everything else — the router, WASM scripting, SEO head, RSS — is documented under the pages on the left.
Try it. Serve the build directory with any static file server — python3 -m http.server, npx serve, whatever you have.
What you should see
The site works from any static server: plain HTML, CSS and a little JavaScript, with no runtime to install.
How should pages link to assets?
Ctx.Asset and Ctx.Link are base-aware, so one build works from disk, at a localhost root, and under /repo/.
What is in the build directory?
Build writes static files — the site is ready to serve from anywhere, with no runtime to install.