Docs · Getting started

Day-zero walkthrough

Five steps from your first login to your first finished lab.

Step 1

Pick a discipline

A discipline is a career track — for example, GenAI Engineering or AI Security Engineering. Each one bundles 2–4 courses and 24–48 chapters of focused work.

Open the Disciplines page to browse what's available.

The Disciplines page — a grid of GenAI engineering discipline cards, each with its course and goal counts — The Disciplines page · click any card to see its courses.

Step 2

Enroll in a course

Each discipline has multiple courses, sequenced for compounding. You'll see chapter previews before you commit, and every course unlocks its first chapter for free so you can scope-check before subscribing.

Once you're enrolled, the course shows up in your Progress dashboard and on the home page as a "Continue" card.

Step 3

Open your first lesson

Open any lesson (a chapter is just a set of them). Every lesson has the same three steps: Concepts → Knowledge Check → Hands-on Labs — read, quiz, then build. Jump between them freely; each chapter also has an audio overview. Progress saves as you go.

A lesson home page showing the Learning Path — Concepts, Knowledge Check, Hands-on Labs — plus the lab and prerequisites — A lesson home — the three-step Learning Path, the same layout in every course.

Step 4

Run your first lab

Open the lesson's Hands-on Labs step. After ~30 seconds, a real VS Code workspace opens in your browser. Each lab has a few TODOs marked clearly in the code. Implement them, run the lab, and iterate until both scripts pass on your code.

Tests run on GenBodha's cloud — no local setup, no Docker, no dependency hell. The lab persists for 24 hours so you can come back to it.

A lab's README preview — Lab Context, Business Value, a Source Files diagram, and a table mapping each TODO to a function and its rationale — Every lab opens with a brief — context, business value, the files, and a map of each TODO.

The lab workspace — file tree on the left, the starter file with its TODOs in the editor — A real VS Code workspace · the TODOs are marked right in the code.

Claude Code running in the workspace terminal, asked how to better understand a TODO — Stuck? Claude Code is built into the terminal — ask it how to approach a TODO.

The lab terminal showing run_lab.sh output ending in 'Application ran successfully!' — Run the lab — both scripts pass on your code, and the lab counts.

Step 5

Track progress

Your progress dashboard shows everything: lessons complete, hours learned, quiz accuracy, lab pass rate. Use it to see what to do next and how far you've come.

Progress dashboard with stats, active courses, and activity heatmap — The Progress page · stats, active courses, and a 12-week activity heatmap.

Was this page useful?