What makes it more "mature" then say grav? Just started using it and it's pretty good so far.

Well, here is the point of view of a back-end developer (database) that scratched his head on Jekyll last week trying to figure out how to just make a damn god simple (but customisable and multilingual) blog using almost only markdown...

I just spend around 20 minutes on each kirby documentation pages and on grav docs.

So after 20 minutes with kirby doc I have figured out how to reach my goal with kirby even if there are some downsides and that i'll have to remind my old php courses to customize.

but after 20 minutes on grav i'm still trying to figure out if it's gonna be as simple as I need or if I'll have to understand if a twig templating of my markdown, already accelerated with parsedown and doctrine in a pimple dependency injection container will help me manage my YAML simple configuration along with the Symfony console...

YES this is all from learn.getgrav.com > BASIC > What is Grav? - the first goddam chapter of the documentation !

So the landing text of the doc is basically throwing at me that i'll have to ingest a bazillion new front-end trendy concepts while actually I just want a Markdown based site...

Maybe grav is great but i'll probably never know because documentation killed all curiosity in me.

Its much older. Kirbys admin is the big difference.

In Grav admin you have problems when you start to have more than 30 pages. Because of its design it shows pages as flat structure. In kirby its more like folders. In grav you cant say this type of page can have only these type of children. Basicaly you have to remember which page type belongs to this page.

Kirby comunoty plugins are awesome kirby-modular for exp.

Kirby also has permissions in admin, so you can limit users what they can do.

Its also way easier i think while achieving more. There is clear path of how things work and Grav is somehow overengineered idk why i would my simple cms to compile stylus or js... it uses twig which is fine but i found it to be wrong choice because in cmses like this you are traversing trough the pages (pages are your db). Twig is not meant to do that its for showing already queried stuff from db. So they are basicaly recreating more and more php in twig so you can actualy get the data.

Thanks. I will have a look at Kirby, I started coding a blog that's good enough for my needs in php with a database.

I am just having a loot around see what there is.

Can I create custom fields for posts in the Kirby admin frontend (or any other way??

Sure! Take a look: https://getkirby.com/docs/panel/blueprints

Excellent, thanks.

Can you extend Kirby with custom content types and fields to represent arbitrary things, ie a list of team members or pricing plans?

Yes, totaly. This is why we use it. You basicaly make yaml schema of the conent in admin interface and then simply query it in template.

There is also core plugin called kirby modules which turns kirby into very sophisticated "site builder" we use it to make highly modular websites while keeping it simple for clients to administer.

How do you handle clients updating the site? Because in my experience, people don't want to learn markdown.

They dont have to. The admin is basicaly big form field generator that maps values to markdown.

So you make field for everything. Dates, checkboxes image selectors..

Only time they would have to touch markdown is when they would need to format text - article for example. This can be solved by using wysiwyg field instead of md field.

Does somebody know how does it compare to Lektor?

Lektor builds static html, kirby is just a cms without a database.