Great documentation isn't written once — it's continuously improved. This guide gives you a repeatable system for raising quality across your docs using Doxbrix'...
Great documentation isn't written once — it's continuously improved. This guide gives you a repeatable system for raising quality across your docs using Doxbrix'...
Great documentation isn't written once — it's continuously improved. This guide gives you a repeatable system for raising quality across your docs using Doxbrix's AI scans, reader feedback, and analytics. Instead of guessing what to fix, you'll work from objective signals and let AI do much of the heavy lifting.
Who this is for
Anyone responsible for the quality of a documentation site who wants a concrete, data-driven process for improving it.
The quality loop
Step 1 — Measure where you stand
Open Docs Health (/health) for your project's overall health and prioritized issues. Three signals together tell you what to fix:
| Signal | Source | Tells you |
|---|---|---|
| Quality scores | [Scan with AI](/ai/scan-and-content-quality) | Which pages are weak and why. |
| Reader feedback | [Feedback widgets](/reader/feedback-widgets) | Which pages readers find unhelpful. |
| Analytics | [Analytics](/manage/analytics) | Which pages matter (traffic) and what's missing (missing pages, unresolved questions). |
Step 2 — Prioritize for impact
The highest-impact work sits where high traffic meets low quality:
Cross-reference top pages in analytics with low scores in Docs Health.
Review the Missing pages report and the Unresolved questions queue — readers are telling you what to write.
Fix high-traffic weak pages first, then fill the biggest gaps.
Step 3 — Fix with AI
For each page, use the insights panel to drive fixes:
Click the Quality badge to see the score, dimension breakdown, and prioritized findings.
Work down the list — they're ordered by impact (a missing intro, a skipped heading, a thin meta description).
Click Improve with AI in the page header to rewrite the whole draft, or use its caret to target one area (Readability, Structure, SEO, Accessibility, Completeness).
Missing an example or section? Use the /ai palette to draft it.
The badge re-scores as you edit — aim for Excellent (88+).
Step 4 — Verify and track
The overall health score in Docs Health and the This week rail show whether your fixes are moving the needle, and reader helpfulness should rise on the pages you improved.
Step 5 — Automate the upkeep
Once your docs are in good shape, keep them there with the AI agent: a weekly QA audit surfaces pages that slip, and a monthly Freshness task flags overdue pages. See Automate authoring with the AI agent.
Set a quality bar
- Aim for an Excellent rating before publishing.
- In CI, run
dxb lint --strict(blocks broken docs) anddxb quality --min 70to surface pages below your bar. See Search & quality. - Bake conventions into your Workspace AI policy so AI edits stay on-style.