Migrate to Hugo.

This is a big and somewhat complicated decision, but the crux of it is this:

The _mkdocs_ tool embeds a ton of "I am writing a manual" assumptions about document structure.

These assumptions include that there is a single, sitewide TOC, that a top nav bar is broadly an appropriate way to skip around in the document, and numerous others. They serve that use case well, but that's not really what this site _is_, or how I intend it to be approached. I'm trying for something more blog-esque (and deliberately a bit haphazard).

Hugo is an experiment. This commit migrates most pages to it, but it does drop a few; this is a convenient excuse to forget items I'd prefer not to continue publishing.

2 files changed, 10 insertions, 5 deletions

diff --git a/tools/build b/tools/build
index 5e25d51..49b2007 100755
--- a/tools/build
+++ b/tools/build
@@ -4,6 +4,6 @@ cd "$(dirname "$0")/.."
 
 ## tools/build
 ##
-## Converts the content in docs/ into a deployable website in site/
+## Converts the content in content/ into a deployable website in public/
 
-exec mkdocs build
+exec hugo --cleanDestinationDir
diff --git a/tools/publish b/tools/publish
index 9ee5d71..14a69ef 100755
--- a/tools/publish
+++ b/tools/publish
@@ -4,8 +4,13 @@ cd "$(dirname "$0")/.."
 
 ## tools/publish
 ##
-## Publishes site/ to the S3 bucket hosting grimoire.ca
+## Publishes public/ to the server hosting grimoire.ca
 
-exec rsync -zav --delete --progress \
-    site/ \
+exec rsync \
+    --compress \
+    --archive \
+    --delete \
+    --verbose \
+    --progress \
+    public/ \
     admin@grimoire.ca:/srv/grimoire.ca/webroot/