The post-field contract lives in src/content.config.ts. Astro Content Collections parse frontmatter during the build and validate types, dates, and allowed values.

Schema and Fields

// Posts Collection (src/content/posts)
const posts = defineCollection({
  loader: glob({ pattern: "**/*.{md,mdx}", base: "./src/content/posts" }),
  schema: () => z.object({
    title: z.string(),
    published: z.coerce.date(),
    series: z.string().optional().default(""),
    seriesOrder: z.number().int().optional(),
    draft: z.boolean().default(false),
  }),
});

// Series Collection (src/content/series)
const series = defineCollection({
  loader: glob({ pattern: "**/*.md", base: "./src/content/series" }),
  schema: () => z.object({
    title: z.string(),
    status: z.enum(["ongoing", "completed"]).optional().default("ongoing"),
    defaultCategory: z.string().optional().default(""),
  }),
});

The source schema is authoritative; see Frontmatter for the field reference. Unknown fields cannot safely be consumed by components.

Extending Fields

1. Add a field with the right default or optionality.
2. Update src/types/ and every consumer.
3. Update Frontmatter documentation and examples.
4. Run npx astro check, pnpm type-check, and pnpm build.

Follow the project's date convention instead of mixing strings and Date values. Production collection queries exclude draft: true; an encrypted: true post must also have a non-empty password.

Copyright

Copyright Ownership:matsuzaka-yuki

License under:Attribution 4.0 International (CC-BY-4.0)

Contributors: matsuzaka-yuki, Dawn6666666

Previous pagePermalinks

Next pageEncryption (Optional)