Skip to main content
Astro Stack
Docs
Documentation navigation

Astro Stack documentation

Content

Add an Astro content collection and optionally configure Pages CMS.

On this page

Select a content setup

Choose markdown, mdx, or collections in the wizard when the project needs local written content. Each option creates src/content.config.ts and one starter entry in src/content/posts.

src/
├── content.config.ts
└── content/
    └── posts/
        └── getting-started.md

The MDX option creates getting-started.mdx instead and configures Astro’s official MDX integration. Markdown and Content Collections use a .md entry.

Add an entry

Create a file in src/content/posts with frontmatter followed by Markdown:

---
title: A new post
description: A short summary for readers.
---

# A new post

Write the post here.

The generated collection uses Astro’s glob() loader to find Markdown and MDX files in that directory. When using MDX, you may also include supported JSX-style components and JavaScript expressions.

Edit content with Pages CMS

Choose pages at the CMS prompt to generate a root .pages.yml and a repository-backed media directory at public/images. The CMS schema follows the content selected for the project:

  • Generic Markdown and Content Collections edit src/content/posts as .md files.
  • MDX uses .mdx files and a code editor for the body so component syntax and expressions remain intact.
  • Blog and Documentation use their built-in src/content/blog and src/content/docs collections.

Pages CMS adds no package dependency. Push the generated project to GitHub, then connect the repository at app.pagescms.org.

Build the reading experience

The content selection deliberately creates the collection and starter content, not a blog index or post-detail route. Add those pages in src/pages when you are ready to decide your URLs, listing design, and metadata.