You have now done, at small scale, everything this academy teaches: describe something clearly, hand it to an AI, test what comes back, fix what is broken, and ship a working page. Everything past this point is the same loop, just with more capable tools and bigger projects.
Here is where each module picks up, so you can choose based on what you want to build next:
- If your project needs to be saved safely: start with GitHub Basics. It removes the fear of breaking things you cannot undo.
- If you want editor-based workflows on real files: move into Cursor for Beginners from the modules page.
- If you want AI to handle bigger multi-step tasks while you direct: choose Claude Code Crash Course from the modules page.
- If your project is built and only needs a real live home: choose Ship It Free from the modules page.
There is no wrong order beyond one recommendation: GitHub Basics helps no matter which tool you use next, so most people are better off starting there.
Assignment 1.7 - Pick your next step
You're done when: you have shipped a real project, tested it on a real person, fixed at least one real issue, and picked a specific next module.
0 of 3 items checked
Your notes save to your account and this browser.
Self-check
Why is GitHub Basics generally recommended as the starting point among the modules?
Because other workflows assume your project is saved safely with recoverable history. GitHub removes that fear first.
Is there a required order to the modules?
Not strictly. GitHub Basics is a strong first step, then choose based on what you want to build.