Don't wait for a perfect repo.
This page packages the smallest credible path from Markdown notes to a course-shaped repo: a known-good config, lesson frontmatter, quiz example, and a launch checklist that keeps self-host and hosted both open.
Turn a folder of Markdown drafts into a course-shaped repo without pretending you already have a polished content system.
Publish one small lesson publicly so you can test clarity and interest before thinking about monetization.
The goal is first proof, not an early platform decision. Self-host and hosted stay open after the format is clear.
- 1Start with one folder of Markdown notes instead of trying to migrate every draft you have.
- 2Copy the same course.yml + lessons/ shape into a small repo when you are ready for a believable test.
- 3Make one lesson free first so readers can judge the material before a paywall exists.
- 4Use the sample import or notes-first signup path to sanity-check structure before touching pricing.
- 5Only think about hosted vs self-host after one preview lesson is live and sharable.
Want the starter kit emailed to you?
If you are comparing options or want to forward the proof assets to a teammate, we can send the exact starter files and sample repo links to your inbox.
title: "Advanced Git for Engineers"
slug: advanced-git-for-engineers
description: "Turn real team Git habits into a structured mini-course."
price_cents: 2900
currency: usd
tags:
- git
- devtools
- engineering-management---
title: "Recover safely from a bad merge"
slug: recover-safely-from-a-bad-merge
order: 1
access: free
estimated_minutes: 12
quiz_id: recover-bad-merge
---
# Recover safely from a bad merge
Explain the workflow, add code blocks, and keep the repo versioned like normal.id: recover-bad-merge
title: Recover safely from a bad merge
questions:
- prompt: Which command keeps history intact while undoing a merge commit?
choices:
- git reset --hard
- git revert -m 1 <merge_sha>
- git checkout .
answer: git revert -m 1 <merge_sha>Use the sample repo flow to see a read-only outline, inspect the docs for the full schema, or create a free account and import the template immediately.
Copy the exact starter assets, then lint your files before signup
This is the low-risk path skeptical creators asked for: copy known-good snippets, paste your own content into the linter, and only sign up once the format feels real.
title: "Advanced Git for Engineers"
slug: advanced-git-for-engineers
description: "Turn real team Git habits into a structured mini-course."
price_cents: 2900
currency: usd
tags:
- git
- devtools
- engineering-management---
title: "Recover safely from a bad merge"
slug: recover-safely-from-a-bad-merge
order: 1
access: free
estimated_minutes: 12
quiz_id: recover-bad-merge
---
# Recover safely from a bad merge
Explain the workflow, add code blocks, and keep the repo versioned like normal.id: recover-bad-merge
title: Recover safely from a bad merge
questions:
- prompt: Which command keeps history intact while undoing a merge commit?
choices:
- git reset --hard
- git revert -m 1 <merge_sha>
- git checkout .
answer: git revert -m 1 <merge_sha>