Documentation

Getting started with Lexington Themes

PagesCMS Integration

Overview

All themes include Astro Content Collections for Blog, Work, and Store.
To make editing easier for non-developers, each theme also ships with PagesCMS support via a single configuration file: .pages.yml.

This integration is fully optional — remove the .pages.yml file anytime if you prefer to edit Markdown directly. No extra dependencies or runtime code are required.

How It Works

  • Content Collections (Blog, Work, Store) are preconfigured with schemas for consistent content editing.
  • PagesCMS reads the .pages.yml file to generate a lightweight visual editor connected to your GitHub repo.
  • No lock-in: if you delete .pages.yml, everything continues to work with standard Markdown.

Example Configuration

Here’s a simplified snippet from .pages.yml:

content:
  - name: posts
    label: Blog
    type: collection
    path: src/content/posts
    fields:
      - { name: title, label: Title, type: string }
      - { name: pubDate, label: Publication Date, type: date }
      - { name: tags, label: Tags, type: list }

This config tells PagesCMS to expose the posts collection for editing inside the CMS.

Editing content

  1. Push your project to GitHub.
  2. Log in to PagesCMS.
  3. Connect your repository.
  4. Edit blog posts, work entries, or store products visually.

Removing CMS

Don’t need a CMS? Just delete the .pages.yml file — content collections will still work with Markdown as usual. There’s no extra code, no dependencies, and no runtime overhead.

Learn more

For full configuration options and advanced usage, see the official PagesCMS Documentation.

Getting Started