Is there an easy way to get the Panel to show all the Fields I’ve made in my pages .txt files? So the panel automatically picks up the Fields I’ve already made in my content .txt files?
Preferably in the default Blueprint, so I don’t have to make any other Blueprints?
So for example:
Description meta tag:
It feels like I’m duplicating work. I’ve created my Fields and added my content into the .txt docs. And now I have to create Blueprints to allow me to use the Panel to edit my Fields and content.
Plus a way to include certain images on the page (but not all) and in a specific order, with captions showing?
Can I caption images in the Panel and make alt text? It would be neat if the same Blueprint allowed this
So I’m going to have to duplicate quite a bit of work – creating a Blueprint to get the Panel to display the Fields I’ve already made? I guess I had assumed the Panel would automatically display my content .txt documents and fields that I have already created.
I’ve read all the docs on Blueprints, but I’m afraid I didn’t understand a word of it. Any pointers on how I get the Panel to display my Fields and content?
Usually, when you use the Panel, you create the blueprints with all the fields you need first, then the content files are created automatically via the Panel.
The reason why you have to create the fields in the blueprint is because it gives you the option to create as many page types (blueprints with different layout, fields etc) as you need to structure your content.
If you start with the content first, you have some duplicate work to do, that’s true.
I already recommended you to have a look at the blueprints and the content files in the Starterkit, this will give you a good idea of how it all works. It’s impossible to repeat our complete documentation here in the forum.
You can also find example blueprints here:
The guide is here together with a video:
If that doesn’t help, please feel free to come back with specific questions.
That also wouldn’t work in a good way. The Panel can’t know just by the content what field/input you would want to represent a field in the Panel. A text input? A textarea? Maybe actually a select dropdown?
I would say that you are the only one who has never had the willingness to fill your gaps by reading docs carefully and adapt your coding style to the framework of a modern CMS like Kirby. To blame the support who has already put much time and effort into it is not appropriate.
Most of your posts in this forum (and I have read them all) could be answered by “RTFM - and try to understand”. E.g., if the doc says “… Kirby automatically parses…” I would not expect the need to turn something on or off, otherwise it wouldn’t be automatically. So please, slow down, invest some time to learn from the docs, the cookbook, the screencasts, the instant demo and the starterkit, all of them made with time consuming commitment and deliberation, and if there are still open questions afterwards, everyone here will enjoy to give a helping hand.
I’m coming to Kirby as a complete novice in content management systems, PHP and web development in general. I really like the look of Kirby and the support on this Forum has been amazing. I have found the documentation to be hard – for me – to understand. This probably says more about me, than the documentation. But I do wonder if some of the docs are written assuming knowledge. Actually I wonder if I can help – if I spot something that I don’t understand I’d want to point this out, to see if we can improve the docs. If I can understand it, anyone can!
As you suggest, I’ll slow down and re-read the docs.
Your reaction really warms my heart in many ways. On the on hand we always went to help everyone who’s getting started as good as we can and on the other hand it’s sometimes just not possible to go further because of missing time and resources.
It’s especially great that you commented in a way that I totally didn’t expect. I thought it’s going to be at least disappointment or even anger. It tells a lot about you that your comment is so self-reflected.
You are also right with your remarks about the documentation. Of course we have assumptions of the knowledge of our users. We already try to keep the entry barrier as low as possible. We hate it when the docs start something like “Just run npm run dev” without any additional explanation. But we have the same kind of weak spots. It’s becoming tougher and tougher to put ourselves into the shoes of beginners and balance the expectations of novices and pro users in the docs at the same time.
As a designer I am often trying to bridge the gap between my clients expertise and what their audience knows. As you say dealing with ‘assumed knowledge’. Once we’re experts in something it then becomes very hard to explain it to someone who knows little. And I know little when it comes to CMS, PHP and development!
An example of this is I don’t know what Github is or how to leave an issue (without breaking anything)! If I have any suggestions perhaps I can simply direct message you on here?
I know I am late to this conversation, but also you don’t have to worry about breaking anything. Posting an issue on Github is like leaving a comment, you cannot break anything for us. Worst what could happen is an issue in a wrong repository or so - but we can move that around, so that’d be not bad at all