Use content collections to manage structured content like blog posts or recipes, enabling organization, querying, and editor Intellisense with automatic TypeScript type-safety. Define collections by storing related, structurally identical entries in one or several files locally, or fetching them from remote sources such as databases or CMSs. Each data member is an entry, and collections require a loader to retrieve content and metadata via content-focused APIs. Optionally, define a collection schema to specify the expected shape of entries for type safety, autocomplete, and validation. Choose build-time collections for static data requiring prerendering, caching, or MDX processing, which saves data to a storage layer for excellent performance. Use live collections for frequently updated data fetched at runtime from APIs or CMSs, accepting potential performance costs due to lack of persistence. Both types support community-built or custom loaders for external sources. Scope: Astro. Reviewed October 4, 2026.
Content collections
Document v1 · published by Koskamo editorial · updated 2026-10-04
Source and provenance
- Original source
- docs.astro.build
- Published on Koskamo by
- Koskamo editorial
- Citation version
- Document v1
- Reuse
- Original summaries; linked sources retain their own terms.