diff --git a/content/about/index.md b/content/about/index.md index e3aa831..1642c6e 100644 --- a/content/about/index.md +++ b/content/about/index.md @@ -1,6 +1,6 @@ --- title: "About Me" -description: "A brief bio and my credentials" +summary: "A brief bio and my credentials" showDate: false showReadingTime: false --- diff --git a/content/series/aardwolf-adventures/_index.md b/content/series/aardwolf-adventures/_index.md index 903db66..45768ef 100644 --- a/content/series/aardwolf-adventures/_index.md +++ b/content/series/aardwolf-adventures/_index.md @@ -1,4 +1,5 @@ --- title: "Trying to break Aardwolf" +summary: "A game of life and death and stockpiling pocket portals" --- In a friendly competitive sense, of course. The game at its core is about speed and finding shortcuts, usually through space. \ No newline at end of file diff --git a/content/series/blogging-with-quartz/_index.md b/content/series/blogging-with-quartz/_index.md index 9f34840..8f05b75 100644 --- a/content/series/blogging-with-quartz/_index.md +++ b/content/series/blogging-with-quartz/_index.md @@ -1,5 +1,6 @@ --- title: "Authoring a blog in Markdown" +summary: "Blogging for fun and posterity (myself)" --- The core thesis of this project is using [Obsidian](https://obsidian.md) for authoring my blog posts. I'm a big fan of Markdown for authoring and Obsidian's already where I keep my notes. It's gone through a lot of iterations, but the current version uses Gitea, Drone, and a few Docker images I've built that do various types of sanitizations/transformations. diff --git a/content/series/building-with-bazel/_index.md b/content/series/building-with-bazel/_index.md index 759e2d6..82ecf50 100644 --- a/content/series/building-with-bazel/_index.md +++ b/content/series/building-with-bazel/_index.md @@ -1,4 +1,5 @@ --- title: "Building with Bazel" +summary: "Bazel is an extremely opinionated but powerful build system" --- Bazel is a build system with a lower profile than stuff like cmake or gradle, and it's more esoteric by a significant margin. In particular, the ecosystem is going through a migration between different ways to handle dependencies and it seems to be going about as smoothly as the Go 1.11 transition. \ No newline at end of file