Pages CMS screenshot thumbnail

Pages CMS

Editors can update a static website without learning Git, because Pages CMS puts a visual editor on top of the repository itself. A single .pages.yml file defines what is editable: collections of Markdown files that share a schema, standalone files such as site settings, and nested groups that organize the sidebar. Fields cover strings, rich text, code, dates, numbers, booleans, selects, images, files, references, objects, and repeatable blocks, with front matter stored as YAML, JSON, or TOML. Plain text files like robots.txt open in a raw editor, redirect files in a code editor, and CSV files as an editable datagrid. Collection lists can be searched, sorted, and shown flat or as a folder tree. The media manager supports drag-and-drop uploads, multi-file selection, allowed extensions, and safe or random renaming. People without GitHub accounts join through email invitations and edit content and media, with their saves committed through the GitHub App. Custom action buttons dispatch GitHub Actions workflows after a confirmation dialog or input form, so one click can rebuild a preview or deploy the site. Commit message templates and a choice of app or user commit identity shape how each save appears in Git history. The responsive interface works on mobile screens, and suits Jekyll, Hugo, Astro, Next.js, Eleventy, VuePress, and similar site generators. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy