So I would say that the config is set up to serve the use cases we most commonly see, and to work with all supported software that we provide integrations for.
So most studio’s work with assets and shots so it makes sense to cover those. However, you don’t need those if you don’t want them.
The environment you will probably always want is
project.yml especially if you are using Shotgun Desktop as this always works in a project context.
You will need
site.yml if you are using the config as a site config, i.e a
PipelineConfiguration without a
Other than that it’s up to you what you want to keep or lose. For the most part though we’ve tried to keep the config as sparse as possible, for example, we only define the settings in the environment ymls that need to be set, and leave off anywhere the bundle’s default setting can be used.