Start here
If you are new, read these in order. Each one builds on the last.
- Getting Started installs the CLI and builds your first page end to end.
- The Language covers the mental model: pages, components, layouts, build-time versus request-time, and guards.
- Architecture explains how the compiler, generated adapters, and runtime fit together.
The language
- Language overview is the full
.gwdkreference: annotations, blocks, render modes, markup, components, and slots. - Forms & progressive enhancement shows how forms and links work without JavaScript, then enhance into fragment requests.
- SSR & request-time explains opting into request-time rendering with
loadandgo ssr.
Reference
- Routing covers routes, dynamic params, rest params, and the trailing-slash policy.
- Config documents source discovery, modules, build output, CSS settings, render defaults, and addons.
- CLI lists every command for scaffolding, checking, building, watching, and serving a project.
- Deployment walks through publishing static files, generating a Go app, and shipping a single binary.
What makes GOWDK different
- Go owns the build. No Node toolchain is required. The CLI is one Go binary and your project is normal Go code.
- Compile first, serve later. Pages render at build time by default and you opt into SPA or SSR behavior only where it is needed.
- Everything is explicit. Routes, guards, render lanes, and component usage are declared in the source file, never inferred from folder layout.
- Portable output. Ship static files to a CDN, run the generated app, or package the whole site into a single executable.