Show HN: Pages CMS – A CMS for GitHub

In a nutshell: 1. You log in with your GitHub account. 2. You select the GitHub repo where your site/app is at (whether it's Next.js, 11ty, Hugo, Nuxt... as long as you're using flat files for content). 3. You add a single config file to your repo to define the content types and other settings (e.g. media folder). 4. Congrats: you now have a user friendly CMS to manage content + media BUT all changes are still tracked like regular commits (under your account) on GitHub. I started using Jekyll around 2009 and over the course of the past 10+ years, I've helped build major sites and tiny blogs with Hugo, Gatsby, Next.js and more recently 11ty. I still love it. BUT once you're done building, managing content and media can be a bit of a pain. You have a few options: - Edit files directly (on GitHub or your local). Good luck getting your colleagues on the marketing team to do that. - Hook up a headless CMS like Contentful, Sanity, or Strapi. That works, but it's