I think the general language on the site is geared towards developers, although cookbook recipes help. The level of abstraction in the (excellent) reference is for developers: lots of ways the manipulate your content, makes your head spin, but few examples.
Our goal is to implement Kirby features in “layers”. Like Nico wrote, it’s a bit like progressive enhancement: Kirby sites can be really simple (even without using the Panel at all), but they can also be customized to fit even large corporations and organizational structures. It’s really important to us that every advanced feature stays optional and gets out of the way of all devs who want to build simple sites.
Our docs reflect that idea: The guide is the introduction for general concepts and useful to get started, the cookbook contains practical examples for different use cases and the reference contains the details about possible integrations with Kirby.
It’s always difficult to explain complex concepts in simple terms, we still want to provide all the details for those who need them. Good point regarding the missing examples: Unfortunately it’s sometimes quite difficult to think of every use case when writing these examples. PRs or issues in the getkirby.com repo on GitHub are well appreciated.
Also, as you wrote, we have our forum: If something in our docs makes your head spin or you need a practical example for your task, then feel free to ask in our forum at any time.
Setting up blueprints with tabs and lots of options gets very messy very quickly, I’m always fighting with the yaml structure.
Yep, that’s true. Blueprints can be really simple, but as you write they can get really complex with complex structures. We have plans to build a blueprint editor that can help to set them up visually. There’s no timeframe yet, but it’s on our list.
So and last you have get to code the front end which can turn into php spaghetti quickly and page models and controllers and plugins all make things more complex/abstract.
I think that’s always the case when programming. Either you get spagetti or you get abstractions. Solutions in between can get quite complex as well as they often need to do some magic that is then hard to understand.