Welcome to docs.dev
Documentation that reads like a designed page — in a repo you own, on infrastructure you control.
docs.dev is a documentation platform built on a bet most docs tools won't make: you should own everything. Your docs live in your GitHub repository, your site runs on your Cloudflare account, and if you stop using docs.dev tomorrow, your site keeps working. What we add on top is the part you actually want from a docs product: a beautiful reading experience, an editor your whole team can use, and sign-in that stays out of your way.
What makes it different
A reading experience, not a wall of blocks. Prose flows around figures, code, and shapes — like the paragraph you are reading right now — powered by the pretext layout engine. Every run of text is measured with canvas arithmetic and placed as real, selectable, indexable DOM text on both sides of a figure at once, which CSS floats and CSS Shapes cannot express. Resize the window and the words re-measure and re-break against the live column width. See it live on the home page.
- Your repo is the source of truth. Every page is an MDX file. Publishing from the editor is a git commit. Your history, your pull requests, your rollbacks.
- Your infrastructure. One click deploys to your Cloudflare account with CI wired up. AI features run on Workers AI — also yours. There is no hosting bill from us and no lock-in to escape later.
- Built for agents. The repo ships a
CLAUDE.mdand skills, so pointing Claude Code at your docs works on day one: "add a quickstart page" is a one-line request.
Start here
Getting started
Deploy your docs site in one click and make your first edit.
Editing
The on-page editor, shared drafts, publishing, and editing with Claude Code.
AI writing & images
Generate docs and images on your own Cloudflare account — no API keys.
Team sign-in
Give your whole team access with docs.dev accounts and roles.
How it fits together
Your site is a Next.js app (Fumadocs + the pretext engine) deployed to Cloudflare Workers from your own repository. Everything the editor does — sign-in, drafts, publishing, AI generation — goes through your site's own same-origin API, documented in the API reference. The optional docs.dev service adds one thing: team sign-in, so editors authenticate with their docs.dev account instead of shared credentials. It's a sign-in check, not a dependency — your published site never needs us to serve a single page.