Spring is here / Kirby 2.3.0 is here :)

Our poor blog must have felt pretty lonely in the last months. But instead of falling into hibernation, we have been super busy working on all kinds of exciting projects for you. Here's a little summary…

This is a companion discussion topic for the original entry at https://getkirby.com/blog/spring-is-here

Ohh finally! Thanks for all contributors :clap:

I was expecting about few features :innocent:

  1. Hooks > https://github.com/getkirby/kirby/pull/348
  2. User Permissions > https://github.com/getkirby/panel/issues/60

Great! Will love to try it out! :smiley:

Can you remove the double enter strokes in the post?

The conversion from Discourse didn’t work too well. I just fixed it.

1 Like

I know that there’s still quite some stuff missing. But we just had to wrap it up at some point. It’s all still on the list and we are already working on priorizing features for 2.4


Thank you all for the new version 2.3.0.

Congratulations to the increase of the team!

The beta 2 had looked very nice, so I am excited to use the final version soon (this weekend)…

1 Like

I love Kirby more and more :heart_eyes: sure, i’m a beginner but in the last months i have learned new things like the funcion from the Template’s and the Blueprints, and a LITTLE bit how the Page Models works, its very Cool Stuff! :slight_smile:

and i love the new Documentation Stuff Thanks @bastianallgeier,@lukasbestle and @texnixe. i will read the new Stuff Very Soon whit great interest (maybe in the summer holidays :yum: )

and i wanna to say welcome to you @fabianmichael :slight_smile: i think the next years whit you in the Kirby Team will be really Cool

Thanks for 2.3.0 Just amazing!!


Congratulations to the whole team it’s been fantastic to follow the beta and I can’t wait to start breaking projects apart so they work with 2.3!


I don’t understand, why in the ZIP file at https://getkirby.com/downloads the blueprint files are in the old PHP format, while at https://github.com/getkirby/starterkit/tree/master/site/blueprints the blueprint files are in the new YML format.

I’m sorry for that. The build process broke unnoticed and only replaced the kirby and panel folders correctly. The starterkit files stayed at the last version. I just fixed it.

1 Like

Thank you for the quick fix.

I am sorry, but I miss the thumbs folder at https://getkirby.com/docs/getting-started#kirby-s-folder-structure.

But I also want to tell, that I like the new page https://getkirby.com/docs/getting-started. This is the best improvement of the docs for the last months!

Please continue like this!

Thank you for the feedback, we will add the thumbs folder to the list.
But again, it would be great if you had a GitHub account to report those things directly as an issue. That would reduce our work by a fair bit. :slight_smile:

I’ve just added it to the master branch.

This is discussed at https://forum.getkirby.com/t/how-to-get-zero-sorting-in-panel/597/3 some time ago.

It is not my decision to use more than ONE issue queue.

And, sorry to repeat it again, I can not understand this, whether now then before. Until now, I have to look at many places to follow all, e.g. at:

Sorry, Kirby is ONLY my hobby and not my business.

Good luck! Furthermore, I will use and further promote Kirby.


We definitely understand and respect that you as the user don’t have that much time when reporting bugs and suggesting new features and that’s totally fine.

However let me explain again why we are collecting our issues in the GitHub repositories: GitHub allows us to quickly close issues, we can directly refer to code from the issues and it helps us to keep the overview.
We use several repositories for that to keep the issues sorted into the Kirby components. A Kirby bug needs to be fixed differently than a Panel bug and issues of the Kirby site are completely different again.

If you don’t want to invest that much time, you don’t need to follow the different places. If you find a bug, just post a new issue and we will take care of it. :slight_smile:
Posting on GitHub instead of here takes nearly the same time for you but reduces the time we need to solve the issue (= the time we can’t use to actually improve Kirby). If you see it differently, that’s fine and you are still welcome to post here, but I hope you understand our situation.