Kirby

Kirby CMS uses plain .txt files for content. Since the bare .txt files should not be accessible with a browser, one normally uses a path matcher in Caddy and then denies requests based on a path, like so…

I’ve migrated daily.baty.net to Kirby CMS. It has been a static site managed by Tinderbox for a long time. I love Tinderbox, but now that baty.net is back on Hugo, I wanted a playground for learning more about Kirby, without moving the main blog back and forth between Hugo and Kirby. So, here we are.

One of the things that frustrated me about Kirby last year was handling code/template changes vs content changes. I complained about it here.

We’re back on Hugo for baty.net.

After yesterday’s Kirby->Hugo-Kirby debacle, I’ve been thinking about why I spend so much time farting around with and on my blog. Fair question, and one I don’t really have an answer to. I guess it’s my little place on the internet and I like to have the furniture arranged just so. But “just so” changes all the time, so I keep trying new configurations. It’s fun. Also useless, and nobody but me cares, but still.

Have you ever been so enamoured with plain-text-static-html publishing that you’re willing to burn down a month of implementing a blog using Kirby CMS in order to go back to using Emacs and Markdown and Hugo?

How I reimplemented my Daily Notes feature from my Tinderbox blog to baty.net in Kirby

⚠️ This blog is no longer running Kirby, but I left this here just in case.

The Kirby experiment has been fun, but I’m not sure I’ll finish anything useful.