internal: Make footnotes work

Apparently, the footnotes and superscript extensions conflicted with
each other.

5 files changed, 11 insertions, 48 deletions

diff --git a/blog/degoogling-part-one.md b/blog/degoogling-part-one.md
index 94fafea..cceb3a5 100644
--- a/blog/degoogling-part-one.md
+++ b/blog/degoogling-part-one.md
@@ -3,7 +3,7 @@ title: "De-Googling Part One"
 date: 2020-05-25
 draft: false
 series: 
-  - degoogle
+    - degoogle
 ---
 
 Taking a look at my use of [Google](https://google.com) and their... not-great history of privacy, I've been spending my spare time over the past few years working on, if it's not possible to *completely* get off their platform, then at least minimize my use of it. <!--more-->Frankly, I think I've been fairly successful. So far I've migrated my email from Gmail to [Migadu](https://migadu.com), and I've been working more and more on using services like [Disroot's](https://disroot.org) Nextcloud instance instead of Google Drive. [DuckDuckGo](https://duckduckgo.com) has been my default search engine for the past year. Those were really the only two Google services I used.
diff --git a/blog/draft/hello-world.md b/blog/draft/hello-world.md
deleted file mode 100644
index 3c8e296..0000000
--- a/blog/draft/hello-world.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Hello World
-layout: false
-draft: true
----
-Welcome to [Hexo](https://hexo.io/)! This is your very first post. Check [documentation](https://hexo.io/docs/) for more info. If you get any problems when using Hexo, you can find the answer in [troubleshooting](https://hexo.io/docs/troubleshooting.html) or you can ask me on [GitHub](https://github.com/hexojs/hexo/issues).
-
-## Quick Start
-
-### Create a new post
-
-``` bash
-$ hexo new "My New Post"
-```
-
-More info: [Writing](https://hexo.io/docs/writing.html)
-
-### Run server
-
-``` bash
-$ hexo server
-```
-
-More info: [Server](https://hexo.io/docs/server.html)
-
-### Generate static files
-
-``` bash
-$ hexo generate
-```
-
-More info: [Generating](https://hexo.io/docs/generating.html)
-
-### Deploy to remote sites
-
-``` bash
-$ hexo deploy
-```
-
-More info: [Deployment](https://hexo.io/docs/one-command-deployment.html)
diff --git a/blog/how-to-plan-an-event.md b/blog/how-to-plan-an-event.md
index bc22b9f..6454c4d 100644
--- a/blog/how-to-plan-an-event.md
+++ b/blog/how-to-plan-an-event.md
@@ -1,7 +1,7 @@
 ---
 title: "How to Plan a Successful Event"
-date: 2021-12-10
-draft: true
+date: 2022-01-21
+draft: false
 ---
 
 Note: This is not meant to serve as a definitive "how to plan" guide. This is
@@ -24,7 +24,7 @@ service providers.
 ## TL;DR
 Write down *everything*. Even if you think it's not important. Make sure that
 more people than you have access to it. Give as much detail as you can to your
-service providers.
+service providers. Be prepared for sudden changes on the day of the event
 
 ## First Steps: Pre-planning (T-3 months)
 The absolute first thing you should do is write down what your event will be at
@@ -44,7 +44,7 @@ don't know, make sure they know that you'll be changing your answer later on.
 
 Pick one or two people to serve as the point(s) of contact with the reservation
 manager and any service providers. Make sure that all communication flows
-through them. I can't tell you how many times I've receive conflicting
+through them. I can't tell you how many times I've received conflicting
 information because the planning team all emailed different documents. It's so
 much easier to just have one or two people giving the same information.
 
@@ -54,6 +54,7 @@ would go well with it? For each part, figure out:
 - If it needs any special materials or equipment
 	- If it does, who will be providing it?
 - Who will be in charge of making sure it happens
+- What needs to happen for this to be included
 
 Try not to overload yourself or your team with too many separate parts. Try to
 keep the total number of components to around 2 per planning team member. Any
@@ -63,7 +64,7 @@ Your event should have a way for all volunteers to see the status of tasks
 across the whole event and filter to certain parts. As tasks are completed, the
 task owner should update the status and close it out. You can use a Trello
 board, a spreadsheet, or anything else that might help you keep track of
-everything.
+everything. When I planned my FLL qualifier, myself and the rest of the event team had a Google Sheet that we would use to keep track of everything, with columns for the task, who it was assigned to, and when it was completed. We used the same sheet for every stage of the planning and execution process, with different tabs for "Pre-Event Tasks", "Event Setup", and "Post-Event Tasks". We also tracked the volunteers we had assigned to roles here.
 
 This is the proper time to reach out to any service providers you may need. If
 you need lighting or sound, figure out a good company or other organization that
@@ -99,6 +100,9 @@ little bit, gather your planning team again. Go through your lists of roses
 into a post-mortem and share it with the entire team. Keep it around, so that
 future teams can have a reference.
 
+This is not at all tailored for a specific kind of event, but it is experience gathered over my time working on both sides of events.
+
 [^1]: WPI Annual VEX Event
 [^2]: Lens and Lights - a WPI club providing lighting, sound, and projection
 services to the WPI community
+
diff --git a/blog/preparing-to-come-out.md b/blog/preparing-to-come-out.md
index 9c4af42..1af4c32 100644
--- a/blog/preparing-to-come-out.md
+++ b/blog/preparing-to-come-out.md
@@ -2,7 +2,7 @@
 title: "Preparing to Come Out"
 date: 2021-04-26
 series:
-  - coming-out
+ - coming-out
 ---
 
 I've written about changing your deadname with Git [before](/blog/2021/3/on-deadnames-and-git), but I haven't written about how to _come out_ to other people. I'm getting ready to go to college in the fall, so I'm continuing this series as I go through the steps to come out not just to my family, but to my college and friends.
diff --git a/blog/status-update-may.md b/blog/status-update-may.md
index 4dbe6d2..3e54026 100644
--- a/blog/status-update-may.md
+++ b/blog/status-update-may.md
@@ -1,7 +1,6 @@
 ---
 title: "Status Update: May 2020"
 date: 2020-05-18
-lastmod: 2020-05-18T16:04:30-04:00
 draft: false
 series:
     - status