feat: Expose cdn settings as params

[bradbeam]

This moves the configuration of much of the cdn (js/css) into the configuration
so they can be more easily maintained.

Signed-off-by: Brad Beam [email protected]

[LisaFC]

Thanks for this! This is a potentially interesting approach (especially as we have some users who don't necessarily want to use our chosen CDNs), but is presumably going to break any site that doesn't update their config.toml/yaml

Thoughts @chalin @geriom @emckean?

[fekete-robert]

Maybe we could use the default function of hugo, and use the config parameters if set, or use the original cdns if not.

[LisaFC]

I'll have a look at how the scripts partial would look if we used defaults.

[bradbeam]

Sorry for the delay, I just pushed up changes to include defaults inside the templates.

[deining]

This moves the configuration of much of the cdn (js/css) into the configuration so they can be more easily maintained.

I like the idea. This PR does not pull in the latest versions of the resources, however (e.g. it pulls in KaTeX 0.15.1, while latest version is 0.16.2.) Were great if this could be improved.

[bradbeam]

I wanted to keep the scope of the change as minimal as possible. I think version bumps can be done as followups to this.