Kirby is for me really the one and only CMS. Thanks to the blueprints scheme the panel is very wide customizable. Also: with great Plugins made by also great people like @DieserJonas and @distantnative it is really easy to use without fully compromizing the joy of use. With the concept of @timoetting’s free page format plugin Kirby is really just some steps away to enable fully customizable webpages. But that’s all you already know, I guess.
But there’s still a gap between what you’ve created and where you’re creating it. It’s like painting a portrait without seeing what you’re already painting (I really recommend Bret Victors talk “Inventing on Principle” for this principle). And that’s also some behavior I’ve observed while working with Kirby: you really want to have some kind of preview.
My vision is to have soon a Kirby version with the benefits of a fully customizable inline WYSIWYG editor combined with all the benefits Kirby brings to the developers and users.
All right, but what happens to the fields?
Yes, the blueprint fields are very important to standardize the content you will find on the web page. @timoetting’s builder shows how to declare and develop a standardized block format with an extended version of the structure field. Additionally it is still very important to have some kind of meta informations and additional data. So the panel fields should still be used to standardize content.
A simple example
If you think about a blogpost page, you would think about having some kind of meta informations, like the author and the date and one big area for the content, typically formatted in Markdown. So the vision for this example is to write the blogpost directly in your page - everything will adapt the style of the page. You can see directly how it looks like. You don’t need some kind of preview mode or anything else.
Is it possible?
Well that’s truly the main question behind everything. Yes it is (like almost everythink) but I don’t know how hard it is to bring the idea to life.
Here is a pic to visualize concrete5’s drag and drop block principle:
concrete5 isn’t really a WYSIWYG-Editor, but this is also good to show a solution for a more complex block:
gpEasy is truly an inline WYSIWYG editor (but the code is awful):
The good and the bad
Last but not least: it’s needles to say that it wouldn’t always be useful to have such sort of WYSIWYG inline editor so this should be something optional - like an alternative Panel. But I think this could be really an enhancement for the users, for the clients and also for the agencies and freelancers out there. And of course it would be another argument for choosing Kirby.
Alright. What do you think?