Where to read Docsbook release notes for one feature
By section of the admin panel#
- Changes — What shipped in the Docsbook Changes tab, and when
- Issues — What shipped in the Docsbook issue tracker, and when
- MCP — What changed in the Docsbook MCP server, and when it shipped
- Sources — What changed in Docsbook Sources, and in which release
- Prompts — What changed in the Docsbook prompt library, and when
- Chat — What changed in the Docsbook AI Chat assistant, and when
- SEO & GEO — What changed in Docsbook SEO and GEO, and in which release
- Translations — What changed in Docsbook Translations, and in which release
- Feeds — What changed in Docsbook Feeds and webhooks, and when
By the outcome a release moves#
Twelve numbers, each with its own page. Better is stated on every page, because half of them go down.
| Outcome | Better is | Page |
|---|---|---|
| Support load — fewer questions reaching a human | down | Support load |
| Upkeep time — less time keeping the docs true | down | Upkeep time |
| Manual checks — fewer things somebody has to check by hand | down | Manual checks |
| AI spend — less money burnt on model calls | down | AI spend |
| Broken pages — fewer pages that are broken or unreachable | down | Broken pages |
| Time to answer — readers reaching an answer sooner | down | Time to answer |
| AI citations — more answers from assistants that cite you | up | AI citations |
| New markets — audiences the docs did not previously serve | up | New markets |
| Organic traffic — more readers arriving from search | up | Organic traffic |
| Conversion — more readers doing the thing the page was for | up | Conversion |
| First-visit bounce — fewer first visits ending in nothing | down | First-visit bounce |
| Repeat readers — more readers coming back | up | Repeat readers |
Related#
- Full Docsbook changelog — every release in one file, newest first
- Changelogs by outcome — the same releases, cut by the number they move