Your first project
A project in Typillar is the thing you’re building — a site, an app, a service — together with its history, its repository, and the resources it runs on. You grow a project the same way you start one: by describing what you want next.
Start small and concrete
Section titled “Start small and concrete”The best first ticket is small and specific. Instead of “a SaaS for gyms,” start with the first useful slice:
A landing page for my gym with a “join the waitlist” email box.
A tight first ticket builds fast, is quick to Ship, and gives you something live to react to before you decide what’s next.
Grow it incrementally
Section titled “Grow it incrementally”Once the first piece is live, add to it one change at a time:
- “Put the waitlist count on the page.”
- “Add a pricing section with three tiers.”
- “Ask people what they’d use it for.”
Each becomes a tracked ticket, and each build leaves a set of commits. When you want what you’ve built to go live, you Ship — one action for the whole project, not one per ticket. The project accumulates into something real without ever needing a big upfront plan. See The build loop.
Not sure what’s next?
Section titled “Not sure what’s next?”Just describe it. There’s no separate planning step — type the next feature or fix into the thread and it builds, or park it as a ticket in the Plan tab to build later. See Tickets & the thread.
What’s behind the project
Section titled “What’s behind the project”While you work in plain language, each project is backed by real, owned infrastructure:
- a GitHub repository with every change (Connect GitHub),
- Cloudflare resources — Workers, and any databases or triggers the features need (Connect Cloudflare),
- a version history you can restore the code from, and a deployment history you can roll a live Worker back from (Deploys & rollback).
- Tickets & the thread — how requests become tracked work.
- Project history — tracing how your project evolved.