Move cascading properties from to config.yaml

I have many empty section files containing only cascading info for the section. It would be more clean to move all this data to config.yaml just like how permalinks are defined per section.

  • Why is the indentation of background: ... in the example different than indentation of kind: ... and others?
  • Say I want to add a section listing to main menu, why doesn’t the following work:
  - _target:
      path: /pages/*
      kind: section
    menu: main

You can do that. Just take the cascade entries from your file and move them to config.yaml and it should work as expected.

Basic example: add property menu: main to the list of /pages/.

The code provided above doesn’t seem to work for me.

The code you provided isn’t correct. cascade is a top level config option.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.