Docsbook documentation: publish, get cited, measure
Every capability page here follows one rule: it states what you get, how it is built in enough mechanical detail to predict the output, the evidence with a link to a primary source, and what is not proven. If we cannot source a claim, the page says so rather than dropping it — see how we prove it.
New to Docsbook? Read the overview first, then publish a site.
What Docsbook does with your repository, and what it costs
Publish a documentation site, from source to public URL
Workspace, project balance, indexing and the other terms
The jobs teams hire documentation for
The evidence rule every capability page here follows
Step-by-step, no prior GitHub experience assumed
Settings, reindexing, and who can read the site
An "Edit on GitHub" link on every page, and where repository sync is set up
Which folders and files become pages
One CNAME, SSL provisioned automatically
Shared password, or your own SSO identity provider
Name, icon, accent colour, fonts
Light, dark and system defaults
What Docsbook emits for search engines without you configuring anything
Title, description, canonical, hreflang, cards, robots and sitemap, in resolution order
How a change reaches the index, and what actually gates that
What Docsbook adds so Perplexity, ChatGPT Search and AI Overviews can quote you
The rules that make a passage quotable, and what has been measured not to work
A plain-text index of your docs for AI clients, and who really reads it
What an answer engine needs from a page, and what Docsbook emits
The JSON-LD Docsbook emits, what triggers it, and what Google still shows
The rules Docsbook writes by, each with what it does to an answering agent
Documentation an agent can navigate and act on, not just read
SKILL.md files that teach any agent documentation work
The tools that let an agent read and edit your docs
The document graph an agent navigates
Auth model, what a read-only token cannot do, and what is not offered yet
An assistant that answers from your indexed pages
The retrieval and grounding pipeline, and what happens when nothing matches
A search box in the header, the sidebar, or both
Repositories and sites your agent may read as fact
Run your own code before and after the model
Thumbs up and down, per page
What Docsbook measures and where it comes from
Visitor identity, bot filtering, read time, and what is never collected
Whether readers reach the page that sells
AI opens, code copies, link clicks, goals
How long readers spend on each page
Where readers are and what they read in
What AI work drew on the project balance
Enable languages and place the switcher
How automatic translation works, and how to correct it
What is protected from translation, how drift is caught, and the hreflang side
What is metered, and what a project balance pays for
Cost, cancellation, sync, privacy and data ownership
Every reference page in one list
Every tool, its parameters and its price class
Call your docs chat from your own backend
Event catalogue, payload schemas, signature format
Cards, accordions, steps and CTA blocks in Markdown
What shipped, and what each change was meant to buy
Longer pieces on AI search, docs SEO, analytics and platform comparisons
Support#
Email support@docsbook.io, or ask in the Docsbook Discord.
Paste a repository, a website URL, or a sentence about your product. The draft is generated before you sign in.