Wow. To be honest. The best CMS ever, even for non-technical skilled person. I'm a designer, not a developer but I manage to switch years ago this photographic magazine from WP to Kirby and never had an issue. The support on the forum is also amazing. Well done Kirby team!
Thank you very much for the kind feedback Fabio!
I see a lot of upvotes both here and producthunt.
Can anyone share experiences while migrating from other sources or different cms to Kirby? And what does it have to offer to the design community?
I know I know: "just google it man". I did but I would like to know more about it.
For me, the fact that it is "flat-file" means I don't have to worry about porting a database around. Using Laravel Valet I can have a local dev environment up in no time. With Laravel Mix I can leverage a streamlined Webpack asset compilation for JS and CSS/Sass/PostCSS and it takes the fuss out of the painful areas of building on a CMS.
Also between Kirby's Guide and Cookbook and their Starterkit, it is very easy to get up and running and start building layouts and the kind of content you want to create throughout various areas of the site.
Kirby's paradigms are simple and straightforward. As a designer all of these things remove barriers for me in being able to design the kind of experience I want for projects.
A lot to these reasons also apply to another excellent flat file CMS, Statamic. I'd argue that of the two, Statamic is better.
I love me some Statamic. There are lots of great CMS options these days.
Can you explain why you think so?
One of the biggest reasons is the field sets Statamic comes with. A lot of CMSs underestimate the power and flexibility of letting developers tailor the content model each site uses. Statamic follows in the footsteps of Expression Engine and Craft CMS in this regard and in my opinion, this is a huge advantage.
We have tons of default fields that can be extended with custom field plugins: https://getkirby.com/docs/reference/panel/fields But we extend this even further with our section system. With this, you can set up the entire interface for each page type in the way that fits best. You can see this in action here: https://getkirby.com/docs/guide/blueprints/layout
I have been using it for years. It is just most straightforward clever zen experience there is. Bastian the creator used to be designer and it shows in all the decisions. It is not overengineered. It's transparent - most importantly to me it is very clear to understand what is going on. It is especially fast if you are doing custom design all the way. I run my life on Kirby.
Hell i even use kirby for my internal invoicing. You can just throw at it anything and it will hold up.
I have tried all the Wordpreses, Drupals, Bolts, Crafts, Statamics of the world and everything is just a littlebit more hurdles.
Add to that fact that it has great support and it cost HALF of what most competition costs..
It feels like its some secret i don't know why more people are not using it.
Nice examples, especially your own shop. I've just glanced over the Kirby docs, but presumably you could hook up or code a custom cart and checkout system to an virtual Kirby endpoint? Presumably now the /buy page is still Kirby and then just integrates with that 3rd party payment service?
There are many ways to solve this. You could create your own cart and order system with Kirby, but that would require quite some custom dev work. There are services like Snipcart that make this a lot easier though. For our own license shop, we use Paddle.
"Kirby’s Panel is powered by Vue. Use the full power of Vue or our Vue UI component kit to make the admin interface truly yours."
Woo Vue! That got my attention :)
For a second I thought it was great web design for the Kirby vacuum cleaner which I would have been totally ready for.
I'm a bit confused as to what kind of hosting would Kirby need, since it uses static files? Currently I'm using Now, but that only allows immutable deploys—so impossible to update files later.
Any kind of simple PHP hosting works. That can be a cheap shared hosting package or a VPS. You can find more about the requirements here: https://getkirby.com/docs/guide/installation#requirements I can't tell if it's working on Now. We haven't tried that yet. But you can also use it as a data source for static site generators, or use Kirby itself as static site generator. In this case you end up with static files and they can be hosted everywhere. But you still can make use of our powerful admin interface.
I've really enjoyed using Laravel Forge for hosting. It connects to a your DigitalOcean Droplet or AWS, is affordable, and a very scalable way to host sites, manage SSL, and so forth.
Looks nice, but it appears tied to its templating system which kind of kills its utility to me. I want a headless CMS that I can use to manage content for any templating system I want to switch it to.
One of the beautiful things about 3.0 is that you can use it as a headless CMS:
Instead of using Kirby's front-end templates, you can use it to generate a JSON API that can be consumed by a static front-end like Gatsby or Next.js.
Ohhhh I missed that part, very nice! Definitely going to look into it now.
This has been always possible with kirby.
Working with kirby is very much like if you were working with nosql db where every record by default is also URL/route endpoint (it does not have to be you can have all routing you want).
You don't have to output HTML. Kirby does not enforce templating engine so you can straight up output json on those routes.
But there might be even better ways
Make your own route endpoints https://getkirby.com/docs/guide/routing this is almost identical to how you do it in expressjs or slim
Content representations - https://getkirby.com/docs/guide/templates/content-representations - you might output multiple things at once. /calendar will be html page /calendar.json will be the same thing in json.
I've come across this before but have not tried it — yet. I think there is definitely a good segment of projects that could run on this, where a client or designer might want some editing capabilities, but the hassle of setting up (and esp. maintaining) something like WordPress is a pain. It's developer-friendly to see you can also install and update via composer; presumably hooking up your own templating engine could be possible via the API endpoints?
Since the CMS is file based I looked at the caching section and was wondering if, aside from the general cache timeout, Kirby does automatically purge updated pages from the cache? Experiences how this performs on scale without any additional lower level cache?
Yes, you can replace our template engine with your favorite one via a plugin.
Our page cache gets flushed automatically on updates via the panel. This performs really well as you can see on our own site. We got quite some traffic from being #1 product on product hunt and all sorts of other launch-related traffic spikes.
Kirby has three different default cache engines. It starts simple with a file cache, but you can also switch to APCU or Memcached. You can also create your own cache engine plugin – for example for something like Redis.