Staleless
A git-backed documentation platform that tells you which pages no longer match your product.
Documentation that cannot go stale without saying so
Section titled “Documentation that cannot go stale without saying so”Your Markdown stays in your own git repository. Staleless gives your writers a block editor over it, an MCP server so an agent can draft and commit while a person reviews the diff, and a published site built from the same content.
Start herePick your way in
Section titled “Pick your way in”Blocks, snippets, variables, assets, and the review flow. Start with Pages.
🚀 I am setting this upConnect a repository, write a page, publish it, connect your domain.
🤖 I am pointing an agent at itFourteen MCP tools in three scopes. An agent drafts and commits; a person publishes.
🛠️ I am wiring it into CIFive commands. lint needs no token and no network, so it works from a fork.
The operating model
Section titled “The operating model”- Draft changes on a branch.
- Review the rendered preview and the source diff.
- Commit the approved change.
- Merge it into the main documentation branch.
- Publish main for readers.
Tip
A commit or a merge is not automatically a public release. Publishing is a separate action a person takes.
What is different here
Section titled “What is different here”Every other documentation tool treats staleness as your problem. Pulse measures it: it reads your pages, your code and your OpenAPI documents, then names the pages that describe something which has changed.
| Signal | Reaches |
|---|---|
| Evidence — a dead link, a removed endpoint, a missing asset | outdated |
| Suspicion — an overdue review, no owner | review |
Age is never evidence. A five-year-old page that is still correct is still correct, and a tool that calls it stale teaches people to ignore the indicator.
The same rules run in your build, so broken documentation fails a pull request instead of reaching a reader.
The rest of it
Section titled “The rest of it”Pages, frontmatter, navigation and redirects.
📤 PublishingMerging, previews, versions, rollback and history.
📡 Staying currentPulse, review schedules, health, the inbox and code impact.
🎨 Site managementTheme, domains, private sites, search, Ask and analytics.
👥 Teams and securityRoles, members, single sign-on, the audit log, privacy and export.
💳 Billing and plansFour tiers, every limit, and what each claim is worth.
🔌 API and integrationsThe content API, tokens, GitHub, Slack, webhooks and OpenAPI.
🧯 TroubleshootingWhen a build, a certificate or a token does not behave.
Two things worth reading early
Section titled “Two things worth reading early”- Concepts — workspace, project, page, branch, publish. Every word the rest of the documentation depends on.
- Lint rules — all 28 rules and their severity. It is what refuses a commit.