Prevent client from reordering, renaming or changing status of pages in Panel

The CMS Questions
21

I think I get it now. The different type of sections – pages, files, fields, info – have to be kept apart in separate sections.

title: Site

sections:
  listed: # this is a section within the 'sections' this can be called anything perhaps section_a
    type: pages
    status: listed
    image: icon
  content: # # this is a section within the 'sections' this can be called anything perhaps section_b
    type: fields
    fields:

So the ‘sections’ is divided into two sections, one for the pages section and one for the fields section.

And it seems that even if there is only one section the Blueprint still needs to have:

sections:
	section_a:
22

Perhaps this article will give you a clearer understanding of how blueprints work:

The video illustrates the theory with practical examples:

1 Like
23

Hey thanks. I’ll take a look. I’m struggling to understand the written docs