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.

1 files changed, 0 insertions, 15 deletions

diff --git a/docs/code/index.md b/docs/code/index.md
deleted file mode 100644
index e0efe37..0000000
--- a/docs/code/index.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Code
-
-Pieces of code and code-adjacent work, with or without exposition, that don't quite fit into the library ecosystem, but which I enjoyed writing.
-
-* [Using the shell environment as a project tool](tools-convention.md) — A general and less tooling-intensive approach to automating routine project tasks.
-
-* [A Users, Roles & Privileges Scheme Using Graphs](users-rolegraph-privs.md) — An SQL schema and associated queries for handling permissions when roles can nest arbitrarily.
-
-* [Configuring Browser Apps](configuring-browser-apps.md) — Notes on the available techniques for delivering runtime configuration to code running in a user's browser, and the tradeoffs involved.
-
-* [Writing Good Commit Messages](commit-messages.md) — A style guide.
-
-* [Some collected advice about Git](../git/index.md) — Not the source control tool we want, but definitely the source control tool we've got, and I think we should make the best of it.
-
-I also maintain a [Github account](https://github.com/ojacobson/) for more substantial projects.