What you learn
- What frontend, backend and database mean and how they hand work to each other
- How Next.js, Astro, TanStack Start and Vue differ and when to reach for each
- The marketing-site versus app split and when a monorepo is worth its complexity
Summary
You finished Course 1 by shipping a real site, and Course 2 by turning your agent into a power tool. Now you graduate from a single static site to a real application with users, data and payments. Before any of that, you need the map. This lesson is that map: what a framework actually does for you, the three layers every app is built from, why serious teams split a fast marketing site from the heavier app, and when a monorepo is a gift versus a tax. Get this clear and every later decision in this course stops feeling arbitrary.
What you will learn
You will learn the difference between frontend, backend and database in plain language, how the main 2026 frameworks compare and when each fits, why companies like Clerk and Convex run a separate marketing site from their app, and the honest rule for when a monorepo pays for itself. By the end you can sketch the architecture of any SaaS on a napkin and explain why it is shaped that way.
Prerequisites
Course 1, especially the project setup and deploy lessons, since architecture decisions build on a working build-and-ship loop. You should be comfortable running terminal commands and have deployed at least one site. If the words "framework" or "TypeScript" are still fuzzy, skim the Fundamentals pages on what a framework is and what TypeScript is first, then come back.
A framework is a ready-made structure for building apps so you do not start from scratch. Learn what frameworks are and why nearly every app uses one.
TypeScript is JavaScript with type checking that catches mistakes before you run your code. Learn what it is and why so many projects use it.
Node.js is a runtime that lets you run JavaScript outside the browser. Learn what it is, why you need it, and how to install it in a few minutes.
A database is an organised store for your app data that you can save, search and update. Learn what databases are and the main types in plain language.
The problem
Most beginners glue an app together by copying whatever a tutorial did, with no model of how the pieces relate. Then they hit a wall: the marketing page is slow because it is bundled with the whole app, auth and data are tangled into the UI, and nobody can say where a given responsibility lives. The result is an app that is hard to change and impossible to reason about. None of that is a coding skill problem. It is a missing mental model. This lesson installs the model so your agent builds on solid ground instead of a pile of copied snippets.
Comments
Loading comments.
Post a comment