Blueprint editor#20

A visual editor for blueprints, which would administrate all the yaml settings for you.

This would really help speed up kirby dev, I always mess up the yml indentation and live in the field docs.

A visual editor which shows all possibilities, depending on the fieldtype, would really speed up the whole building-process for new websites. For now, i always have to switch between searching the docs, editing the blueprint and reload the panel.

It would also be interesting to edit blueprints from within the actual page view. Like changing field order in the panel directly.

Oh, my, goodness, yes please. I would love this. I dislike editing YAML or trying to remember how to structure blueprints or what options are available for each field/structure/extends/defaults/templates/etc., etc. This is an awesome idea.

The concept of coding up the blueprints is a plus in my book. I found that a visual builder gets very clicky (e.g. lots of click, inputs, selects, clicks… ) Ever use Processwire? Coding those blueprints does require some referencing from time to time, but it’s very fast and efficient (plus ditches any bloat required to make that process visual).

@Chris I guess this will not change, you can still edit manually.

@Chris I’ve used processwire and statamic and both offer a very helpful visual interface for creating blueprints - i really like them!

This sounds like a great idea for a plug-in.

Please make this happen!

The visual blueprint-editor would be the reason for a new major update to 4.0 😍🔥

I am also apposed to this. I’d would be cool to have a plugin, but the core kirby teams should not waste resources on this untrivial undertaking. I think kirby’s core values are to provide an extensive toolset to enable developers to create a great user exeperience for users. structuring blueprints for pages and blocks is definately a developer task and not for someone who does not know what they’re doing. creating blueprints is already very fast. copy - paste - rename - extend.

I need it!!!

This seems like a bad idea. The blueprints are perfect just as they are and seems like a massive undertaking for not much added benefit.

This seems like a really great idea. Especially for people who only use kirby every so often and don’t know the system by heart, so then need to have the docs open for reference, just to set up some fields. Using something like Craft CMS is a heaps better experience in this regard (for me). How would it be a waste of time/resources if the feature made certain users much happier? Happy users choose kirby more often for client projects = benefit?

@Maxwell Hibbert I totally agree! The UX is much better using systems like Craft CMS or Statamic. Especially when each webdeveloper can choose between writing biueprints by hand or using a GUI. This feature makes kirby very interesting, especially for new users, as even complex construction plans can be implemented more quickly. I love the idea from @Bastian 👍