Pages CMS 2.1.7 was just released! But this account will be deactivated. I just don't have the bandwidth to deal with multiple X accounts for each of my open source projects. Follow me directly at @hunvreus

Pages CMS 2.1.x is here, along with Actions. You can now trigger GitHub Actions right from the UI. This opens up a lot of possibilities for teams that need to implement more complex workflows. github.com/pagescms/pagescms…

Just got @pagescms 2.1.0 out. The main thing is GitHub Actions support. You can now add custom buttons across the interface to trigger GitHub Actions workflows.

New version is out: 2.0.1. Lots of bug fixes from v2.0.0, improved performance for the webhook/cache, and additional helpers for users who migrate from older version. More info at: github.com/pages-cms/pages-c…

Launching @pagescms 2.0.0 tomorrow. I'm also almost done with @devpush 1.0.0 (running on kubernetes) and @basecoatui 1.0.0. Hoping to be done by next week and step away from open source work for a little while. I can finally lock in on AI.

I avoid using a database at all cost. At least in small projects, when longevity and cost is more important than user-generated data. Examples? Blogs, brand websites, directories, etc. Thanks to this approach, demo bioinformatics tools I've created 7 years ago are still up at my previous employer's website. I've used static files to replicate the API structure for a limited sample of data, making it possible to host a limited version of the app for close to $0. Today I'm using static files for directory project I use to get up to speed with building products - airportregistry. But how to manage static data? For me, the tool of choice is Pages CMS @pagescms. It's an open-source, 100% free editor that uses your Git repository to store your content in markdown. In fact, integrating it with my website required no code change, because I was already using markdown with frontmatter (extra metadata) for my posts. You can specify custom fields, upload files, manage on-off schemas for specific pages like a home page. Every update creates a commit, which in turn deploys a new version of my app. Highly recommend giving Pages CMS a go. It's a simple but delightful project. If this is not what you need, give a thought to what can be static and pre-fetched in your project, it can make a difference both for your wallet and for experience of your users.

Pages CMS was down for a couple of hours, due to an outage from Turso. It is now back up and running on @supabase. If you are running you are self-hosting Pages CMS, make sure to check the upcoming version with the new install steps.

Pages CMS 1.0.0 is finally (officially) out and it's running on @nextjs (App Router). Thanks to @vercel, @tursodatabase, @DrizzleORM, @resend and @shadcn (for the UI).

I just published How to Use and Configure @pagescms with Next.js Applications. medium.com/frontendweb/how-t… #nextjs #reactjs #cms #pagescms

Pages CMS 0.4.0 is out, and with it a completely rethought fields system which allows for custom fields. github.com/pages-cms/pages-c…

Pages CMS 0.3.0 is out. Lots of improvements including: revamped settings management, improved image support, full support for TOM/JSON/YAML files, support for content with no fields, support for date in filename... github.com/pages-cms/pages-c…