Creating a single child page: Pages section or Pages field?

I found an answer in this topic: Is it possible to nest a column within a column? - #2 by texnixe

It is possible to have sections in a column. My mistake was doing something like this:

columns:
  sidebar:
    fields:
      # Config for the fields
      # …
    sections:
      gallery:
        type: pages
        # Config for the pages section
        # …

Turns out that when you use a fields key in a column, that’s a shortcut for creating a sections structure with an entry of type fields. When you want to have both fields and non-fields sections in a column, you need to be more explicit and declare everything as sections:

columns:
  sidebar:
    sections:
      stuff:
        type: fields
        # config for the fields section
        # …
      gallery:
        type: pages
        # config for the pages section
        # …

So that makes sense.

If I’m allowed a tiny rant: maybe that’s the programmer in me, and others have different preferences, but I wish Kirby didn’t have so many shortcuts in its Blueprint parsing (like deriving the section type from keys, optional sections key…). Because when the implicit conditions for using a shortcut are not met, then everything breaks and you don’t get an error or any guidance.