Content and publishing · Edition No. 41 · 5 Oct 2026

hunvreus/pagescms

An editing screen for a website whose content lives in a git repository, so the repository stays the only copy.

← Content and publishingRead the whole edition →

3,930 stars · MIT at main/LICENSE, stock text, holder named: 'Copyright 2025 Ronan Berder' (no '(c)', a slight deviation from the stock header). · 2.1.8, '08 Jun' with no year, settled as 2026-06-08 by the ungh releases record and consistent with package.json on main; corroborated only weakly by a relative 'three months ago' elsewhere, which pins the year but not the day. · Track this in Scout

An editing screen for a website whose content lives in a git repository, so the repository stays the only copy.

▶Repo detailsthe review · specs · pros & cons · install

What it is

A small web application that signs in to your GitHub repository and shows the Markdown files and images in it as editable pages. Markdown is plain text with a few simple marks for headings and links. The files stay exactly where they were; this only edits them.

What it is good for. The situation where one person builds a site and a different person writes for it. The writer gets a form, not a code editor. It suits anyone whose site is already generated from files in a repository and who does not want to add a database and an admin system to make it editable.

Stars3,930
LicenceMIT at main/LICENSE, stock text, holder named: 'Copyright 2025 Ronan Berder' (no '(c)', a slight deviation from the stock header).
Latest2.1.8, '08 Jun' with no year, settled as 2026-06-08 by the ungh releases record and consistent with package.json on main; corroborated only weakly by a relative 'three months ago' elsewhere, which pins the year but not the day.
Good
  • Nothing new holds your content. The repository is still the only copy.
  • MIT licensed, with the holder named: Copyright 2025 Ronan Berder.
  • There is a hosted version run by the project, so you can see whether it suits you before installing anything.
Watch for
  • Self-hosting it is a real job, not a setting. It needs Node.js, PostgreSQL 16, Docker for the database, two secrets you generate by hand, and a GitHub App you register yourself before anything works at all.
  • No Node.js version is stated anywhere in the project, and there is no published package, so the only route is clone and build.
  • It has been renamed at least twice. pages-cms/pages-cms and pagescms/pagescms both lead here, and the project's own README still tells you to clone the old address. Code last landed on 23 June 2026, about three and a half months ago.
Similar repositories
Install
git clone https://github.com/hunvreus/pagescms.git
cd pagescms
docker run --name pagescms-db -e POSTGRES_USER=pagescms \
  -e POSTGRES_PASSWORD=pagescms -e POSTGRES_DB=pagescms \
  -p 5432:5432 -d postgres:16
npm install
# Create a file called .env.local containing:
#   DATABASE_URL=postgresql://pagescms:pagescms@localhost:5432/pagescms
#   BETTER_AUTH_SECRET=...
#   CRYPTO_KEY=...
# Generate each secret with: openssl rand -base64 32
npm run setup:github-app -- --base-url http://localhost:3000
npm run db:migrate
npm run dev
Screenshots
hunvreus/pagescms: GitHub preview cardhunvreus/pagescms: Screenshot 1

Get the next edition in your inbox

A dozen repositories, opened and checked. The licence read, the last release dated, and the ones that did not make it named with the reason. It is the half most lists leave out.

No tracking pixels. One click to leave. The archive stays free either way.

We use your address to send the edition and nothing else. Confirm by email, leave in one click. How we handle it.