Going No Build

Over the last few years I've experimented with various different systems and tooling to run this tiny site.

As a constant tinkerer, I like to try new CMSs, frameworks and methodologies but never really found one that I truly enjoyed.

Out of the above, I probably liked WordPress the least but that was because I've built countless sites using it at work (and still do) and with any personal project you want to try new things, right? The beauty of using WordPress was that I knew how to achieve most things I wanted without too much trouble. Most functionality was only a Stack Overflow search away (or ChatGPT these days)

Kirby is a CMS that I have never used for commercial work but I bought myself a license a while ago and used it to power my site. I liked how it didn't use a database and your content was committed to the repository rather than being stored in a database like WordPress. Being able to work on different branches and then push to live when I was happy was a nice feature to have coming from WordPress.

I then moved on to Laravel as we were doing a lot of projects at work at the time using Filament as a framework for admin areas and it seemed like a good fit. I enjoyed building the site with Laravel as it meant the possibilities were endless but with all that freedom came a bit of paralysis when it came to making changes or even just adding content. I was constantly trying to invent new features and it came to the point where I spent more time tinkering with how the site worked rather creating content for the site. It's flexibility made me feel stifled.

Kirby had the right balance between a static site and something content managed. It was a CMS but no database.