Folio blog: Docs as code
Markdown in Git, Mermaid and docs that live next to the code.
Posts tagged Docs as code
LLM wiki for a team: Markdown in Git, readable by agents over MCP
Karpathy's LLM wiki is a folder of Markdown that an agent maintains. It suits one person; a team needs rights, shared editing, history and review. Where the pattern breaks, and what Folio gives an agent over MCP and what it leaves to you.
- AI & MCP
- Docs as code
Mermaid vs PlantUML: which to use for docs in Git
Both draw diagrams from text. Mermaid runs in a browser and renders on GitHub, GitLab and in Obsidian; PlantUML covers more UML types but needs Java. A table of syntax, types, rendering, support and licenses, with sources, and where each fits.
- Comparisons
- Docs as code
Export Confluence to Markdown and keep it in Git
Confluence exports Word, PDF, HTML, XML and CSV, not Markdown. Five ways to get Markdown files in Git, how to keep the page tree, what each loses on the way, and a checklist for a trial run.
- Confluence
- Docs as code
- How-to
Mermaid diagrams in a team wiki: keep them as code
A diagram stored as Mermaid code changes in the same edit as the page, shows in the diff and renders on GitHub. Three examples with real code (flowchart, sequence, ER), how Folio draws and edits them, and what the free live editor does.
- Docs as code
- How-to
Docs-as-code without the IDE: edit your repository's docs in a browser
The docs stay Markdown in your product's Git repository and a technical writer edits them in a browser, by hand, with Folio AI or through an agent over MCP. How the Git sync works, and where it stops.
- Docs as code
- How-to