What's the future of Kirby?

[dfreire]

I suppose you need to define complex.

IMHO Kirby can become challenging when:

• your website is very large with lots of pages and files
• you need to have dynamic content on your website

For the first situation, please check this:

Concerns about using kirby for a medium size website that will grow over time

You can have a look at my use cases: http://ruderclub-nuertingen.de Still using Kirby 1, at the moment working on updating to Kirby 2. There are many invisible pages behind which are just displayed as data (at the moment ~300 pages in total). http://wagner-ewar.de The product folder alone holds all ~250 products. Only page loading issue comes by design (at the product line, where all products of one line are displayed on the same page without pagination…). Also doing many connections in betw…

Kirby panel support for database

I think @jenstornell concerns are valid. If Kirby becomes popular for lots of use cases, at some point the community will need to address the performance issues that will naturally arise with trying to handle thousands of files. There are different approaches to how one might solve this. One possibility is to have pluggable persistence, one user might opt to store everything in disk, another might wish to use a database. Another possibility, which I find much more appealing, is to use database…

For the second situation you can use something like firebase, or if you want to avoid vendor lock-in, an open source equivalent (shameless plug: I’m working on diskette which is my attempt to solve all my dynamic data problems).