Curated directory · ten tools
Tools that leave the truth where they found it.
A small, opinionated list of software that treats repository files as durable records and every interface as a view. Use a DIY workflow, an open-source tool, a hosted view, or a mix: all can operate on the same files, so the choice is per-tool and reversible. No repo.md product is required, and a third-party tool over your files can be repo-native too.
The repo.md family
These are ours. They are listed first and labeled plainly.
Ours · Shipped
RepoTodoTodos and plans as Markdown in a TODO/ directory, with CLI, dashboard, MCP, and SDK views.
The task files remain complete without the tool; progress and staleness are recomputed from files and git history.
Ours · Beta
FolderblogA blog whose Markdown folder renders into a site, feeds, and editorial views.
Posts stay readable in the repository while the publishing surfaces remain replaceable.
Ours · Exploring
SidequestA portfolio map rendered from REPO.md files across the projects you own.
The cross-repository map is a computed view; each repository keeps its own durable record.
Ours · Exploring
TinboxEmail history and campaigns kept in git, with delivery handled at the edge.
The archive stays in owned files even though sending remains an external service.
Elsewhere in the ecosystem
Independent projects that make the same architectural bet in content, releases, and documentation.
Independent
Decap CMSA Git-based CMS that gives editors a UI over content stored in a repository.
Its editor commits the same repository content that developers can edit directly, rather than moving content into a CMS database.
Independent
KeystaticA CMS interface for Markdown, Markdoc, JSON, and YAML in a local checkout or GitHub repository.
Keystatic has no content database: its local and GitHub modes edit codebase files that remain usable without the UI.
Independent
ChangesetsRelease intent and changelog copy captured as small Markdown files beside the code they describe.
Pending release decisions are reviewable Markdown, and the project explicitly advises against blocking contributions that do not need one.
Independent
MkDocsProject documentation written as regular Markdown and rendered into a completely static site.
The docs directory is the authored record; generated HTML belongs in a disposable build directory that its guide recommends ignoring in git.
Independent
DocusaurusA documentation and blog renderer whose project structure keeps Markdown and MDX beside the site code.
Its documented source tree keeps docs and posts as files, then converts those files into website pages.
Independent
HugoA static site generator that turns repository content, data, and templates into a publishable site.
Hugo documents content and templates as source directories and `public` as generated output, keeping the rendering boundary explicit.