I built **cms-lab**, an open-source CLI for checking CMS-backed Next.js sites before deploy.
The Directus use case is the failure mode where content exists in Directus, but the rendered app still breaks because a slug is missing, route mapping drifted, an expected page returns 404/500, SEO fields are incomplete, or image alt text is missing.
Basic flow:
```sh
npx cms-lab init
npx cms-lab doctor
npx cms-lab scan --ci --report
```
It can map Directus items to the URLs your Next.js app expects, probe a local or staging app, and produce terminal, JSON, Markdown, JUnit, and local HTML report output.
GitHub: GitHub - i-afaqrashid/cms-lab: Catch CMS bugs before deploy. · GitHub
Docs: Scan Command | cms-lab
npm package: `cms-lab`
I’d be interested in feedback from Directus users on route conventions, collection/field patterns, and checks that would catch real deployment issues.