Once the fundamentals from the first-30-minutes tutorial feel comfortable, the natural question is what to actually build next. These seven are ordered by what they require — the first three need nothing beyond static files, the next two introduce saving data between sessions, and the last two involve automation that runs on its own.
Write a short brief first — audience, the one action you want a visitor to take, and any must-have sections — then describe that outcome to Claude Code rather than the exact HTML. This is the best true first project: fully static, the result is visible in a browser immediately, and every change is easy to review.
A step up in scope from a single landing page: multiple pages, consistent navigation, and a bit more content to organize. Good for practicing the habit of making one contained change at a time instead of asking for the whole site in one pass.
Take a page you already have (or a rough draft) and ask for one specific improvement at a time — better mobile layout, clearer hierarchy, a working contact form. Editing existing structure is a different skill from generating from scratch, and it's the more common real-world task.
A simple tracker, checklist, or note-taking page that remembers what you entered after you close the tab. This is the first project that introduces persistent storage — a genuinely new concept worth isolating in its own small project before combining it with anything else.
Pick a handful of numbers you actually track — spending, habit streaks, simple stats — and build a page that displays and updates them. Combines the layout skills from earlier projects with the persistence from the previous one.
Instead of a one-off page, build a repeatable process: a script or workflow that drafts a content outline, checks it against basic on-page SEO rules (title length, one H1, meta description), and flags issues. This is where "building a website" turns into "building a system you reuse."
Automate one specific repetitive task you actually do by hand — formatting a weekly report, renaming and organizing a batch of files, or pulling a few numbers into a summary. Small in scope, but the closest of the seven to the operations work covered in the course's growth module.
These seven work as standalone practice, but the course covers them (and more) as a deliberate sequence — plus 180+ HTML/CSS/JS templates to use as real starting points instead of blank files.
See the Course — $35 →A single landing page from a written brief. It's small enough to review every change, has a visible result you can check in a browser immediately, and doesn't require any backend or data-persistence decisions yet.
No — each one is scoped to be achievable by describing outcomes and reviewing proposed changes, the same workflow habits covered in the beginner tutorial. Experience helps you scope tasks better, but isn't required to start.
Roughly, yes. The first three need no backend or persistent storage; the next two introduce saving data between sessions; the last two involve automation running on a schedule or against real business tasks — each step adds one new concept rather than several at once.