Pages CMS

Pages CMS is an Open Source Content Management System for GitHub. It is particularly well suited for static site generators (e.g. Jekyll, Next.js, VuePress, Hugo).

It offers a user-friendly interface to edit the content of your website or app directly on GitHub.

Watch the demo ▶

Documentation

Go to pagescms.org/docs.

Community chat

Join the Discord server to get help with Pages CMS, share feedback, and connect with other users building with the platform.

Built with

• Next.js
• Tailwind CSS
• shadcn/ui
• drizzle
• Vercel
• Turso
• Resend

Use online

The easiest way to get started is to use the online version of Pages CMS. You'll be able to log in with your GitHub account and get the latest version of Pages CMS.

This online version is identical to what's in this repo, but you can also install your own version locally or deploy it (for free) on Vercel following the steps below.

Install and Deploy

Create a GitHub App

Whether you're installing Pages CMS locally or deploying it online, you will need a GitHub App.

You can either create it under your personal account (https://github.com/settings/apps) or under one of your organizations (https://github.com/organizations//settings/apps).

You will need to fill in the following information:

• GitHub App name: use "Pages CMS" or whatever you think is appropriate (e.g. "Pages CMS (dev)").
• Homepage URL: whatever you want, https://pagescms.org will do.
• Identifying and authorizing users:
  • Callback URL: the URL for /api/auth/github:
    • http://localhost:3000/api/auth/github for development,
    • something like https://my-vercel-url.vercel.app/api/auth/github (or whatever custom domain you're using) if you're deploying on Vercel.
  • Expire user authorization tokens: no.
  • Request user authorization (OAuth) during installation: yes.
  • Enable Device Flow: no.
• Post installation:
  • Setup URL (optional): leave empty.
  • Redirect on update: no.
• Webhook:
  • Active: yes.
  • Webhook URL: the (public) URL for /api/webhook/github:
    • for development, you'll need to use something like ngrok. You'll end up with something like https://your-unique-subdomain.ngrok-free.app/api/webhook/github.
    • something like https://my-vercel-url.vercel.app/api/webhook/github (or whatever custom domain you're using) if you're deploying on Vercel.
  • Secret: generate a random string (for example with openssl rand -base64 32 on MacOS/Linux)
• Permissions:
  • Repository permissions:
    • Administration: Read & Write
    • Contents: Read & Write
    • Metadata: Read only
  • Organization permissions: nothing.
  • Account permissions: nothing.
• Subscribe to events:
  • Installation target
  • Repository
  • Push
  • Delete
• Where can this GitHub App be installed?: you'll want to select "Any account" unless you intend to only use Pages CMS on the account this GitHub App is created under.

Environment variables

Local development

We assume you've already created the GitHub App and have a running tunnel for the GitHub App Webhook (using ngrok for example):

1. Install the dependencies: npm install
2. Update your environment variables: copy .env.example to .env and fill in the values according to your setting (see section above).
3. Create the database: npm run db:migrate
4. Run it: npm run dev

Deploy on Vercel

1. Create a SQLite database: I recommend using Turso, because it's free (and pretty awesome)

2. Deploy to Vercel: at this stage you have 2 choices:

   1. Create a fork: fork the pages-cms/pages-cms repo in your account and deploy that fork. This will allow you to get updates. Make sure you define all of the environment variables listed above.

   2. Use the deploy button:

      

3. Update your GitHub OAuth app: you'll probably need to go back to your GitHub App settings to update some of the settings once you have the Vercel URL (e.g. "Callback URL" and "Webhook URL").

Self-host

There are plenty of other options: Fly.io, Digital Ocean, Render, SST, etc.

License

Everything in this repo is released under the MIT License.