How-To
How-To answers one question: Can you build real things with Putnami, easily?
Each guide is:
- outcome-driven
- reassuring
- cross-layer
- minimal but complete
Each guide should feel like: "Oh. That's it?"
What This Is Not
- not a framework manual
- not a CLI reference
- not exhaustive
- not language theory
If a guide tries to teach everything, it failed.
By Intent
How-To is organized by user intent, not architecture.
Plan
Build
Extend
- Add persistence
- Add authentication
- Add background jobs
- Add observability
- Structure business logic with DI
- Provision infrastructure and run conformance packs
Ship
Maintain
Learn by Running Code
If you prefer learning by running code, the TypeScript samples are a progressive learning path — 14 projects that build on each other from a minimal HTTP server to a full-stack app. Each sample is self-contained and runnable. They live in the repository under typescript/samples/, alongside go/samples/ and the experimental python/samples/.
The samples also cover surfaces the how-to guides do not: real-time, events, service-to-service clients, storage, caching, capabilities, and a capstone fullstack app that combines everything.
Structure Rule
Every guide must say:
- what you'll build (first paragraph)
- what you'll end with (last paragraph)
And it must end with:
You now have X.