When describing complex content types, frontmatter.json quickly become a long and unreadable file.
I just finished creating a content type describing Hugo various front-matter fields, and my frontmatter.json has 211 lines of content, and this is just with one complex content type and some frontmatter settings.
Hugo allows to split is configuration file in multiple files stored in config folder, and named according to the config section they store.
An example of Hugo splitted config can be found at https://github.com/razonyang/hugo-theme-bootstrap-skeleton/tree/main/config/_default
Frontmatter could allow a similar setup in .frontmatter/config to allow an atomic configuration.
Another option is to allow the use of an import directive in frontmatter.json where the user explicitly import another file in lieu of a parameter value.
When describing complex content types, frontmatter.json quickly become a long and unreadable file.
I just finished creating a content type describing Hugo various front-matter fields, and my frontmatter.json has 211 lines of content, and this is just with one complex content type and some frontmatter settings.
Hugo allows to split is configuration file in multiple files stored in
configfolder, and named according to the config section they store.An example of Hugo splitted config can be found at https://github.com/razonyang/hugo-theme-bootstrap-skeleton/tree/main/config/_default
Frontmatter could allow a similar setup in
.frontmatter/configto allow an atomic configuration.Another option is to allow the use of an import directive in frontmatter.json where the user explicitly import another file in lieu of a parameter value.