S2. Quick start
What this page helps you do
Take the shortest practical path through the guide without getting lost in optional branches.
Why it matters
Many launch mistakes come from missing one boring but important step. A quick-start path gives you a baseline even if you are busy, impatient, or not very technical.
You should already have
- some code, a prototype, or a clear idea of the app you want to ship
Skip this page if
- you want to choose a more specific app path first
- you already know which parts you already finished
In that case, go to S4. Choose your path or S5. What you already have.
What to do
Follow this default route:
- Pick your app path in S4. Choose your path.
- Put the project in GitHub with F1. Put your code on GitHub.
- Make sure it runs on your machine with F4. Run your app locally.
- Choose where it will live with H1. Choose hosting.
- Get it online with H6. Deploy your app.
- Put a real domain in front of it with D2. Set up Cloudflare and D3. Point your domain to your app.
- Check the basics before launch in R8. Launch checklist.
If you want the fastest route by situation:
- starting from scratch: begin at S4. Choose your path
- already have code in GitHub: jump to B1. Already have GitHub
- already running locally: jump to B2. Already running locally
- already online but nervous: jump to B12. App already online but messy
If you hit a wall:
- app works locally but not online: T1. App works locally but not online
- domain not working: T2. Domain not working
Recommended default
Choose the simplest hosting that fits your app.
- simple website: managed hosting is usually enough
- small app with login or database: managed hosting is still usually the easiest
- AI app or background jobs: use a path that clearly supports long-running work, logs, and secrets
If you do not know which path to take, start with P2. SaaS web app path. It covers the most common shape of a modern app.
Common mistakes
- launching straight from a laptop demo
- not knowing where secrets are stored
- not knowing how to roll back after a bad deploy
- buying a domain before the app works in a basic hosted environment
Next step
Go to S4. Choose your path, or jump to S5. What you already have if you are not starting from zero.
Related pages
Advanced notes
If you are using this repo inside an agent workflow, this page is the fastest human-readable summary of the default launch path.