It is a flatfile PHP CMS for anyone wondering. Version 3 is admin rewrite in Vue.js
It is one of the best if you need smaller/medium size website or blog. Much nicer dev experience thany any worpress drupal bs. I think Tower git client website is made using kirby.
Been using Kirby almost exclusively for my clients and personal projects for at least a couple of years.
Was already super happy with the V2 and can't wait to start using the V3 since pretty much everything has been rewritten and there's a lot more flexibility available.
I'm also excited to see what the plugin developers will come up with. We've seen some pretty interesting creations during the beta period and things can only get better now that V3 is officially out.
Also need to mention that the Kirby Team is amazing, they all do their best to help everyone who's struggling and the Kirby Community is made of a bunch of fun people who are very passionate.
I've been developing websites and plugins with Kirby 2 for 3 years and have had a great experience with it. I find it great for building custom websites. Clients love the simplicity of the Panel too.
Kirby 3 is a huge step forward. Some of my favorite new features are:
- New Panel powered by Vue.js
- Panel tabs & sections
- Better plugin API
- Built-in REST API which allows it to be used as a headless CMS
Such a great, fast and easy to use system. I love it for many years and with version 3 it got event better. I mean, look at the many fantastic showcase examples as well to see which companies and who is using Kirby already.
I have followed Kirby since the very first post, when Bastian announced his new company launch in order to build Kirby.
I have always be impressed by the heart Bastian and now the team around him put in Kirby.
Having tested Kirby 3 a lot in the last weeks, I can confirm that the Kirby 3 version is just incredible. You can at the same time build your website and its admin interface.
This admin interface becomes then the best I have ever seen. You can taylor it to match exactly your needs or your customer needs.
My opinion is that to use Kirby with pleasure, you need to have a good understanding of OOPHP (oriented Object PHP). But it's only my opinion.
For advanced PHP developers it is, without any doubt, the best CMS available. And I like also a lot Drupal or October CMS, and I even appreciate and use WordPress, trying to forget this strange thing named Gutenberg!
We relaunched our company website in Kirby and have been really happy with it.
As a developer, it really hits the sweet spot between providing you with tools to create great webpages without forcing you into any particular modes of working.
Excited to kick the tires on Kirby3.
Just a comment in another post, it’s not just for small to medium sites, there is no reason why a large site can’t run this, it’s extraordinarily fast and immensely extendable.
Lastly, can’t say enough good things about the community!
Kirby is by far the most fun CMS I've ever worked with.
I’m really impressed by its unrivalled flexibility when it comes to managing content.
Everything about Kirby feels refined, functional and consistent. Congratulations to the whole team for the excellent work!
Absence of a database makes the development experience that much more enjoyable. Having all configuration in yaml files makes for a very fast setup of the backend and easy deployment. Having worked with Wordpress, Drupal and Craft, this one's by far my favourite CMS.
Btw why are the points about asking for votes or comments not part of the guidelines but only part of the FAQ?
The usual understanding for me is that guidelines should be read and followed, while FAQ provide additional information on topics that are asked a lot (password reset, what does XYZ mean, etc).
sctb is a moderator (kind of annoying that you have to google that) [1] and given their statement it indicates that "soliciting upvotes and booster comments" is disallowed/discouraged. Yet, that information is not part of the official HN guidelines [2] but is merely mentioned in the HN FAQ [3]. My point being, if telling your users about the HN post you created is disallowed, then why is it not part of the guidelines and merely hidden among the FAQ? Like I said, guidelines are to be read and followed, but I wouldn't expect from people to read the FAQ to find all the 'rules'.
Oh i understand now. Well it is obvious people don't understand it works like that. From outside it seems that it is perfectly normal to share products and updates HN. It seems to happen all the time often with authors or employees in the comments.
So what is prohibited is to share the direct link?
Obviously submitting links to one's own work isn't prohibited. It's encouraged!
What's not allowed are asking friends or teammates to upvote and/or post booster comments in the thread. Those are forms of gaming the system which the community here is not ok with.
People should upvote or comment on things that they personally ran across and found intellectually interesting, not because they or a friend have something to promote.
I posted this on Twitter and of course kindly asked our followers to upvote it if they like the new version. This is something I see on Twitter every day and I really wasn’t aware that it is not allowed to do. https://twitter.com/getkirby/status/1085873516132605952?s=20
You can also do a search for getkirby on Twitter: https://mobile.twitter.com/search?q=Getkirby to see that we got quite a few very positive reactions to the launch there as well.
There's 5 or so commenters that newly signed up just to comment on this story (new accounts appear in green, so it's easy to spot). That looks fairly suspiciously like they did that because the author asked people to sign up and boost this story, not because they happened to browse hackernews and saw something they like. You're case is not the problem.
I am one of the new members, although I visit HN almost daily. I am a very satisfied Kirby user, so instead of doing the "lurker" as usual, I decided to share my thoughts (:
Bastian is not a friend of mine. We have never met together. We have never spoken together. We have perhaps only exchanged some words by written in the last five years. And I have only spent something like 30 dollars with his company in the last five years. When I saw he was happy to be there, I decided by myself to share my opinion about Kirby3 here. I tried to be as honest as possible not waiting any reward of any sort. I was not thanked for my contribution here by Bastian or someone from his team. I am now 58 and I write code since I was 14, at the time of the first programmable calculators. Usually I don't write comments on this kind of forum because I prefer to invest my time building solutions. I only did this time because I think that Kirby3 and the team behind this solution are worth it. That's all! :-)
25 comments
[ 2.4 ms ] story [ 47.2 ms ] threadIt is one of the best if you need smaller/medium size website or blog. Much nicer dev experience thany any worpress drupal bs. I think Tower git client website is made using kirby.
It also introduces a new API for plugins allowing things that weren't possible in Kirby 2.
Was already super happy with the V2 and can't wait to start using the V3 since pretty much everything has been rewritten and there's a lot more flexibility available.
I'm also excited to see what the plugin developers will come up with. We've seen some pretty interesting creations during the beta period and things can only get better now that V3 is officially out.
Also need to mention that the Kirby Team is amazing, they all do their best to help everyone who's struggling and the Kirby Community is made of a bunch of fun people who are very passionate.
Kirby 3 is a huge step forward. Some of my favorite new features are:
- New Panel powered by Vue.js
- Panel tabs & sections
- Better plugin API
- Built-in REST API which allows it to be used as a headless CMS
- External data sources
- Asynchronous media API
- Better cache system
- Simpler language management
- an admin interface that developers can tailor to any content model
- possibility to really integrate database content, not only frontend but also so it is editable in the admin interface
- REST API to use Kirby as headless CMS
- invaluable feature: the amazingly friendly Kirby community
As a developer, it really hits the sweet spot between providing you with tools to create great webpages without forcing you into any particular modes of working.
Excited to kick the tires on Kirby3.
Just a comment in another post, it’s not just for small to medium sites, there is no reason why a large site can’t run this, it’s extraordinarily fast and immensely extendable.
Lastly, can’t say enough good things about the community!
I’m really impressed by its unrivalled flexibility when it comes to managing content. Everything about Kirby feels refined, functional and consistent. Congratulations to the whole team for the excellent work!
The usual understanding for me is that guidelines should be read and followed, while FAQ provide additional information on topics that are asked a lot (password reset, what does XYZ mean, etc).
[1] https://news.ycombinator.com/item?id=12073675
[2] https://news.ycombinator.com/newsguidelines.html
[3] https://news.ycombinator.com/newsfaq.html
So what is prohibited is to share the direct link?
What's not allowed are asking friends or teammates to upvote and/or post booster comments in the thread. Those are forms of gaming the system which the community here is not ok with.
People should upvote or comment on things that they personally ran across and found intellectually interesting, not because they or a friend have something to promote.
As I said in my comment, we love Kirby, I saw this post, and commented. Isn’t that how this is supposed to work?