CMS / Content
Markdown / MDX
Write content in files in your repo — commit as docs.
Monthly cost
Free
Popularity
4/5
LLM knowledge
5/5
Difficulty
Easy
#open-source#low-cost
What Markdown / MDX is good at
Strengths
- +Git-tracked content
- +Zero CMS cost
- +Great for dev audiences
Tradeoffs
- −Not for non-technical authors
- −Manual media handling
Coding-agent prompt
Drop into Claude / Cursor to get idiomatic Markdown / MDX code.
You're working with Markdown / MDX. Write content in files in your repo — commit as docs. Best practices: - Lean on: git-tracked content - Lean on: zero cms cost - Lean on: great for dev audiences Things to watch for: - Watch out for: not for non-technical authors - Watch out for: manual media handling General guidance: - Follow the official docs — don't invent APIs. - Keep secrets in environment variables, never commit them. - Write TypeScript where the ecosystem supports it; add types to every exported function. - Add tests for the critical paths before declaring the task done. - Read-the-docs is usually faster than guessing — cite the docs page in code comments when you apply a non-obvious pattern.
Beginner's guide to Markdown / MDX
In one line: Write your content in plain text files inside your repo.
Markdown is a simple text format — `# Heading` and `**bold**`. MDX lets you embed React components inside markdown. Content lives alongside your code, versioned in git. Great for docs and dev-facing sites.
Browse all categories