Yes, you would have to adapt the notes section (/site/blueprints/sections/notes.yml
) and set the parent
option to the new parent (currently set to parent: site.find("notes")
).
No, of course not. You can have blueprints for pages on all levels, and children in a folder don’t have to use the same blueprint. The template/blueprint a page uses is defined in the pages section.
To make the notes parent/children show up in your new parent page, you have to include a pages section in your parent’s blueprint.
For example, if you put the complete notes
folder into the test
folder with a text file test.txt
, then in your test.yml
you could create a pages section like this:
title: Test
sections:
notes:
headline: My Notes
type: pages
parent: site.find("test/notes")
templates: note
This would then list all children of the notes page. With the templates
option we define that new children may only be created using the note.yml
blueprint.