From 3f811670189375319990a8684eb0b057868a875b Mon Sep 17 00:00:00 2001 From: "Brandon C. Irizarry" Date: Fri, 27 Feb 2026 10:39:14 -0500 Subject: Remove TOC from blog posts --- drafts/posts/smoothing-over-more-markdown-pain-points.md | 12 ------------ drafts/posts/understanding-pratt-parsing.md | 15 --------------- drafts/posts/writing-my-blog-with-eleventy.md | 14 -------------- 3 files changed, 41 deletions(-) (limited to 'drafts/posts') diff --git a/drafts/posts/smoothing-over-more-markdown-pain-points.md b/drafts/posts/smoothing-over-more-markdown-pain-points.md index ab87edb..ac853be 100644 --- a/drafts/posts/smoothing-over-more-markdown-pain-points.md +++ b/drafts/posts/smoothing-over-more-markdown-pain-points.md @@ -12,15 +12,6 @@ generating a table of contents for a Markdown file. +++ -# Table of Contents - -+ [I Couldn't Keep It Together](#i-couldn't-keep-it-together) -+ [Elisp For The Win](#elisp-for-the-win) -+ [Yet Another Yasnippet Testimonial](#yet-another-yasnippet-testimonial) -+ [Now I Can Keep It Together!](#now-i-can-keep-it-together!) - - - # I Couldn't Keep It Together As I go about editing these blogs as Markdown buffers inside Emacs, @@ -35,7 +26,6 @@ on—is a pain. And so I came up with a way to sync the two, using Emacs Lisp. Emacs Lisp, or Elisp for short, is the Emacs editor's extension language: the language you use to write Emacs plugins. - # Elisp For The Win [Having written](https://brandonirizarry.xyz/blog/writing_my_blog_with_eleventy/#introduction) about my zany Elisp-based Java build system made me recall those times: I could once again rise to the challenge, and @@ -58,7 +48,6 @@ manage locally. I store it remotely, and install it as an *official* package, much like how Go packages work. In this way, I can even share my work with the community. - # Yet Another Yasnippet Testimonial I also decided to go the extra mile and use a [Yasnippet](Yasnippet) snippet @@ -70,7 +59,6 @@ to set up her `ox-hugo` front matter. In fact, this is what turned me on to the idea of Yasnippet as a useful tool in general; that is, it isn't just a lazy man's way of inserting a for-loop into source code. - # Now I Can Keep It Together! I now use table-of-contents regeneration frequently: writing the diff --git a/drafts/posts/understanding-pratt-parsing.md b/drafts/posts/understanding-pratt-parsing.md index 4c058fe..d88ba88 100644 --- a/drafts/posts/understanding-pratt-parsing.md +++ b/drafts/posts/understanding-pratt-parsing.md @@ -12,15 +12,6 @@ programming language I was designing at the time. +++ -# Table of Contents - -+ [Introduction](#introduction) -+ ["It's like a burrito"](#its-like-a-burrito) -+ [Down To Brass Tacks](#down-to-brass-tacks) -+ [Wanting More](#wanting-more) - - - # Introduction I've forgotten how I came across Pratt parsing specifically. I had @@ -47,8 +38,6 @@ are always used for application terms there.) This time though, I wanted to try something different. And so, rummaging through the internets, I stumbled across Pratt parsing. - - # "It's like a burrito" Understanding Pratt parsing ended up being much harder than I @@ -115,8 +104,6 @@ the current `level`, the while loop exits and `acc` is returned. The algorithm is initialized by calling `parse(0)`. - - # Down To Brass Tacks My approach was to take Eli Bendersky's full source code at the bottom @@ -138,8 +125,6 @@ say you have precedence levels `MULTIPLICATION = 2` and associativity for exponentiation. I found this to be one of the more remarkable aspects of the algorithm. - - # Wanting More To be fair, my calculator app technically doesn't parse arithmetic diff --git a/drafts/posts/writing-my-blog-with-eleventy.md b/drafts/posts/writing-my-blog-with-eleventy.md index c822446..dc78e51 100644 --- a/drafts/posts/writing-my-blog-with-eleventy.md +++ b/drafts/posts/writing-my-blog-with-eleventy.md @@ -12,16 +12,6 @@ since migrated to a custom engine. +++ -# Table of Contents - -+ [Introduction](#introduction) -+ [Hugo](#hugo) -+ [Eleventy: The Soup Actually Tastes Good](#eleventy:-the-soup-actually-tastes-good) -+ [Painless Deployment](#painless-deployment) -+ [Conclusion](#conclusion) - - - # Introduction This is *at least* my third time trying to start a blog. @@ -36,7 +26,6 @@ dependencies (defined by things like package imports and code syntax), so that those would get passed into `javac` along with the target file. - # Hugo I then started writing a blog using Hugo. Hugo was my first encounter with an SSG. Because of this, I was a bit impatient with Hugo, and hit @@ -54,7 +43,6 @@ and Hugo obfuscates the nature of Hugo, something I'm realizing now as I go deeper into using Eleventy. - # Eleventy: The Soup Actually Tastes Good I went ahead and did a little bit of "shopping" for SSGs. I ran into @@ -83,7 +71,6 @@ occurring within the same file—all somehow live under one roof. However, tweaking the starter project ended up being a relatively easy, even pleasant experience. - # Painless Deployment Even deployment is simple. This site's content is version-controlled @@ -94,7 +81,6 @@ with the new files. I don't need a GitHub workflow, as I did when using Hugo with GitHub pages; I don't even need to push to a remote repo. Copying the files suffices. - # Conclusion On the one hand, I'm nowhere near able to make something like the -- cgit v1.2.3