Introduction to Stew

Philosophy

Stew was originally built on top of templ and Go templates. The 0.1 release introduces the native Stew template language (.stew), a custom compiler that transforms these files into idiomatic Go code. The core principles are:

• One file, two contexts. A .stew file can contain both server-side logic (native Go) and client-side logic (compiled to Wasm).
• Convention over configuration. The directory structure defines the routing — no manual configuration required.
• Go is the language. No obscure DSL: the logic is standard Go inside <goscript> blocks.
• Zero front-end build. No Node.js, no bundler. TinyGo alone for WebAssembly.

Tech Stack

Minimal Project Structure

my-app/
├── pages/
│   ├── @layout.stew       ← Root layout (HTML shell)
│   ├── @page.stew         ← Route /
│   └── users/
│       ├── @layout.stew   ← Nested layout (optional)
│       ├── @page.stew     ← Route /users
│       └── __id__/
│           └── @page.stew ← Route /users/{id} (URL parameters)
├── component/
│   └── Card.stew          ← Reusable component
├── static/
│   └── wasm/              ← Automatically generated Wasm binaries
├── .stew/                 ← Cache tracker (gitignore)
├── .stew.yaml             ← Stew configuration
├── main.go                ← Server entry point
└── stew_router_gen.go     ← Automatically generated router