🚀 “I want to publish something”
A website, a blog, a page on the web. The roadmap starts at the syntax and has you live by step ②, today. Prefer working straight through? The tutorial series goes from zero to a published site.
The Way of Markdown
Own the source. Compose with anything.
Websites, knowledge bases, blogs, even a Notion replacement — built from plain text files you own, with tools you can swap anytime. Markdown is quietly everywhere; here's the way to make it work for you.
Markdown source and rendered output
notes/reading-list.md — plain text, yours forever
# My reading listBooks I **actually** finished:
| Book | Year | Done |
|------|------|------|
| The Dispossessed | 1974 | ☐ |
| File over app | 2023 | ☑ |
```mermaid
graph LR
A[write] –> B[store] –> C[publish]
```
> Plain text never goes out of fashion.
Tables, task lists, diagrams — all still plain text. That's the whole trick, and it goes remarkably far.
Why markdown wins
The whole syntax takes ten minutes to learn, and then it's yours: plain files on your disk, still readable in fifty years, which is more than your .docx files can promise (the history is instructive here). The rest of the world has quietly agreed. Every AI speaks markdown, most of the apps you already use handle it, and you can put diagrams, databases and whole tools inside three backticks.
📝 “I want better notes”
A knowledge base, a second brain, published later or never. Start the same way, then build a catalog of anything and read the pattern behind it.
Never touched markdown? The basics take ten minutes, or try it live right now. Onboarding a team? The step-by-step path sequences the whole thing with checkpoints. Already fluent — go poke around the reference shelf, the videos, the canon or the blog.
