Guides
Build a login system with AI
A login system is authentication (who you are) plus authorization (what you may do). Spell out the security rules so the AI doesn't hand you holes.
A working prototype that can register, sign in, sign out, and gate access by role — and you know which security rules you must not skip.
Design a database with AI
Database design means deciding what to store and how things connect first, then letting AI turn that into tables.
A clear table draft (columns, types, relationships, indexes) you can hand straight to AI to generate a migration.
Cloudflare vs Vercel for beginners
Vercel is the smoothest for Next.js with the best DX; Cloudflare has a generous free tier with strong edge and database integration. It depends what you value.
A clear call on which platform fits your project — and what your first step is once you've chosen.
Grow a form into a CRM
Don't build the big system on day one. Start with a form, then add a list, login, and permissions as you need them — a CRM is grown, not built all at once.
An upgrade path from form to CRM, knowing what to add at each stage and what signal means it's time for the next.
Deploy to Cloudflare Pages
Connect Cloudflare Pages to your Git, and every push auto-builds and goes live — shipping shouldn't be hard.
A site connected to Git that auto-deploys on every push, served on your own domain, all within the free tier.
Choosing a database: D1 vs Postgres vs SQLite
SQLite is simplest, Postgres is most capable, D1 fits Cloudflare best. For most beginner projects, just pick the simplest one that works.
A clear call on which database your project should use and why — no more choice paralysis.
Build a contact form that collects email
Collecting messages looks simple; the hard part is that a static site has no backend — this covers who receives the message and how to prevent abuse.
A contact form that actually delivers messages, and clarity on which receiving method a static site should use and what abuse protection to add.
Add payments with AI: a Stripe overview
Amounts, success, and double-charges all have to be correct — this covers the key pieces of payments and why 'payment succeeded' must come from a backend webhook.
An understanding of the key payment pieces (Checkout, webhook, reconciliation) and which decisions must never be left to the front end.
Get found by Google: SEO basics
SEO isn't magic — it's making your site easy for Google to find and understand. Get the basics right and your content gets a chance to be seen.
An understanding of the few basics that get a site indexed and understood by search engines — and which myths waste your time.
When AI's code breaks: a debugging primer
Debugging isn't guessing — it's narrowing down and feeding the right clues back to the AI. Learn this and the AI can actually fix it.
A fixed routine for broken code: how to read the error, narrow the range, and give the AI the clues it needs to fix it.
Where to keep API keys and passwords: secrets 101
A secret in the front end or in version control is effectively public — this covers where to keep them, how to use them, and how to recover from a leak.
Knowing where keys/passwords belong (env vars / platform secrets), where they must never go, and the right recovery after a leak.
Manage your code with Git: a beginner's start
Git is a save point and time machine for your code — learn a few basic actions and you can change boldly and roll back anytime.
Being able to save progress, view history, roll back to a working version, and sync safely with the cloud using Git.