@mikeuk i understand the confusion, this is very normal when trying out new thing isnt it! I can asure kirby is much much simpler than Drupal so don’t overthink it.
I think you have to realize that kirby is mainly aimed at much less experienced developers than Drupal devs. Its main aim is simplicity. If you can make sites with Drupal - Kirby is going to be piece of cake. And you might find it to be extremely fast for development (reason why senior devs around here are using it).
Considering the Blueprints. I dont know how many cmses you’ve seen but ive seen a lot and Blueprints its actualy very common name for files that describe how the admin area (panel) will be generated. Ive seen two types of approaches cmses (that have same funcionality) to take:
-
They either describe pages and call it a blueprint (blueprint for mapping of many fields belonging to page)
-
Or they dont think in pages at all and describe content and call it something like content type (you create type of data with certain properities - fields).
Its the same thing just from different viewpoint.
By the way - worpdress and drupal dont have similar functionality without doing lot of additional work. In wordpress to get custom fields example you need sophisticated plugin (and the good ones cost money) that changes the way wp works. And while i like Drupal more than WP - Drupal is actualy very oldschool in its thinking and the namings in drupal are very nonstandard. Of course Drupal also grew from CMS into almost aplication platform - it tries to be so universal so you can use it as backend for anything. Its much bigger in scope.
With kirby its much simpler and more focused. Its just about creating websites.