Hello from the snoozestack blog

SnoozeStack now has a blog. This first post is here to say what it's for, so you can decide whether it's worth following.

Three kinds of posts, roughly:

• Product updates. When something ships that changes how you build on snoozestack, it gets written up here with enough detail to actually use it, not just a changelog line.
• Technical articles. How a piece of the platform works underneath, and why it was built that way. The runtime, the CLI, the way projects move between your machine and production.
• Build stories. The apps we build on it ourselves, and what we ran into along the way. The whole point of snoozestack is that one person can ship several useful apps, so the stories are about that.

What you won't find is filler. If there's nothing worth saying, nothing gets posted.

If you haven't tried snoozestack yet, the whole local backend is one npm install away. The installation page always has the current command, since the CLI is published at version-pinned URLs. After that, a backend is two commands:

mkdir golf && cd golf
snoozestack init
snoozestack dev

That gives you a project folder with a project.toml, a schema, and a starter function, all running locally. The Get started guide walks through turning that into a real app, and the docs cover everything the CLI can do from there.

There's an RSS feed if you'd rather not check back by hand. Every post also links to the docs it touches, so a post is never the only place something is written down.

Thanks for reading. More soon.