Add/edit page children in panel

Hi,

I took over maintenance of a site originally designed for Kirby 2. As things started to break down, I upgraded it to Kirby 3 and took care of most issues that arose as part of the change (I had never worked with Kirby beforehand).

One thing is still missing, though, and I cannot figure out how to fix it. In the old version, page content was saved as children, i.e., for a list of publications (shown on a page “Publications” with navigation), the information was stored as one child per publication, each respective folder containing a .txt file with the information and an image with the book cover. In Kirby 2, you could edit those children (shown as a list with detail information behind a click) in the panel. In Kirby 3, that functionality broke.

I know I’m not being too precise, but I’m sure that’s a common problem somehow. How do I design the panel templates to show the children of a page, not the content of the actual page itself.

(while trying to fix it, I wrote a python script merging all children txt files into a single txt with all the information, which worked. However, the site uses child page urls to display individual item information and now I broke that system. I figure it’s easier to get back to the original design and get the panel working.)

If you need any more information, I’ll happily provide it. I’m grateful for your help.

Thanks in advance,
Marcus

Hello and welcome to the Kirby forum!

I didn’t understand your question 100%.
Do you mean related articles?

To show the children of a given parent, you create a pages section in the parent blueprint, as for example in the notes or photography pages in the Kirby STarterkit:

Here the sections are called drafts, unlisted etc, but you can name them however you like. The sections themselves in the example are defined in the /site/blueprints/sections folders (which is not required, but useful if you use the same section in several places).

The same is true for the site.yml (Dashboard of the panel), where you can create sections to make pages and their children directly accessible without having the visit the parent first. See site.yml in the Starterkit repo for examples.

Oh, wow, this was so much simpler than I thought it would be. Thank you so much!