Docs Troubleshooting
Quick Checks
Run checks from the repository root unless the command explicitly changes into
docs.Common Issues
Broken relative links
Broken relative links
Symptom: link checker reports missing files.Fix: Ensure links target valid Mintlify routes (
/path), keep routes aligned with docs/docs.json navigation, and remove stale paths after page rename or move.Missing page in navigation
Missing page in navigation
Markdown lint failures
Markdown lint failures
Symptom:
pnpm check:docs fails on format or heading rules.Fix: Follow linter output line-by-line, keep heading hierarchy and list formatting consistent, and prefer native Mintlify components over custom HTML blocks.Docs structure validation failure
Docs structure validation failure
Symptom:
pnpm docs:validate fails despite passing markdown lint.Fix: Check docs/docs.json tab/group/page mapping, confirm every routed page exists under docs/, and ensure each page exposes a title frontmatter field or top-level heading.Page loads with a Mintlify 500 error
Page loads with a Mintlify 500 error
Symptom: the route exists, but Mintlify shows
Page not found! and an unexpected error page.Fix: Reduce the page to standard Mintlify frontmatter (title, summary) plus supported Markdown or Mintlify components, then run pnpm docs:routecheck --base-url <preview-or-site-url> so you validate real route rendering instead of static checks only.PR Checklist
Smoke test real route rendering when debugging 500s
Run
pnpm docs:routecheck --base-url http://localhost:3000 against a local preview, or point it at the deployed docs host.Spot check key navigation paths
Confirm Docs Portal, FAQ, and Business of Agents are reachable.