Adding more docs for citations?

[maelle]

Might be too niche. I was thinking that some users might want to use a site-wide CSL, and even a site-wide bibliography (it was asked in the issue tracker of distill).

It's easy to get and I wonder whether it should be documented, maybe in an article about bibliographies.

• save the CSL and/or bib at the root for instance.
• in the archetype (since there's no site config for hugodown, just individual Rmds), add

bibliography: ../../../refs.bib
suppress-bibliography: true
csl: ../../../chicago-fullnote-bibliography.csl

I've just tested it.

[hadley]

I’m also going to add a hugodown specific config file where those defaults can be recorded.

[maelle]

Ah cool! why does it have to be separate from the Hugo config file?* Couldn't the settings live in it? Wondering because I find bookdown's two config files puzzling (I never remember which is which).

• I guess one reason is the people not using config.toml but weird settings instead, but they could find a way maybe.

[hadley]

Because I'd estimate it's at least a day's work to write code that reliably finds all hugo config file given that it can be in three different formats and spread across multiple directories. (I agree with you about the bookdown problem, but I think that's fundamentally different in nature)

[maelle]

right. will you call it _site.yml? :-)

Edit: I take it back. The specific name is better for GitHub code search 😁

[hadley]

Note to self: for this case, I think we'd need a preprocess hook that adds the bibliography, suppress-bibliograph and csl to the yaml front matter if they don't exist in the yaml front matter. csl should probably default to a file included in hugodown itself, since we can likely pick a reasonable default.

[maelle]

Just wanted to note I got this question. :slightly_smiling_face: So in the future the plan would be for such defaults to live in hugodown.yaml? A default CSL sounds awesome.