Hey there,

After looking this up and confirming this was not possible (thanks again @jmooring!) I would like to propose a feature, that works similar to the draft keyword, but allows specifying the environment(s) for which pages/posts shall be built for. Specifically, I suggest adding an environment keyword, which would accept a list of values:

environment:
  - production
  - staging
  - development

This would allow for per-page/-post management of individual pages/posts, in which individual teams work on parts of a large Hugo deployment, in which none of them (but one admin-team) have access to the actual environment configuration files. Through a keyword inside the pages/posts, teams could individually decide to which environments pages/posts would get deployed to, without having the admin-team involved for adjusting the cascade._target configuration.

I would appreciate thoughts on this! Thank you.