Let’s say you had this structure:
content/
├── books/
│ ├── book-1.md
│ ├── book-2.md
│ └── book-3.md
└── films/
├── film-1.md
├── film-2.md
└── film-3.md
And you wanted to exclude book-2 and film-3 from your “production” environment builds. The cascade target keywords are glob patterns, allowing you to do this:
[[cascade]]
[cascade._build]
render = "never"
list = "never"
publishResources = false
[cascade._target]
kind = 'page'
path = '{**book-2*,**film-3*}'
No. You cannot set a build option that is keyed to a particular environment.
Even if I could do that, I probably wouldn’t. I think it’s easier to track this stuff centrally in site configuration.