Hugo TODO

1. make sure our folder structure is the proper one for what we want to achieve. Also see if we can make folder nesting level smaller, maybe by using permalinks or something. For content and static.
2. can we generate SRI hashes for existent files on the fly? For bootstrap.min.css, bootstrap.*.js, popper.js/1.14.7/umd/popper.min.js. This would simplify things as we could remove the release-sri script
3. get image width/height with Hugo when possible (examples images, homepage)
4. maybe use Hugo Extended version for docs’ CSS? This is now done
5. bep’s suggestion:

   Re.

   {{< partial "callout-warning-color-assistive-technologies.md" >}}
   

   The partial above uses the partial func to load, parse and execute templates. This has its limitations and is possibly ineffective. I would recommend that you store your callouts (and other content files you want to include) in a so-called headless bundle – and load them via .GetPage. This way you can use markdown + shortcodes etc.

6. bep’s suggestion:

   Ref. {{ block "header" . }} in your single.html template. Blocks only make sense inside base template(s) (i.e. baseof.html), which I cannot see. I would highly recommend that you restructure your templates to use them. It removes some repetition.

7. Fix https://github.com/twbs/bootstrap/blob/6335fbe224f28d2ce65c628756a84113ea65643f/site/layouts/_default/docs.html#L27
8. Add a body class like layout-{{layout}} page-{{kind}}-{{title}}{{ with .Params.body_class }} {{ . }}{{ end }}

[bep]

Re sha384 – see https://github.com/gohugoio/hugo/issues/5815 – I will get that in the (big!) release on Monday.

With map files etc. in play, I think a “regular leaf bundle” will do the work, as map etc. files will just be copied to destination.

[budparr]

Curious why you’re running Fingerprint twice? Also, I think resources.Get is looking for your CSS file relative to the assets directory, so you may need to change your path. I’m happy to pull the repo down and fool around with it if that would be helpful.