What problem does it solve? Managing markdown-based content in TypeScript projects often means writing ad-hoc parsing code with no type safety or validation. This Skill guides you through setting up Content Collections so your blog posts, docs, and other content files become fully typed, validated data collections. ## Core Features & Use Cases - Type-Safe Collections: Define collections with Zod schemas and get full TypeScript inference for every document, including frontmatter fields and metadata. - Markdown Transformation: Compile markdown to HTML with remark/rehype plugins, and add computed fields like reading time or slugs during transformation. - Multiple & Joined Collections: Manage posts, docs, and authors as separate collections and join related documents (e.g., resolving an author reference inside a post). - Use Case: Build a blog in TanStack Start where each markdown post is validated at build time, sorted by date in a route loader, and rendered as HTML on individual post pages. ## Quick Start Set up Content Collections in my TanStack Start project with a posts collection that validates title, published date, and tags from markdown frontmatter.
