require-content-config

Why it matters

A content config defines collections and their schemas so Astro can type and validate content entries. Content files without defineCollection() lose those guarantees and allow invalid frontmatter to reach a build or production page.

See the difference

src/
  content/
    blog/
      first-post.md

import { defineCollection, z } from 'astro:content'

const blog = defineCollection({
  schema: z.object({
    title: z.string(),
  }),
})

export const collections = { blog }

Configure this check

Project audits are configured in doctor.config.ts:

export default {
  rules: {
    'astro-doctor/require-content-config': 'error',
  },
}

Use 'error', 'warn', or 'off'. The configuration guide covers presets and per-file overrides.

Keep exploring best practices

• prefer-class-listUse class:list directive for conditional or dynamic class names.
• no-process-envDisallow process.env in Astro files — use import.meta.env instead.
• prefer-content-collectionsPrefer Content Collections over Astro.glob() or import.meta.glob() for Markdown and MDX files.
• no-legacy-astro-7-experimental-flagsMigrate experimental configuration fields removed or stabilized in Astro 7.
• prefer-env-schemaDefine an Astro env schema for variables documented in .env.example.
• prefer-pnpmUse pnpm consistently and remove competing package-manager lockfiles.
• require-client-router-script-lifecycleInitialize scripts on astro:page-load when using ClientRouter.
• require-fetch-default-exportRequire a default export from Astro 7 advanced-routing entrypoints.

Browse every rule and project audit