Bastian Allgeier, creator of the popular CMS Kirby, talks with us about what Kirby is, why Kirby uses flat files, the whole SSG vs flat debate, the $20B Sigma shaped elephant in the room, running Kirby on the edge, how Kirby handles support and licensing, and what kinds of sites use Kirby?
Time Jump Links
- 00:56 Guest introduction
- 02:15 What is Kirby?
- 07:37 Why flat files?
- 10:41 SSG vs Flat File
- 14:33 The $20B elephant in the room
- 18:16 Any plans to run Kirby on edge computing
- 20:07 PHP and Caching
- 23:22 Any hardware spec requirements for Kirby?
- 26:18 Sponsor: Split Software
- 28:01 What are people using Kirby for?
- 34:39 What is in a flat file system?
- 41:38 Example of setting up a blog post
- 46:38 How is the GitHub integration?
- 49:59 How do handle support and licensing?
- 53:13 How should people pitch Kirby?
- 55:12 Shared elements API
Episode Sponsors 🧡
What if a release was exactly how it sounds? A liberation from constraint. A moment of relief. An escape from outdated processes, tedious software changes, and the slow, painful deployments that hold back product engineers.
Free your teams (and your features) with Split.
By attaching insightful data to feature flags, Split helps you quickly deploy, measure, and learn the impact of every feature you release. Which means you can turn up what works, turn off what doesn’t, and give software innovation the room to run wild.
Now you can safely deliver features up to 50 times faster and exhale. Split Feature Management & Experimentation. What a Release.
To reimagine software delivery and propel your teams forward, start your free trial at split.io/shoptalk