Static site generator

[justincy]

I'm going to try using Hugo to build the static website.

This will help with #16, #17, #18.

[justincy]

Looks like Hugo will work great. But I also want to investigate Gatsby.

[justincy]

Possible Hugo theme: https://themes.gohugo.io/hugo-flex/

[justincy]

Gatsby is built with React and that's overkill for now.

[justincy]

I've got Hugo setup on a branch with a template for graphs that includes the SVG and JS linked properly.

TODO:

• [x] Update the build process to work with new asset locations (both input and output)
  • [x] graphs/signs.gv is now at signs/signs.gv
  • [x] simplified.gv should be output to signs/simplified.gv
  • [x] SVGs are written to the svg directory
  • [x] Don't need to build the HTML pages anymore
• [x] Update the CSS
  • [x] SVG viewport fills in available space between header and footer with flexbox
  • [x] SVG hover interactions work as they did previously
  • [x] Scripture refs are displayed

[justincy]

I moved the graph files out of graphs because it seemed to conflict with the graphs archetype and new content/page files for graphs were being created there when they really should be in content/graphs. But I didn't really know what I was doing at first. Is that still the case? I'd prefer to keep the graph files in graphs.

[justincy]

Yeah, it's still conflicting. Oh well.

Maybe graphs-data is better than signs? I chose signs because the repo will only have signs.gv in it at the start. Other files will only be added during builds.

[justincy]

TODO:

• [x] custom.css needs to be fingerprinted
• [x] Add google analytics
• [x] Add full and simplified graph links to the navigation header
• [ ] Add homepage content
• [x] Netlify build

[justincy]

Closed by #22