About

How a course is put together

A track holds courses, a course holds lessons, and a lesson is prose you can read in about a quarter of an hour. Most carry a short quiz to check the concept landed and an exercise to write against in your own editor. You can take notes on any lesson, bookmark the ones you want to return to, look a term up in the track glossary, search across everything, and finish with a summary of what you actually did.

One course — AI Fundamentals — is written. The other eight are outlines with real outcomes and prerequisites and no lessons yet, and they say so.

There is no account, and no server

Nothing here asks you to sign in, because there is nothing to sign in to. The whole site is prerendered static files. What you complete, answer, write and prefer is kept in this browser’s local storage and never sent anywhere — which also means clearing site data erases it. The export file on your profile is how you back it up or move it to another machine.

The one exception is worth naming: the pages you visit are counted in aggregate by Vercel Analytics, so it is possible to tell which lessons get read. Nothing you type, answer or complete is part of that.

What it deliberately does not do

• No certificates. The completion summary is your own record of what you finished, and it is not accreditation.
• No streaks, badges or leaderboards. A counter that resets because you had a sprint deadline is worse than no counter.
• No code runner. Exercises are written for the SDK you already have installed. You run them where you would run any other .NET project.
• Nothing that needs a server to adjudicate. No comments, no ratings, no per-learner analytics. Faking any of them locally would produce a feature that lies to you.

It is open, all of it

The lessons, the curriculum and the code that renders them are one public repository, together with the architecture notes and the decision records explaining why it is built this way. If a lesson is wrong, the fix is a pull request.