Provider docs
Each provider uses the same scan model: fetch CMS documents, normalize stable IDs and route fields, resolve paths, and run checks against a running site.
Supported providers
Use Prismic when document types have UIDs or route resolver URLs that map cleanly to Next.js routes.
Read PrismicUse Strapi when collections and single types drive pages, layouts, or locale-specific content.
Read StrapiUse Directus when explicit collections hold route fields, SEO fields, and catalog content.
Read DirectusUse Payload when collections live in the same Next.js app and expose route, SEO, and media fields over the REST API.
Read PayloadUse WordPress when REST API pages, posts, or custom endpoints map to a Next.js frontend.
Read WordPressUse Contentful when content types expose slug-like fields and a delivery token can read entries.
Read ContentfulUse Sanity when document types expose slug fields and can be queried through the HTTP Query API.
Read Sanity