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.
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.