Default manifests

In general, settings go into manifests that directly relate to an "object" on the site, that is, either the manifest of the site itself, or into the manifests for artists, catalogs, multitrack releases and tracks.

However, a site directory can contain arbitrary directory hierarchies where artists, releases, etc. are placed only at the deepest end of the hierarchy, which sparks the question: If I put a number of artists, releases, etc. in an intermediate directory for organizational purposes (for instance: grouping all releases by year, or all artists by country), can I use that to somehow specify default setttings that apply to all entitites within this grouping directory?

The answer is yes, and the mechanism that allows it are default manifests – manifests with the file name defaults.eno that can go into any directory that is not the site directory or an artist, catalog, multitrack or track directory.

Defaults only, prefixing mandatory

As a defaults manifest is not tied to a specific object or scope (settings may relate to artists, catalogs, tracks, etc. alike), all settings within a defaults manifest need to be prefixed with their respective target scope, for instance:

track.more_label: Lyrics
track.streaming_quality: original

Consequently, a defaults manifest can only ever contain default-able and/or universal settings (which are identified by their Default-able and Universal badge all across the documentation).