Course Generator
A tool I built that turns any piece of software into a full course on its own. You give it a tool name, it researches the real docs, and it produces both a written guide and a deployed interactive web course you can hand to a team.
The problem
Every time a team adopts a new tool, someone has to teach it. Writing a real course is slow, manual work: dig through the docs, find the good tutorials, figure out a sensible order, write the lessons, and then build something people will actually open. Most of the time nobody has the days to do it, so the tool gets handed over with a link and a shrug, and adoption stalls.
What I built
One command that builds a complete course for any tool. You give it a name (Cursor, Notion, whatever the team is rolling out) and it does the whole job end to end. It produces two things:
- A written course as a Markdown file. Structured so it can go straight into NotebookLM, with modules, lessons, step-by-step tasks, workflow examples, a quick-reference table, an FAQ, and a first-week plan.
- A deployed interactive web course. A Next.js site that goes live on its own URL (something like
{tool}-course.vercel.app), with checkable tasks, progress tracking, and resource buttons next to each lesson.
This is the generator, not a single course. It is the tool that makes the courses. The "Learn Claude" LMS is one finished course; this is the thing that can spin up the next one for any other software.
How it works
It runs in clear phases:
- Research. It searches for the tool's official documentation, quickstart, and changelog, then finds recent video tutorials, written guides, and the primary community (the right subreddit or forum). It favors official sources and recent videos so the content does not go stale.
- Write. It generates the Markdown course aimed at smart beginners: plain language, no jargon, second person, simple metaphors, and examples written to work for any industry. Five or six modules, a few lessons each, every task with real step-by-step instructions and a link to the actual tool.
- Build and deploy. It fills a Next.js course template with that content, sets the branding and the official docs link, then builds and ships it to Vercel so the web course is live at the end of the run.
The details that make it usable
A few choices that came from actually wanting people to finish a course, not just receive one:
- Every task has numbered steps and a button to open the relevant tool, so there is no guessing what to click.
- Each module's first lesson links out to a real community (a subreddit or forum) so learners can see how others use the tool and ask questions.
- There is a workflow library at the bottom, split into beginner, intermediate, and advanced patterns, that people explore after the core curriculum.
- Video and resource links are held to a freshness standard, since these tools change fast and an out-of-date tutorial does more harm than good.
Why it matters
Adoption is where most tool rollouts die. For an implementation role, building the system is only half the job; getting a team to actually use it is the other half. This is how I close that gap quickly: instead of one course taking a week of writing, I can stand up a real, deployed course for whatever a team is adopting and move on to the next thing.