Add table of contents to old blogs

content/2024/01/17/post-01.md

@@ -2,7 +2,17 @@ Title: First blog post built with blag
 Description: Because every new blog needs a new post.
 Date: 2024-01-17 10:28
 Tags: personal, gitops, devops, technical
-Edited: 2024-01-18 00:18
+Edited: 2024-09-27 13:50
+
+# Table of Contents <!-- omit in toc -->
+
+- [A new post for a new blog](#a-new-post-for-a-new-blog)
+- [Fixing that old mess](#fixing-that-old-mess)
+- [Static Site Generation](#static-site-generation)
+  - [Using blag](#using-blag)
+  - [Automation](#automation)
+- [Conclusion](#conclusion)
+
 
 # A new post for a new blog
 
@@ -14,13 +24,13 @@ Previously, <https://blog.raer.me/> was an html-only website. The pages were cre
 
 That's terribly inconvenient. To boot, the thing wasn't version managed and it was deployed entirely manually directly to a folder on my reverse proxy server ([see more...](../../../2023/06/28/automating-some-things.md)) Yikes! None of this was ideal at all!
 
-## Fixing that old mess
+# Fixing that old mess
 
 So building the blog with html manually was a pain in the ass. But doing something like an MVC framework or a CMS for a simple blog seemed like too much hassle as well. I don't want a WYSIWYG, or something that's browser-based. I hate dealing with browser frontends. Afterall, a blog is mostly - if not *entirely* - text-based. Why should I have to deal with the overhead of a server-side scripted website? I just want to write my blog in markdown - like i do with all my documentation already. Then I could even keep it in a git repo, backed up to my private gitea instance.
 
 The answer to all of that, is `static site generation`. Turns out, there are plenty of other people out there who have looked at available tools, thought something similar to me, then built their own new tool that can take markdown, then generate a whole-ass website with it. Simple, and clean. You write content, maybe tweak some CSS/HTML templates, then the generator handles all the dirty work. No more searching for dozens of instances of a link when I change something in the navbar. That navbar is now a single template file that's reused by the generator.
 
-## Static Site Generation
+# Static Site Generation
 
 This all sounds very complicated, yes? Well, sure. But really, its not.
 
@@ -187,6 +197,8 @@ jobs:
 
 ```
 
+# Conclusion
+
 Bear in mind, this all required a bit of setup and learning to self-host. But, when the hosts & runners are all set up and running properly, with the above workflow, updating this blog is a simple matter of committing to a git repo then pushing it to my remote. The runners handle everything else.
 
 Ain't gitops grand?