From 77deda68beb468f2ba67c1eb2899f834de5ab317 Mon Sep 17 00:00:00 2001
From: bt <bt@btxx.org>
Date: Sat, 8 Jun 2024 11:56:18 -0400
Subject: Use openrsync for OpenBSD systems, alter README

---
 README.md                          |   7 +-
 barf                               |   1 +
 build/about/index.html             |   4 ++
 build/atom.xml                     | 127 +++++++++++++++++++++++++++++++++++--
 build/cleanup/index.html           |   9 +++
 build/dark-mode/index.html         |   8 +++
 build/index.html                   |  21 +++++-
 build/macos/index.html             |   7 ++
 build/markdown-examples/index.html |  81 ++++++++++++++++++++++-
 build/openbsd/index.html           |   6 ++
 build/qol/index.html               |  12 ++++
 build/rss.xml                      | 127 +++++++++++++++++++++++++++++++++++--
 build/websites/index.html          |   2 +
 index.md                           |   2 +-
 14 files changed, 397 insertions(+), 17 deletions(-)

diff --git a/README.md b/README.md
index 6fedcb2..e0275c1 100644
--- a/README.md
+++ b/README.md
@@ -55,12 +55,13 @@ https://barf.btxx.org/openbsd
 - coreutils
 - gcc
 - cmake
-- rsync
 - lowdown
 - gsed
 - entr (optional)
 
-    doas pkg_add coreutils gcc cmake rsync lowdown gsed
+Example:
+
+    doas pkg_add coreutils gcc cmake lowdown gsed
 
 macOS
 -----
@@ -74,6 +75,8 @@ https://barf.btxx.org/macos
 - lowdown
 - entr (optional)
 
+Example:
+
     brew install coreutils gnu-sed rsync lowdown
 
 basic setup
diff --git a/barf b/barf
index 10a92ca..4fae748 100755
--- a/barf
+++ b/barf
@@ -8,6 +8,7 @@ os_name=$(uname -s)
 if [ "$os_name" = "OpenBSD" ]; then
     alias sed=gsed
     alias date=gdate
+    alias rsync=openrsync
 elif [ "$os_name" = "Darwin" ]; then
     alias sed=gsed
     alias date=gdate
diff --git a/build/about/index.html b/build/about/index.html
index 698aa5c..860308b 100644
--- a/build/about/index.html
+++ b/build/about/index.html
@@ -16,9 +16,13 @@
 
 <main>
 <h1 id="about-">About <code>barf</code></h1>
+
 <p>barf is a minimal and suckless-inspired blog generator. It is a tweaked and slightly patched version of Karl Bartel&#8217;s fantastic <a href="https://github.com/karlb/karl.berlin">blog.sh</a>.</p>
+
 <h2 id="why">Why?</h2>
+
 <p>This project was created by me, <a href="https://btxx.org">Bradley Taunt</a>, out of frustration with overly complex and bloated blogging options. I tried <em>so many</em> &#8220;minimal&#8221; generators but each one ended up having some glaring issue or heavy reliance on dependencies. </p>
+
 <p>I wanted to have a system that I could easily replicate on any Linux machine. Something that didn&#8217;t require me to download half the internet just to get up and running. I&#8217;m a sucker for keeping things simple.</p>
 <footer role="contentinfo">
     <hr>
diff --git a/build/atom.xml b/build/atom.xml
index 145d5a8..a4148bf 100644
--- a/build/atom.xml
+++ b/build/atom.xml
@@ -2,34 +2,46 @@
 <feed xmlns="http://www.w3.org/2005/Atom">
 	<title>barf</title>
 	<link href="https://barf.btxx.org/atom.xml" rel="self" />
-	<updated>2024-06-07T10:26:51Z</updated>
+	<updated>2024-06-08T11:53:53Z</updated>
 	<author>
-		<name>Bradley Taunt</name>
+		<name></name>
 	</author>
 	<id>https://barf.btxx.org,2024-01-19:default-atom-feed/</id>
 	<entry>
 		<title>Quality of Life Improvements</title>
 		<content type="html">&lt;h1 id=&quot;quality-of-life-improvements&quot;&gt;Quality of Life Improvements&lt;/h1&gt;
+
 &lt;p&gt;2024-06-06&lt;/p&gt;
+
 &lt;p&gt;I haven&amp;#8217;t circled back to &lt;code&gt;barf&lt;/code&gt; in quite a bit of time, so I&amp;#8217;m happy to announce a small update mainly focused on quality of life improvements! I&amp;#8217;ll keep things brief and get right into the core changes:&lt;/p&gt;
+
 &lt;p&gt;&lt;strong&gt;Automatic detection of your operating system (supports Linux, macOS and OpenBSD currently)&lt;/strong&gt;&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;&lt;code&gt;barf&lt;/code&gt; now checks your current OS and sets aliases accordingly&lt;/li&gt;
 &lt;li&gt;this removes the need to hard-set your own aliases or run syslinks&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;&lt;strong&gt;Added a semantically valid RSS feed&lt;/strong&gt;&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;&lt;code&gt;barf&lt;/code&gt; initially launched with Atom support only, now a separate RSS feed is generated at build time&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;&lt;strong&gt;Removed hardcoded feed links from &lt;code&gt;header.html&lt;/code&gt;&lt;/strong&gt;&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;You now only need to set your main domain at the top of the core &lt;code&gt;barf&lt;/code&gt; file.&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;&lt;strong&gt;Swapped out &lt;code&gt;smu&lt;/code&gt; for &lt;code&gt;lowdown&lt;/code&gt;&lt;/strong&gt;&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;The default Markdown parser is now set to &lt;code&gt;lowdown&lt;/code&gt;. The original parser (&lt;code&gt;smu&lt;/code&gt;) is great, but I wanted to make the project simpler by avoiding users to clone and build a separate package.&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;That&amp;#8217;s it really! I&amp;#8217;ve also updated the original blog posts about setting up &lt;code&gt;barf&lt;/code&gt; on macOS and OpenBSD to reflect these changes.&lt;/p&gt;
+
 &lt;p&gt;Cheers!&lt;/p&gt;</content>
 		<link href="https://barf.btxx.org/qol"/>
 		<id>https://barf.btxx.org/qol</id>
@@ -39,12 +51,18 @@
 	<entry>
 		<title>Running `barf` on OpenBSD</title>
 		<content type="html">&lt;h1 id=&quot;running-on-openbsd&quot;&gt;Running &lt;code&gt;barf&lt;/code&gt; on OpenBSD&lt;/h1&gt;
+
 &lt;p&gt;2023-08-12&lt;/p&gt;
+
 &lt;p&gt;The &lt;code&gt;barf&lt;/code&gt; project was built on Linux and was catered towards Linux users. The core of the project will remain focused on Linux&amp;#47;GNU tools, but I also need to support OpenBSD since that is my personal operating system of choice.&lt;/p&gt;
+
 &lt;h2 id=&quot;download-packages&quot;&gt;Download Packages&lt;/h2&gt;
+
 &lt;p&gt;Along with your Markdown parser of choice (&lt;code&gt;barf&lt;/code&gt; assumes you will be using my version of &lt;a href=&quot;https://git.sr.ht/~bt/smu&quot;&gt;smu&lt;/a&gt;) you will also need to install the required packages on your OpenBSD system:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;doas pkg_add rsync coreutils gsed cmake gcc
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;After that, everything should work perfectly fine when building!&lt;/p&gt;</content>
 		<link href="https://barf.btxx.org/openbsd"/>
 		<id>https://barf.btxx.org/openbsd</id>
@@ -54,12 +72,17 @@
 	<entry>
 		<title>Markdown Examples in barf</title>
 		<content type="html">&lt;h1 id=&quot;markdown-examples-in-barf&quot;&gt;Markdown Examples in barf&lt;/h1&gt;
+
 &lt;p&gt;2023-01-05&lt;/p&gt;
+
 &lt;p&gt;This following was lifted from &lt;a href=&quot;https://github.com/karlb/smu&quot;&gt;https:&amp;#47;&amp;#47;github.com&amp;#47;karlb&amp;#47;smu&lt;/a&gt;&lt;/p&gt;
+
 &lt;h1 id=&quot;syntax&quot;&gt;&lt;code&gt;smu&lt;/code&gt; Syntax&lt;/h1&gt;
+
 &lt;p&gt;smu was started as a rewrite of
 &lt;a href=&quot;http://daringfireball.net/projects/markdown/&quot;&gt;markdown&lt;/a&gt; but became something
 more lightweight and consistent. It differs from &lt;a href=&quot;https://commonmark.org/&quot;&gt;CommonMark&lt;/a&gt; in the following ways:&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;No support for &lt;em&gt;reference style links&lt;/em&gt;&lt;/li&gt;
 &lt;li&gt;Stricter indentation rules for lists&lt;/li&gt;
@@ -67,13 +90,17 @@ more lightweight and consistent. It differs from &lt;a href=&quot;https://common
 &lt;li&gt;Horizontal rules (&lt;code&gt;&amp;#60;hr&amp;#62;&lt;/code&gt;) must use &lt;code&gt;- - -&lt;/code&gt; as syntax&lt;/li&gt;
 &lt;li&gt;Code fences have stricter syntax&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;Patches that increase the CommonMark compatibility are welcome as long as they don&amp;#8217;t increase the code complexity significantly.&lt;/p&gt;
+
 &lt;p&gt;This project is a fork of the &lt;a href=&quot;https://github.com/gottox/smu&quot;&gt;original smu&lt;/a&gt; by
 &lt;a href=&quot;https://eboland.de&quot;&gt;Enno Boland (gottox)&lt;/a&gt;. The main differences to the
 original smu are:&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;Support for code fences&lt;/li&gt;
 &lt;li&gt;Improved &lt;a href=&quot;https://commonmark.org/&quot;&gt;CommonMark&lt;/a&gt; compatibility. E.g.
+
 &lt;ul&gt;
 &lt;li&gt;Code blocks need four spaces indentation instead of three&lt;/li&gt;
 &lt;li&gt;Skip empty lines at end of code blocks&lt;/li&gt;
@@ -87,10 +114,14 @@ original smu are:&lt;/p&gt;
 &lt;/ul&gt;&lt;/li&gt;
 &lt;li&gt;Added a simple test suite to check for compliance and avoid regressions&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;h2 id=&quot;inline-patterns&quot;&gt;Inline patterns&lt;/h2&gt;
+
 &lt;p&gt;There are several patterns you can use to highlight your text:&lt;/p&gt;
+
 &lt;ul&gt;
-&lt;li&gt;&lt;p&gt;Emphasis
+&lt;li&gt;&lt;p&gt;Emphasis&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;Surround your text with &lt;code&gt;*&lt;/code&gt; or &lt;code&gt;_&lt;/code&gt; to get &lt;em&gt;emphasised&lt;/em&gt; text:
 This &lt;em&gt;is&lt;/em&gt; cool.
@@ -106,29 +137,39 @@ This &lt;strong&gt;&lt;em&gt;is&lt;/em&gt;&lt;/strong&gt; cool, too.&lt;/li&gt;
 This is a wontfix bug because it would make the source too complex.
 Use this instead:
 &lt;strong&gt;&lt;em&gt;Hello&lt;/em&gt;&lt;/strong&gt; &lt;em&gt;you&lt;/em&gt;&lt;/li&gt;
-&lt;/ul&gt;&lt;/p&gt;&lt;/li&gt;
+&lt;/ul&gt;&lt;/li&gt;
 &lt;li&gt;&lt;p&gt;inline Code&lt;/p&gt;
+
 &lt;p&gt;You can produce inline code by surrounding it with backticks.&lt;/p&gt;
+
 &lt;p&gt;Use &lt;code&gt;rm -rf &amp;#47;&lt;/code&gt; if you&amp;#8217;re a N00b.
 Use &lt;code&gt;rm -rf &amp;#47;&lt;/code&gt; if you&amp;#8217;re a N00b.
 Use &lt;code&gt;rm -rf &amp;#47;&lt;/code&gt; if you&amp;#8217;re a N00b.&lt;/p&gt;
+
 &lt;p&gt;Double and triple backticks can be used if the code itself contains backticks.&lt;/p&gt;&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;h2 id=&quot;titles&quot;&gt;Titles&lt;/h2&gt;
+
 &lt;p&gt;Creating titles in smu is very easy. There are two different syntax styles. The
 first is underlining with at least three characters:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;Heading
 =======
 
 Topic
 -----
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;This is very intuitive and self explaining. The resulting sourcecode looks like
 this:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;h1&amp;#62;Heading&amp;#60;&amp;#47;h1&amp;#62;
 &amp;#60;h2&amp;#62;Topic&amp;#60;&amp;#47;h2&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Use the following prefixes if you don&amp;#8217;t like underlining:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;# h1
 ## h2
 ### h3
@@ -136,127 +177,179 @@ this:&lt;/p&gt;
 ##### h5
 ###### h6
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;h2 id=&quot;links&quot;&gt;Links&lt;/h2&gt;
+
 &lt;p&gt;The simplest way to define a link is with simple &lt;code&gt;&amp;#60;&amp;#62;&lt;/code&gt;.&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;http:&amp;#47;&amp;#47;s01.de&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;You can do the same for E-Mail addresses:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;yourname@s01.de&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;If you want to define a label for the url, you have to use a different syntax&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;[smu - simple mark up](http:&amp;#47;&amp;#47;s01.de&amp;#47;~gottox&amp;#47;index.cgi&amp;#47;proj_smu)
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;The resulting HTML-Code&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;a href=&quot;http:&amp;#47;&amp;#47;s01.de&amp;#47;~gottox&amp;#47;index.cgi&amp;#47;proj_smu&quot;&amp;#62;smu - simple mark up&amp;#60;&amp;#47;a&amp;#62;&amp;#60;&amp;#47;p&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;h2 id=&quot;lists&quot;&gt;Lists&lt;/h2&gt;
+
 &lt;p&gt;Defining lists is very straightforward:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;* Item 1
 * Item 2
 * Item 3
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Result:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;ul&amp;#62;
 &amp;#60;li&amp;#62;Item 1&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;li&amp;#62;Item 2&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;li&amp;#62;Item 3&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;&amp;#47;ul&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Defining ordered lists is also very easy:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;1. Item 1
 2. Item 2
 3. Item 3
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Only the first number in a list is meaningful. All following list items are
 continously counted. If you want a list starting at 2, you could write:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;2. Item 1
 2. Item 2
 2. Item 3
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;and get the following HTML which will render with the numbers 2, 3, 4:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;ol start=&quot;2&quot;&amp;#62;
 &amp;#60;li&amp;#62;Item 1&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;li&amp;#62;Item 2&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;li&amp;#62;Item 3&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;&amp;#47;ol&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;h2 id=&quot;code-blockquote&quot;&gt;Code &amp;#38; Blockquote&lt;/h2&gt;
+
 &lt;p&gt;Use the &lt;code&gt;&amp;#62;&lt;/code&gt; as a line prefix for defining blockquotes. Blockquotes are
 interpreted as well. This makes it possible to embed links, headings and even
 other quotes into a quote:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#62; Hello
 &amp;#62; This is a quote with a [link](http:&amp;#47;&amp;#47;s01.de&amp;#47;~gottox)
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Result:
     
     Hello
     This is a quote with a link
     &lt;/p&gt;
+
 &lt;p&gt;You can define a code block with a leading Tab or with &lt;strong&gt;4&lt;/strong&gt; leading spaces&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;    this.is(code)
 
     this.is(code, too)
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Result:
     this.is(code)
     this.is(code, too)
     &lt;/p&gt;
+
 &lt;p&gt;Please note that you can&amp;#8217;t use HTML or smu syntax in a code block.&lt;/p&gt;
+
 &lt;p&gt;Another way to write code blocks is to use code fences:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;```json
 {&quot;some&quot;: &quot;code&quot;}
 ```
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;This has two advantages:
 * The optional language identifier will be turned into a &lt;code&gt;language-&lt;/code&gt; class name
 * You can keep the original indentation which helps when doing copy &amp;#38; paste&lt;/p&gt;
+
 &lt;h2 id=&quot;tables&quot;&gt;Tables&lt;/h2&gt;
+
 &lt;p&gt;Tables can be generated with the following syntax:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;| Heading1 | Heading2 |
 | -------- | -------- |
 | Cell 1   | Cell2    |
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Aligning the columns make the input nicer to read, but is not necessary to get
 correct table output. You could just write&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;| Heading1 | Heading2 |
 | --- | --- |
 | Cell 1 | Cell2 |
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;To align the content of table cells, use &lt;code&gt;|:--|&lt;/code&gt; for left, &lt;code&gt;|--:|&lt;/code&gt; for right
 and &lt;code&gt;|:--:|&lt;/code&gt; for centered alignment in the row which separates the header from
 the table body.&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;| Heading1 | Heading2 | Heading3 |
 | :------- | :------: | -------: |
 | Left     | Center   | Right    |
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;h2 id=&quot;footnotes&quot;&gt;Footnotes&lt;/h2&gt;
+
 &lt;p&gt;Here is an example of using Markdown footnotes&lt;sup id=&quot;fnref1&quot;&gt;&lt;a href=&quot;#fn1&quot; rel=&quot;footnote&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;. And incase you were looking for more examples, here is another one&lt;sup id=&quot;fnref2&quot;&gt;&lt;a href=&quot;#fn2&quot; rel=&quot;footnote&quot;&gt;2&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
+
 &lt;h2 id=&quot;other-interesting-stuff&quot;&gt;Other interesting stuff&lt;/h2&gt;
+
 &lt;ul&gt;
 &lt;li&gt;&lt;p&gt;to insert a horizontal rule simple add &lt;code&gt;- - -&lt;/code&gt; into an empty line:&lt;/p&gt;
+
 &lt;p&gt;Hello&lt;/p&gt;
+
 &lt;hr/&gt;
+
 &lt;p&gt;Hello2&lt;/p&gt;
+
 &lt;p&gt;Result:
 
 Hello
 &lt;/p&gt;
+
 &lt;p&gt;Hello2&lt;/p&gt;&lt;/li&gt;
 &lt;li&gt;&lt;p&gt;Any ASCII punctuation character may escaped by precedeing them with a
 backslash to avoid them being interpreted:&lt;/p&gt;
-&lt;p&gt;!&amp;#8221;#$%&amp;#38;&amp;#8217;()*+,-.&amp;#47;:;&amp;#60;=&amp;#62;?@[]^_`{|}~\&lt;/p&gt;&lt;/li&gt;
+
+&lt;p&gt;!&amp;#8221;#$%&amp;#38;&amp;#8217;()*+,-.&amp;#47;:;&amp;#60;=&amp;#62;?@[]&lt;sup&gt;_`{|}~\&lt;/sup&gt;&lt;/p&gt;&lt;/li&gt;
 &lt;li&gt;&lt;p&gt;To force a linebreak simple add two spaces to the end of the line:&lt;/p&gt;
+
 &lt;p&gt;No linebreak
 here.
 But here is&lt;br/&gt;
 one.&lt;/p&gt;&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;h2 id=&quot;embed-html&quot;&gt;embed HTML&lt;/h2&gt;
+
 &lt;p&gt;You can include arbitrary HTML code in your documents. The HTML will be
 passed through to the resulting document without modification. This is a good
 way to work around features that are missing in smu. If you don&amp;#8217;t want this
 behaviour, use the &lt;code&gt;-n&lt;/code&gt; flag when executing smu to stricly escape the HTML
 tags.&lt;/p&gt;
+
 &lt;div class=&quot;footnotes&quot;&gt;
 &lt;hr/&gt;
 &lt;ol&gt;
@@ -279,14 +372,21 @@ tags.&lt;/p&gt;
 	<entry>
 		<title>Running `barf` on MacOS</title>
 		<content type="html">&lt;h1 id=&quot;running-on-macos&quot;&gt;Running &lt;code&gt;barf&lt;/code&gt; on MacOS&lt;/h1&gt;
+
 &lt;p&gt;2023-01-18&lt;/p&gt;
+
 &lt;p&gt;The &lt;code&gt;barf&lt;/code&gt; project was built on Linux and was catered towards Linux users. The core of the project will remain focused on Linux&amp;#47;GNU tools, but that doesn&amp;#8217;t mean MacOS needs to be left out in the cold.&lt;/p&gt;
+
 &lt;h2 id=&quot;download-packages&quot;&gt;Download Packages&lt;/h2&gt;
+
 &lt;p&gt;This walkthrough assumes that you already have &lt;a href=&quot;https://brew.sh/&quot;&gt;homebrew&lt;/a&gt; installed on your machine.&lt;/p&gt;
+
 &lt;p&gt;You will need to install the GNU versions of both &lt;code&gt;date&lt;/code&gt; and &lt;code&gt;sed&lt;/code&gt; in order to avoid breaking things when &lt;code&gt;barf&lt;/code&gt; tries to build.&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;brew install coreutils
 brew install gnu-sed
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Now everything should work as intended!&lt;/p&gt;</content>
 		<link href="https://barf.btxx.org/macos"/>
 		<id>https://barf.btxx.org/macos</id>
@@ -296,16 +396,24 @@ brew install gnu-sed
 	<entry>
 		<title>Supporting Basic Dark Mode</title>
 		<content type="html">&lt;h1 id=&quot;supporting-basic-dark-mode&quot;&gt;Supporting Basic Dark Mode&lt;/h1&gt;
+
 &lt;p&gt;2023-03-07&lt;/p&gt;
+
 &lt;p&gt;The default &lt;code&gt;barf&lt;/code&gt; site generator now supports basic dark mode functionality. This has been achieved by including the standard &lt;code&gt;color-scheme&lt;/code&gt; meta tag in the core &lt;code&gt;header.html&lt;/code&gt; file:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;meta name=&quot;color-scheme&quot; content=&quot;dark light&quot;&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;This change also ships with some minor updates to the default &lt;code&gt;blockquote&lt;/code&gt; design. You can see an example below:&lt;/p&gt;
+
 &lt;blockquote&gt;
 &lt;p&gt;This is a really &lt;em&gt;cool&lt;/em&gt; blockquote&lt;/p&gt;
 &lt;/blockquote&gt;
+
 &lt;h2 id=&quot;minor-caveat&quot;&gt;Minor Caveat&lt;/h2&gt;
+
 &lt;p&gt;Unfortunately, Safari still has minor &lt;code&gt;ahref&lt;/code&gt; &amp;#47; link color issue when defaulting to browser dark mode. If this is a problem for your own build of &lt;code&gt;barf&lt;/code&gt;, take a look at a &lt;a href=&quot;https://bt.ht/safari-default-dark-mode/&quot;&gt;solution I wrote about here&lt;/a&gt;.&lt;/p&gt;
+
 &lt;p&gt;Personally, I can&amp;#8217;t be bothered to add that extra code to this project. The Safari team needs to get their shit together and fix such a simple bug. Plus, you shouldn&amp;#8217;t be using Safari anyway - it&amp;#8217;s proprietary garbage.&lt;/p&gt;</content>
 		<link href="https://barf.btxx.org/dark-mode"/>
 		<id>https://barf.btxx.org/dark-mode</id>
@@ -315,22 +423,31 @@ brew install gnu-sed
 	<entry>
 		<title>Cleaning Up barf's Structure</title>
 		<content type="html">&lt;h1 id=&quot;cleaning-up-barfs-structure&quot;&gt;Cleaning Up barf&amp;#8217;s Structure&lt;/h1&gt;
+
 &lt;p&gt;2023-10-09&lt;/p&gt;
+
 &lt;p&gt;Things probably look a little different around here. Both in terms of this demo site &lt;em&gt;and&lt;/em&gt; the core &lt;code&gt;barf&lt;/code&gt; files itself.&lt;/p&gt;
+
 &lt;p&gt;This project was always intended to be focused on Linux platforms. So, I&amp;#8217;ve removed the included &lt;code&gt;barf_macos&lt;/code&gt; and &lt;code&gt;barf_openbsd&lt;/code&gt; files to keep the generator more streamlined. But have no fear! Instructions for both Mac and OpenBSD can still be found on the main blog:&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;&lt;a href=&quot;/macos&quot;&gt;Running &lt;code&gt;barf&lt;/code&gt; on MacOS&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href=&quot;/openbsd&quot;&gt;Running &lt;code&gt;barf&lt;/code&gt; on OpenBSD&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;As for the &amp;#8220;default&amp;#8221; look of &lt;code&gt;barf&lt;/code&gt;, I&amp;#8217;ve simplified things further. The total CSS styling now consists of only:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;*{box-sizing:border-box;}
 body{font-family:sans-serif;margin:0 auto;max-width:650px;padding:1rem;}
 img{max-width:100%;}
 pre{overflow:auto;}
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Users still have the ability to tweak things as much as they&amp;#8217;d like, but the standard look should be more than enough for anyone just focusing on writing. Dark mode has also been dropped but is easily added by adding the following inside the &lt;code&gt;head&lt;/code&gt; tags:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;meta name=&quot;color-scheme&quot; content=&quot;dark light&quot;&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Hopefully these changes reduce the overall scope of the project, which was a main point made on the README originally!&lt;/p&gt;</content>
 		<link href="https://barf.btxx.org/cleanup"/>
 		<id>https://barf.btxx.org/cleanup</id>
diff --git a/build/cleanup/index.html b/build/cleanup/index.html
index b567bac..b34599b 100644
--- a/build/cleanup/index.html
+++ b/build/cleanup/index.html
@@ -16,22 +16,31 @@
 
 <main>
 <h1 id="cleaning-up-barfs-structure">Cleaning Up barf&#8217;s Structure</h1>
+
 <p>2023-10-09</p>
+
 <p>Things probably look a little different around here. Both in terms of this demo site <em>and</em> the core <code>barf</code> files itself.</p>
+
 <p>This project was always intended to be focused on Linux platforms. So, I&#8217;ve removed the included <code>barf_macos</code> and <code>barf_openbsd</code> files to keep the generator more streamlined. But have no fear! Instructions for both Mac and OpenBSD can still be found on the main blog:</p>
+
 <ul>
 <li><a href="/macos">Running <code>barf</code> on MacOS</a></li>
 <li><a href="/openbsd">Running <code>barf</code> on OpenBSD</a></li>
 </ul>
+
 <p>As for the &#8220;default&#8221; look of <code>barf</code>, I&#8217;ve simplified things further. The total CSS styling now consists of only:</p>
+
 <pre><code>*{box-sizing:border-box;}
 body{font-family:sans-serif;margin:0 auto;max-width:650px;padding:1rem;}
 img{max-width:100%;}
 pre{overflow:auto;}
 </code></pre>
+
 <p>Users still have the ability to tweak things as much as they&#8217;d like, but the standard look should be more than enough for anyone just focusing on writing. Dark mode has also been dropped but is easily added by adding the following inside the <code>head</code> tags:</p>
+
 <pre><code>&#60;meta name="color-scheme" content="dark light"&#62;
 </code></pre>
+
 <p>Hopefully these changes reduce the overall scope of the project, which was a main point made on the README originally!</p>
 <footer role="contentinfo">
     <hr>
diff --git a/build/dark-mode/index.html b/build/dark-mode/index.html
index 02c75f0..1e4d183 100644
--- a/build/dark-mode/index.html
+++ b/build/dark-mode/index.html
@@ -16,16 +16,24 @@
 
 <main>
 <h1 id="supporting-basic-dark-mode">Supporting Basic Dark Mode</h1>
+
 <p>2023-03-07</p>
+
 <p>The default <code>barf</code> site generator now supports basic dark mode functionality. This has been achieved by including the standard <code>color-scheme</code> meta tag in the core <code>header.html</code> file:</p>
+
 <pre><code>&#60;meta name="color-scheme" content="dark light"&#62;
 </code></pre>
+
 <p>This change also ships with some minor updates to the default <code>blockquote</code> design. You can see an example below:</p>
+
 <blockquote>
 <p>This is a really <em>cool</em> blockquote</p>
 </blockquote>
+
 <h2 id="minor-caveat">Minor Caveat</h2>
+
 <p>Unfortunately, Safari still has minor <code>ahref</code> &#47; link color issue when defaulting to browser dark mode. If this is a problem for your own build of <code>barf</code>, take a look at a <a href="https://bt.ht/safari-default-dark-mode/">solution I wrote about here</a>.</p>
+
 <p>Personally, I can&#8217;t be bothered to add that extra code to this project. The Safari team needs to get their shit together and fix such a simple bug. Plus, you shouldn&#8217;t be using Safari anyway - it&#8217;s proprietary garbage.</p>
 <footer role="contentinfo">
     <hr>
diff --git a/build/index.html b/build/index.html
index c04b05b..69197cd 100644
--- a/build/index.html
+++ b/build/index.html
@@ -16,33 +16,52 @@
 
 <main>
 <h1 id="barf">barf</h1>
+
 <p><strong>barf is an extremely minimal blog generator.</strong></p>
+
 <p>The entire build script is &#62;170 lines of shell.</p>
+
 <p>It could almost be called &#8220;suckless&#8221;, but probably isn&#8217;t. It was created for those focused on writing, not tinkering.</p>
+
 <p>You can learn more by reading the <a href="https://git.btxx.org/barf/about">official README</a>.</p>
+
 <p><strong>barf</strong> = blogs are really fun</p>
+
 <hr/>
+
 <h3 id="get-setup-in-2-minutes">Get setup in 2 minutes</h3>
+
 <p><strong>Install dependencies:</strong></p>
+
 <p>For Linux (Alpine example):</p>
+
 <pre><code>sudo apk add rsync lowdown
 </code></pre>
+
 <p>For macOS:</p>
+
 <pre><code>brew install rsync lowdown coreutils gnu-sed
 </code></pre>
+
 <p>For OpenBSD:</p>
-<pre><code>doas pkg_add rsync lowdown coreutils gsed cmake gcc
+
+<pre><code>doas pkg_add lowdown coreutils gsed cmake gcc
 </code></pre>
+
 <p><strong>Clone barf:</strong> </p>
+
 <pre><code>git clone https:&#47;&#47;git.btxx.org&#47;barf
 </code></pre>
+
 <ol>
 <li>Open project, change the <code>domain</code> variable at the top of the core barf file</li>
 <li>Run: <code>make build</code></li>
 <li>Upload the contents of <code>build</code> to your server! </li>
 <li>Profit?</li>
 </ol>
+
 <hr/>
+
 <h3 id="articles">Articles</h3>
 <ul>
 <li>2024-06-06 &middot; <a href="qol/">Quality of Life Improvements</a></li>
diff --git a/build/macos/index.html b/build/macos/index.html
index 40ed9a8..34bbee1 100644
--- a/build/macos/index.html
+++ b/build/macos/index.html
@@ -16,14 +16,21 @@
 
 <main>
 <h1 id="running-on-macos">Running <code>barf</code> on MacOS</h1>
+
 <p>2023-01-18</p>
+
 <p>The <code>barf</code> project was built on Linux and was catered towards Linux users. The core of the project will remain focused on Linux&#47;GNU tools, but that doesn&#8217;t mean MacOS needs to be left out in the cold.</p>
+
 <h2 id="download-packages">Download Packages</h2>
+
 <p>This walkthrough assumes that you already have <a href="https://brew.sh/">homebrew</a> installed on your machine.</p>
+
 <p>You will need to install the GNU versions of both <code>date</code> and <code>sed</code> in order to avoid breaking things when <code>barf</code> tries to build.</p>
+
 <pre><code>brew install coreutils
 brew install gnu-sed
 </code></pre>
+
 <p>Now everything should work as intended!</p>
 <footer role="contentinfo">
     <hr>
diff --git a/build/markdown-examples/index.html b/build/markdown-examples/index.html
index 44f972e..25683ea 100644
--- a/build/markdown-examples/index.html
+++ b/build/markdown-examples/index.html
@@ -16,12 +16,17 @@
 
 <main>
 <h1 id="markdown-examples-in-barf">Markdown Examples in barf</h1>
+
 <p>2023-01-05</p>
+
 <p>This following was lifted from <a href="https://github.com/karlb/smu">https:&#47;&#47;github.com&#47;karlb&#47;smu</a></p>
+
 <h1 id="syntax"><code>smu</code> Syntax</h1>
+
 <p>smu was started as a rewrite of
 <a href="http://daringfireball.net/projects/markdown/">markdown</a> but became something
 more lightweight and consistent. It differs from <a href="https://commonmark.org/">CommonMark</a> in the following ways:</p>
+
 <ul>
 <li>No support for <em>reference style links</em></li>
 <li>Stricter indentation rules for lists</li>
@@ -29,13 +34,17 @@ more lightweight and consistent. It differs from <a href="https://commonmark.org
 <li>Horizontal rules (<code>&#60;hr&#62;</code>) must use <code>- - -</code> as syntax</li>
 <li>Code fences have stricter syntax</li>
 </ul>
+
 <p>Patches that increase the CommonMark compatibility are welcome as long as they don&#8217;t increase the code complexity significantly.</p>
+
 <p>This project is a fork of the <a href="https://github.com/gottox/smu">original smu</a> by
 <a href="https://eboland.de">Enno Boland (gottox)</a>. The main differences to the
 original smu are:</p>
+
 <ul>
 <li>Support for code fences</li>
 <li>Improved <a href="https://commonmark.org/">CommonMark</a> compatibility. E.g.
+
 <ul>
 <li>Code blocks need four spaces indentation instead of three</li>
 <li>Skip empty lines at end of code blocks</li>
@@ -49,10 +58,14 @@ original smu are:</p>
 </ul></li>
 <li>Added a simple test suite to check for compliance and avoid regressions</li>
 </ul>
+
 <h2 id="inline-patterns">Inline patterns</h2>
+
 <p>There are several patterns you can use to highlight your text:</p>
+
 <ul>
-<li><p>Emphasis
+<li><p>Emphasis</p>
+
 <ul>
 <li>Surround your text with <code>*</code> or <code>_</code> to get <em>emphasised</em> text:
 This <em>is</em> cool.
@@ -68,29 +81,39 @@ This <strong><em>is</em></strong> cool, too.</li>
 This is a wontfix bug because it would make the source too complex.
 Use this instead:
 <strong><em>Hello</em></strong> <em>you</em></li>
-</ul></p></li>
+</ul></li>
 <li><p>inline Code</p>
+
 <p>You can produce inline code by surrounding it with backticks.</p>
+
 <p>Use <code>rm -rf &#47;</code> if you&#8217;re a N00b.
 Use <code>rm -rf &#47;</code> if you&#8217;re a N00b.
 Use <code>rm -rf &#47;</code> if you&#8217;re a N00b.</p>
+
 <p>Double and triple backticks can be used if the code itself contains backticks.</p></li>
 </ul>
+
 <h2 id="titles">Titles</h2>
+
 <p>Creating titles in smu is very easy. There are two different syntax styles. The
 first is underlining with at least three characters:</p>
+
 <pre><code>Heading
 =======
 
 Topic
 -----
 </code></pre>
+
 <p>This is very intuitive and self explaining. The resulting sourcecode looks like
 this:</p>
+
 <pre><code>&#60;h1&#62;Heading&#60;&#47;h1&#62;
 &#60;h2&#62;Topic&#60;&#47;h2&#62;
 </code></pre>
+
 <p>Use the following prefixes if you don&#8217;t like underlining:</p>
+
 <pre><code># h1
 ## h2
 ### h3
@@ -98,127 +121,179 @@ this:</p>
 ##### h5
 ###### h6
 </code></pre>
+
 <h2 id="links">Links</h2>
+
 <p>The simplest way to define a link is with simple <code>&#60;&#62;</code>.</p>
+
 <pre><code>&#60;http:&#47;&#47;s01.de&#62;
 </code></pre>
+
 <p>You can do the same for E-Mail addresses:</p>
+
 <pre><code>&#60;yourname@s01.de&#62;
 </code></pre>
+
 <p>If you want to define a label for the url, you have to use a different syntax</p>
+
 <pre><code>[smu - simple mark up](http:&#47;&#47;s01.de&#47;~gottox&#47;index.cgi&#47;proj_smu)
 </code></pre>
+
 <p>The resulting HTML-Code</p>
+
 <pre><code>&#60;a href="http:&#47;&#47;s01.de&#47;~gottox&#47;index.cgi&#47;proj_smu"&#62;smu - simple mark up&#60;&#47;a&#62;&#60;&#47;p&#62;
 </code></pre>
+
 <h2 id="lists">Lists</h2>
+
 <p>Defining lists is very straightforward:</p>
+
 <pre><code>* Item 1
 * Item 2
 * Item 3
 </code></pre>
+
 <p>Result:</p>
+
 <pre><code>&#60;ul&#62;
 &#60;li&#62;Item 1&#60;&#47;li&#62;
 &#60;li&#62;Item 2&#60;&#47;li&#62;
 &#60;li&#62;Item 3&#60;&#47;li&#62;
 &#60;&#47;ul&#62;
 </code></pre>
+
 <p>Defining ordered lists is also very easy:</p>
+
 <pre><code>1. Item 1
 2. Item 2
 3. Item 3
 </code></pre>
+
 <p>Only the first number in a list is meaningful. All following list items are
 continously counted. If you want a list starting at 2, you could write:</p>
+
 <pre><code>2. Item 1
 2. Item 2
 2. Item 3
 </code></pre>
+
 <p>and get the following HTML which will render with the numbers 2, 3, 4:</p>
+
 <pre><code>&#60;ol start="2"&#62;
 &#60;li&#62;Item 1&#60;&#47;li&#62;
 &#60;li&#62;Item 2&#60;&#47;li&#62;
 &#60;li&#62;Item 3&#60;&#47;li&#62;
 &#60;&#47;ol&#62;
 </code></pre>
+
 <h2 id="code-blockquote">Code &#38; Blockquote</h2>
+
 <p>Use the <code>&#62;</code> as a line prefix for defining blockquotes. Blockquotes are
 interpreted as well. This makes it possible to embed links, headings and even
 other quotes into a quote:</p>
+
 <pre><code>&#62; Hello
 &#62; This is a quote with a [link](http:&#47;&#47;s01.de&#47;~gottox)
 </code></pre>
+
 <p>Result:
     
     Hello
     This is a quote with a link
     </p>
+
 <p>You can define a code block with a leading Tab or with <strong>4</strong> leading spaces</p>
+
 <pre><code>    this.is(code)
 
     this.is(code, too)
 </code></pre>
+
 <p>Result:
     this.is(code)
     this.is(code, too)
     </p>
+
 <p>Please note that you can&#8217;t use HTML or smu syntax in a code block.</p>
+
 <p>Another way to write code blocks is to use code fences:</p>
+
 <pre><code>```json
 {"some": "code"}
 ```
 </code></pre>
+
 <p>This has two advantages:
 * The optional language identifier will be turned into a <code>language-</code> class name
 * You can keep the original indentation which helps when doing copy &#38; paste</p>
+
 <h2 id="tables">Tables</h2>
+
 <p>Tables can be generated with the following syntax:</p>
+
 <pre><code>| Heading1 | Heading2 |
 | -------- | -------- |
 | Cell 1   | Cell2    |
 </code></pre>
+
 <p>Aligning the columns make the input nicer to read, but is not necessary to get
 correct table output. You could just write</p>
+
 <pre><code>| Heading1 | Heading2 |
 | --- | --- |
 | Cell 1 | Cell2 |
 </code></pre>
+
 <p>To align the content of table cells, use <code>|:--|</code> for left, <code>|--:|</code> for right
 and <code>|:--:|</code> for centered alignment in the row which separates the header from
 the table body.</p>
+
 <pre><code>| Heading1 | Heading2 | Heading3 |
 | :------- | :------: | -------: |
 | Left     | Center   | Right    |
 </code></pre>
+
 <h2 id="footnotes">Footnotes</h2>
+
 <p>Here is an example of using Markdown footnotes<sup id="fnref1"><a href="#fn1" rel="footnote">1</a></sup>. And incase you were looking for more examples, here is another one<sup id="fnref2"><a href="#fn2" rel="footnote">2</a></sup>.</p>
+
 <h2 id="other-interesting-stuff">Other interesting stuff</h2>
+
 <ul>
 <li><p>to insert a horizontal rule simple add <code>- - -</code> into an empty line:</p>
+
 <p>Hello</p>
+
 <hr/>
+
 <p>Hello2</p>
+
 <p>Result:
 
 Hello
 </p>
+
 <p>Hello2</p></li>
 <li><p>Any ASCII punctuation character may escaped by precedeing them with a
 backslash to avoid them being interpreted:</p>
-<p>!&#8221;#$%&#38;&#8217;()*+,-.&#47;:;&#60;=&#62;?@[]^_`{|}~\</p></li>
+
+<p>!&#8221;#$%&#38;&#8217;()*+,-.&#47;:;&#60;=&#62;?@[]<sup>_`{|}~\</sup></p></li>
 <li><p>To force a linebreak simple add two spaces to the end of the line:</p>
+
 <p>No linebreak
 here.
 But here is<br/>
 one.</p></li>
 </ul>
+
 <h2 id="embed-html">embed HTML</h2>
+
 <p>You can include arbitrary HTML code in your documents. The HTML will be
 passed through to the resulting document without modification. This is a good
 way to work around features that are missing in smu. If you don&#8217;t want this
 behaviour, use the <code>-n</code> flag when executing smu to stricly escape the HTML
 tags.</p>
+
 <div class="footnotes">
 <hr/>
 <ol>
diff --git a/build/openbsd/index.html b/build/openbsd/index.html
index 999917a..5cb759d 100644
--- a/build/openbsd/index.html
+++ b/build/openbsd/index.html
@@ -16,12 +16,18 @@
 
 <main>
 <h1 id="running-on-openbsd">Running <code>barf</code> on OpenBSD</h1>
+
 <p>2023-08-12</p>
+
 <p>The <code>barf</code> project was built on Linux and was catered towards Linux users. The core of the project will remain focused on Linux&#47;GNU tools, but I also need to support OpenBSD since that is my personal operating system of choice.</p>
+
 <h2 id="download-packages">Download Packages</h2>
+
 <p>Along with your Markdown parser of choice (<code>barf</code> assumes you will be using my version of <a href="https://git.sr.ht/~bt/smu">smu</a>) you will also need to install the required packages on your OpenBSD system:</p>
+
 <pre><code>doas pkg_add rsync coreutils gsed cmake gcc
 </code></pre>
+
 <p>After that, everything should work perfectly fine when building!</p>
 <footer role="contentinfo">
     <hr>
diff --git a/build/qol/index.html b/build/qol/index.html
index bf38b42..d76dc55 100644
--- a/build/qol/index.html
+++ b/build/qol/index.html
@@ -16,26 +16,38 @@
 
 <main>
 <h1 id="quality-of-life-improvements">Quality of Life Improvements</h1>
+
 <p>2024-06-06</p>
+
 <p>I haven&#8217;t circled back to <code>barf</code> in quite a bit of time, so I&#8217;m happy to announce a small update mainly focused on quality of life improvements! I&#8217;ll keep things brief and get right into the core changes:</p>
+
 <p><strong>Automatic detection of your operating system (supports Linux, macOS and OpenBSD currently)</strong></p>
+
 <ul>
 <li><code>barf</code> now checks your current OS and sets aliases accordingly</li>
 <li>this removes the need to hard-set your own aliases or run syslinks</li>
 </ul>
+
 <p><strong>Added a semantically valid RSS feed</strong></p>
+
 <ul>
 <li><code>barf</code> initially launched with Atom support only, now a separate RSS feed is generated at build time</li>
 </ul>
+
 <p><strong>Removed hardcoded feed links from <code>header.html</code></strong></p>
+
 <ul>
 <li>You now only need to set your main domain at the top of the core <code>barf</code> file.</li>
 </ul>
+
 <p><strong>Swapped out <code>smu</code> for <code>lowdown</code></strong></p>
+
 <ul>
 <li>The default Markdown parser is now set to <code>lowdown</code>. The original parser (<code>smu</code>) is great, but I wanted to make the project simpler by avoiding users to clone and build a separate package.</li>
 </ul>
+
 <p>That&#8217;s it really! I&#8217;ve also updated the original blog posts about setting up <code>barf</code> on macOS and OpenBSD to reflect these changes.</p>
+
 <p>Cheers!</p>
 <footer role="contentinfo">
     <hr>
diff --git a/build/rss.xml b/build/rss.xml
index ed78ca1..b583e2d 100644
--- a/build/rss.xml
+++ b/build/rss.xml
@@ -4,33 +4,45 @@
 		<title>barf</title>
 		<link>https://barf.btxx.org/rss.xml</link>
 		<description>Feed description here</description>
-		<lastBuildDate>Fri, 07 Jun 2024 14:26:51 +0000</lastBuildDate>
-		<pubDate>Fri, 07 Jun 2024 14:26:51 +0000</pubDate>
+		<lastBuildDate>Sat, 08 Jun 2024 15:53:53 +0000</lastBuildDate>
+		<pubDate>Sat, 08 Jun 2024 15:53:53 +0000</pubDate>
 		<generator>Custom RSS Generator</generator>
 		<ttl>1800</ttl>
 		<item>
 			<title>Quality of Life Improvements</title>
 			<description>&lt;h1 id=&quot;quality-of-life-improvements&quot;&gt;Quality of Life Improvements&lt;/h1&gt;
+
 &lt;p&gt;2024-06-06&lt;/p&gt;
+
 &lt;p&gt;I haven&amp;#8217;t circled back to &lt;code&gt;barf&lt;/code&gt; in quite a bit of time, so I&amp;#8217;m happy to announce a small update mainly focused on quality of life improvements! I&amp;#8217;ll keep things brief and get right into the core changes:&lt;/p&gt;
+
 &lt;p&gt;&lt;strong&gt;Automatic detection of your operating system (supports Linux, macOS and OpenBSD currently)&lt;/strong&gt;&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;&lt;code&gt;barf&lt;/code&gt; now checks your current OS and sets aliases accordingly&lt;/li&gt;
 &lt;li&gt;this removes the need to hard-set your own aliases or run syslinks&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;&lt;strong&gt;Added a semantically valid RSS feed&lt;/strong&gt;&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;&lt;code&gt;barf&lt;/code&gt; initially launched with Atom support only, now a separate RSS feed is generated at build time&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;&lt;strong&gt;Removed hardcoded feed links from &lt;code&gt;header.html&lt;/code&gt;&lt;/strong&gt;&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;You now only need to set your main domain at the top of the core &lt;code&gt;barf&lt;/code&gt; file.&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;&lt;strong&gt;Swapped out &lt;code&gt;smu&lt;/code&gt; for &lt;code&gt;lowdown&lt;/code&gt;&lt;/strong&gt;&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;The default Markdown parser is now set to &lt;code&gt;lowdown&lt;/code&gt;. The original parser (&lt;code&gt;smu&lt;/code&gt;) is great, but I wanted to make the project simpler by avoiding users to clone and build a separate package.&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;That&amp;#8217;s it really! I&amp;#8217;ve also updated the original blog posts about setting up &lt;code&gt;barf&lt;/code&gt; on macOS and OpenBSD to reflect these changes.&lt;/p&gt;
+
 &lt;p&gt;Cheers!&lt;/p&gt;</description>
 			<link>https://barf.btxx.org/qol</link>
 			<guid isPermaLink="false">https://barf.btxx.org/qol</guid>
@@ -39,12 +51,18 @@
 		<item>
 			<title>Running `barf` on OpenBSD</title>
 			<description>&lt;h1 id=&quot;running-on-openbsd&quot;&gt;Running &lt;code&gt;barf&lt;/code&gt; on OpenBSD&lt;/h1&gt;
+
 &lt;p&gt;2023-08-12&lt;/p&gt;
+
 &lt;p&gt;The &lt;code&gt;barf&lt;/code&gt; project was built on Linux and was catered towards Linux users. The core of the project will remain focused on Linux&amp;#47;GNU tools, but I also need to support OpenBSD since that is my personal operating system of choice.&lt;/p&gt;
+
 &lt;h2 id=&quot;download-packages&quot;&gt;Download Packages&lt;/h2&gt;
+
 &lt;p&gt;Along with your Markdown parser of choice (&lt;code&gt;barf&lt;/code&gt; assumes you will be using my version of &lt;a href=&quot;https://git.sr.ht/~bt/smu&quot;&gt;smu&lt;/a&gt;) you will also need to install the required packages on your OpenBSD system:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;doas pkg_add rsync coreutils gsed cmake gcc
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;After that, everything should work perfectly fine when building!&lt;/p&gt;</description>
 			<link>https://barf.btxx.org/openbsd</link>
 			<guid isPermaLink="false">https://barf.btxx.org/openbsd</guid>
@@ -53,12 +71,17 @@
 		<item>
 			<title>Markdown Examples in barf</title>
 			<description>&lt;h1 id=&quot;markdown-examples-in-barf&quot;&gt;Markdown Examples in barf&lt;/h1&gt;
+
 &lt;p&gt;2023-01-05&lt;/p&gt;
+
 &lt;p&gt;This following was lifted from &lt;a href=&quot;https://github.com/karlb/smu&quot;&gt;https:&amp;#47;&amp;#47;github.com&amp;#47;karlb&amp;#47;smu&lt;/a&gt;&lt;/p&gt;
+
 &lt;h1 id=&quot;syntax&quot;&gt;&lt;code&gt;smu&lt;/code&gt; Syntax&lt;/h1&gt;
+
 &lt;p&gt;smu was started as a rewrite of
 &lt;a href=&quot;http://daringfireball.net/projects/markdown/&quot;&gt;markdown&lt;/a&gt; but became something
 more lightweight and consistent. It differs from &lt;a href=&quot;https://commonmark.org/&quot;&gt;CommonMark&lt;/a&gt; in the following ways:&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;No support for &lt;em&gt;reference style links&lt;/em&gt;&lt;/li&gt;
 &lt;li&gt;Stricter indentation rules for lists&lt;/li&gt;
@@ -66,13 +89,17 @@ more lightweight and consistent. It differs from &lt;a href=&quot;https://common
 &lt;li&gt;Horizontal rules (&lt;code&gt;&amp;#60;hr&amp;#62;&lt;/code&gt;) must use &lt;code&gt;- - -&lt;/code&gt; as syntax&lt;/li&gt;
 &lt;li&gt;Code fences have stricter syntax&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;Patches that increase the CommonMark compatibility are welcome as long as they don&amp;#8217;t increase the code complexity significantly.&lt;/p&gt;
+
 &lt;p&gt;This project is a fork of the &lt;a href=&quot;https://github.com/gottox/smu&quot;&gt;original smu&lt;/a&gt; by
 &lt;a href=&quot;https://eboland.de&quot;&gt;Enno Boland (gottox)&lt;/a&gt;. The main differences to the
 original smu are:&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;Support for code fences&lt;/li&gt;
 &lt;li&gt;Improved &lt;a href=&quot;https://commonmark.org/&quot;&gt;CommonMark&lt;/a&gt; compatibility. E.g.
+
 &lt;ul&gt;
 &lt;li&gt;Code blocks need four spaces indentation instead of three&lt;/li&gt;
 &lt;li&gt;Skip empty lines at end of code blocks&lt;/li&gt;
@@ -86,10 +113,14 @@ original smu are:&lt;/p&gt;
 &lt;/ul&gt;&lt;/li&gt;
 &lt;li&gt;Added a simple test suite to check for compliance and avoid regressions&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;h2 id=&quot;inline-patterns&quot;&gt;Inline patterns&lt;/h2&gt;
+
 &lt;p&gt;There are several patterns you can use to highlight your text:&lt;/p&gt;
+
 &lt;ul&gt;
-&lt;li&gt;&lt;p&gt;Emphasis
+&lt;li&gt;&lt;p&gt;Emphasis&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;Surround your text with &lt;code&gt;*&lt;/code&gt; or &lt;code&gt;_&lt;/code&gt; to get &lt;em&gt;emphasised&lt;/em&gt; text:
 This &lt;em&gt;is&lt;/em&gt; cool.
@@ -105,29 +136,39 @@ This &lt;strong&gt;&lt;em&gt;is&lt;/em&gt;&lt;/strong&gt; cool, too.&lt;/li&gt;
 This is a wontfix bug because it would make the source too complex.
 Use this instead:
 &lt;strong&gt;&lt;em&gt;Hello&lt;/em&gt;&lt;/strong&gt; &lt;em&gt;you&lt;/em&gt;&lt;/li&gt;
-&lt;/ul&gt;&lt;/p&gt;&lt;/li&gt;
+&lt;/ul&gt;&lt;/li&gt;
 &lt;li&gt;&lt;p&gt;inline Code&lt;/p&gt;
+
 &lt;p&gt;You can produce inline code by surrounding it with backticks.&lt;/p&gt;
+
 &lt;p&gt;Use &lt;code&gt;rm -rf &amp;#47;&lt;/code&gt; if you&amp;#8217;re a N00b.
 Use &lt;code&gt;rm -rf &amp;#47;&lt;/code&gt; if you&amp;#8217;re a N00b.
 Use &lt;code&gt;rm -rf &amp;#47;&lt;/code&gt; if you&amp;#8217;re a N00b.&lt;/p&gt;
+
 &lt;p&gt;Double and triple backticks can be used if the code itself contains backticks.&lt;/p&gt;&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;h2 id=&quot;titles&quot;&gt;Titles&lt;/h2&gt;
+
 &lt;p&gt;Creating titles in smu is very easy. There are two different syntax styles. The
 first is underlining with at least three characters:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;Heading
 =======
 
 Topic
 -----
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;This is very intuitive and self explaining. The resulting sourcecode looks like
 this:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;h1&amp;#62;Heading&amp;#60;&amp;#47;h1&amp;#62;
 &amp;#60;h2&amp;#62;Topic&amp;#60;&amp;#47;h2&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Use the following prefixes if you don&amp;#8217;t like underlining:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;# h1
 ## h2
 ### h3
@@ -135,127 +176,179 @@ this:&lt;/p&gt;
 ##### h5
 ###### h6
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;h2 id=&quot;links&quot;&gt;Links&lt;/h2&gt;
+
 &lt;p&gt;The simplest way to define a link is with simple &lt;code&gt;&amp;#60;&amp;#62;&lt;/code&gt;.&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;http:&amp;#47;&amp;#47;s01.de&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;You can do the same for E-Mail addresses:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;yourname@s01.de&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;If you want to define a label for the url, you have to use a different syntax&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;[smu - simple mark up](http:&amp;#47;&amp;#47;s01.de&amp;#47;~gottox&amp;#47;index.cgi&amp;#47;proj_smu)
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;The resulting HTML-Code&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;a href=&quot;http:&amp;#47;&amp;#47;s01.de&amp;#47;~gottox&amp;#47;index.cgi&amp;#47;proj_smu&quot;&amp;#62;smu - simple mark up&amp;#60;&amp;#47;a&amp;#62;&amp;#60;&amp;#47;p&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;h2 id=&quot;lists&quot;&gt;Lists&lt;/h2&gt;
+
 &lt;p&gt;Defining lists is very straightforward:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;* Item 1
 * Item 2
 * Item 3
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Result:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;ul&amp;#62;
 &amp;#60;li&amp;#62;Item 1&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;li&amp;#62;Item 2&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;li&amp;#62;Item 3&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;&amp;#47;ul&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Defining ordered lists is also very easy:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;1. Item 1
 2. Item 2
 3. Item 3
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Only the first number in a list is meaningful. All following list items are
 continously counted. If you want a list starting at 2, you could write:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;2. Item 1
 2. Item 2
 2. Item 3
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;and get the following HTML which will render with the numbers 2, 3, 4:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;ol start=&quot;2&quot;&amp;#62;
 &amp;#60;li&amp;#62;Item 1&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;li&amp;#62;Item 2&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;li&amp;#62;Item 3&amp;#60;&amp;#47;li&amp;#62;
 &amp;#60;&amp;#47;ol&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;h2 id=&quot;code-blockquote&quot;&gt;Code &amp;#38; Blockquote&lt;/h2&gt;
+
 &lt;p&gt;Use the &lt;code&gt;&amp;#62;&lt;/code&gt; as a line prefix for defining blockquotes. Blockquotes are
 interpreted as well. This makes it possible to embed links, headings and even
 other quotes into a quote:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#62; Hello
 &amp;#62; This is a quote with a [link](http:&amp;#47;&amp;#47;s01.de&amp;#47;~gottox)
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Result:
     
     Hello
     This is a quote with a link
     &lt;/p&gt;
+
 &lt;p&gt;You can define a code block with a leading Tab or with &lt;strong&gt;4&lt;/strong&gt; leading spaces&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;    this.is(code)
 
     this.is(code, too)
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Result:
     this.is(code)
     this.is(code, too)
     &lt;/p&gt;
+
 &lt;p&gt;Please note that you can&amp;#8217;t use HTML or smu syntax in a code block.&lt;/p&gt;
+
 &lt;p&gt;Another way to write code blocks is to use code fences:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;```json
 {&quot;some&quot;: &quot;code&quot;}
 ```
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;This has two advantages:
 * The optional language identifier will be turned into a &lt;code&gt;language-&lt;/code&gt; class name
 * You can keep the original indentation which helps when doing copy &amp;#38; paste&lt;/p&gt;
+
 &lt;h2 id=&quot;tables&quot;&gt;Tables&lt;/h2&gt;
+
 &lt;p&gt;Tables can be generated with the following syntax:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;| Heading1 | Heading2 |
 | -------- | -------- |
 | Cell 1   | Cell2    |
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Aligning the columns make the input nicer to read, but is not necessary to get
 correct table output. You could just write&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;| Heading1 | Heading2 |
 | --- | --- |
 | Cell 1 | Cell2 |
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;To align the content of table cells, use &lt;code&gt;|:--|&lt;/code&gt; for left, &lt;code&gt;|--:|&lt;/code&gt; for right
 and &lt;code&gt;|:--:|&lt;/code&gt; for centered alignment in the row which separates the header from
 the table body.&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;| Heading1 | Heading2 | Heading3 |
 | :------- | :------: | -------: |
 | Left     | Center   | Right    |
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;h2 id=&quot;footnotes&quot;&gt;Footnotes&lt;/h2&gt;
+
 &lt;p&gt;Here is an example of using Markdown footnotes&lt;sup id=&quot;fnref1&quot;&gt;&lt;a href=&quot;#fn1&quot; rel=&quot;footnote&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;. And incase you were looking for more examples, here is another one&lt;sup id=&quot;fnref2&quot;&gt;&lt;a href=&quot;#fn2&quot; rel=&quot;footnote&quot;&gt;2&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
+
 &lt;h2 id=&quot;other-interesting-stuff&quot;&gt;Other interesting stuff&lt;/h2&gt;
+
 &lt;ul&gt;
 &lt;li&gt;&lt;p&gt;to insert a horizontal rule simple add &lt;code&gt;- - -&lt;/code&gt; into an empty line:&lt;/p&gt;
+
 &lt;p&gt;Hello&lt;/p&gt;
+
 &lt;hr/&gt;
+
 &lt;p&gt;Hello2&lt;/p&gt;
+
 &lt;p&gt;Result:
 
 Hello
 &lt;/p&gt;
+
 &lt;p&gt;Hello2&lt;/p&gt;&lt;/li&gt;
 &lt;li&gt;&lt;p&gt;Any ASCII punctuation character may escaped by precedeing them with a
 backslash to avoid them being interpreted:&lt;/p&gt;
-&lt;p&gt;!&amp;#8221;#$%&amp;#38;&amp;#8217;()*+,-.&amp;#47;:;&amp;#60;=&amp;#62;?@[]^_`{|}~\&lt;/p&gt;&lt;/li&gt;
+
+&lt;p&gt;!&amp;#8221;#$%&amp;#38;&amp;#8217;()*+,-.&amp;#47;:;&amp;#60;=&amp;#62;?@[]&lt;sup&gt;_`{|}~\&lt;/sup&gt;&lt;/p&gt;&lt;/li&gt;
 &lt;li&gt;&lt;p&gt;To force a linebreak simple add two spaces to the end of the line:&lt;/p&gt;
+
 &lt;p&gt;No linebreak
 here.
 But here is&lt;br/&gt;
 one.&lt;/p&gt;&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;h2 id=&quot;embed-html&quot;&gt;embed HTML&lt;/h2&gt;
+
 &lt;p&gt;You can include arbitrary HTML code in your documents. The HTML will be
 passed through to the resulting document without modification. This is a good
 way to work around features that are missing in smu. If you don&amp;#8217;t want this
 behaviour, use the &lt;code&gt;-n&lt;/code&gt; flag when executing smu to stricly escape the HTML
 tags.&lt;/p&gt;
+
 &lt;div class=&quot;footnotes&quot;&gt;
 &lt;hr/&gt;
 &lt;ol&gt;
@@ -277,14 +370,21 @@ tags.&lt;/p&gt;
 		<item>
 			<title>Running `barf` on MacOS</title>
 			<description>&lt;h1 id=&quot;running-on-macos&quot;&gt;Running &lt;code&gt;barf&lt;/code&gt; on MacOS&lt;/h1&gt;
+
 &lt;p&gt;2023-01-18&lt;/p&gt;
+
 &lt;p&gt;The &lt;code&gt;barf&lt;/code&gt; project was built on Linux and was catered towards Linux users. The core of the project will remain focused on Linux&amp;#47;GNU tools, but that doesn&amp;#8217;t mean MacOS needs to be left out in the cold.&lt;/p&gt;
+
 &lt;h2 id=&quot;download-packages&quot;&gt;Download Packages&lt;/h2&gt;
+
 &lt;p&gt;This walkthrough assumes that you already have &lt;a href=&quot;https://brew.sh/&quot;&gt;homebrew&lt;/a&gt; installed on your machine.&lt;/p&gt;
+
 &lt;p&gt;You will need to install the GNU versions of both &lt;code&gt;date&lt;/code&gt; and &lt;code&gt;sed&lt;/code&gt; in order to avoid breaking things when &lt;code&gt;barf&lt;/code&gt; tries to build.&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;brew install coreutils
 brew install gnu-sed
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Now everything should work as intended!&lt;/p&gt;</description>
 			<link>https://barf.btxx.org/macos</link>
 			<guid isPermaLink="false">https://barf.btxx.org/macos</guid>
@@ -293,16 +393,24 @@ brew install gnu-sed
 		<item>
 			<title>Supporting Basic Dark Mode</title>
 			<description>&lt;h1 id=&quot;supporting-basic-dark-mode&quot;&gt;Supporting Basic Dark Mode&lt;/h1&gt;
+
 &lt;p&gt;2023-03-07&lt;/p&gt;
+
 &lt;p&gt;The default &lt;code&gt;barf&lt;/code&gt; site generator now supports basic dark mode functionality. This has been achieved by including the standard &lt;code&gt;color-scheme&lt;/code&gt; meta tag in the core &lt;code&gt;header.html&lt;/code&gt; file:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;meta name=&quot;color-scheme&quot; content=&quot;dark light&quot;&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;This change also ships with some minor updates to the default &lt;code&gt;blockquote&lt;/code&gt; design. You can see an example below:&lt;/p&gt;
+
 &lt;blockquote&gt;
 &lt;p&gt;This is a really &lt;em&gt;cool&lt;/em&gt; blockquote&lt;/p&gt;
 &lt;/blockquote&gt;
+
 &lt;h2 id=&quot;minor-caveat&quot;&gt;Minor Caveat&lt;/h2&gt;
+
 &lt;p&gt;Unfortunately, Safari still has minor &lt;code&gt;ahref&lt;/code&gt; &amp;#47; link color issue when defaulting to browser dark mode. If this is a problem for your own build of &lt;code&gt;barf&lt;/code&gt;, take a look at a &lt;a href=&quot;https://bt.ht/safari-default-dark-mode/&quot;&gt;solution I wrote about here&lt;/a&gt;.&lt;/p&gt;
+
 &lt;p&gt;Personally, I can&amp;#8217;t be bothered to add that extra code to this project. The Safari team needs to get their shit together and fix such a simple bug. Plus, you shouldn&amp;#8217;t be using Safari anyway - it&amp;#8217;s proprietary garbage.&lt;/p&gt;</description>
 			<link>https://barf.btxx.org/dark-mode</link>
 			<guid isPermaLink="false">https://barf.btxx.org/dark-mode</guid>
@@ -311,22 +419,31 @@ brew install gnu-sed
 		<item>
 			<title>Cleaning Up barf's Structure</title>
 			<description>&lt;h1 id=&quot;cleaning-up-barfs-structure&quot;&gt;Cleaning Up barf&amp;#8217;s Structure&lt;/h1&gt;
+
 &lt;p&gt;2023-10-09&lt;/p&gt;
+
 &lt;p&gt;Things probably look a little different around here. Both in terms of this demo site &lt;em&gt;and&lt;/em&gt; the core &lt;code&gt;barf&lt;/code&gt; files itself.&lt;/p&gt;
+
 &lt;p&gt;This project was always intended to be focused on Linux platforms. So, I&amp;#8217;ve removed the included &lt;code&gt;barf_macos&lt;/code&gt; and &lt;code&gt;barf_openbsd&lt;/code&gt; files to keep the generator more streamlined. But have no fear! Instructions for both Mac and OpenBSD can still be found on the main blog:&lt;/p&gt;
+
 &lt;ul&gt;
 &lt;li&gt;&lt;a href=&quot;/macos&quot;&gt;Running &lt;code&gt;barf&lt;/code&gt; on MacOS&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href=&quot;/openbsd&quot;&gt;Running &lt;code&gt;barf&lt;/code&gt; on OpenBSD&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
+
 &lt;p&gt;As for the &amp;#8220;default&amp;#8221; look of &lt;code&gt;barf&lt;/code&gt;, I&amp;#8217;ve simplified things further. The total CSS styling now consists of only:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;*{box-sizing:border-box;}
 body{font-family:sans-serif;margin:0 auto;max-width:650px;padding:1rem;}
 img{max-width:100%;}
 pre{overflow:auto;}
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Users still have the ability to tweak things as much as they&amp;#8217;d like, but the standard look should be more than enough for anyone just focusing on writing. Dark mode has also been dropped but is easily added by adding the following inside the &lt;code&gt;head&lt;/code&gt; tags:&lt;/p&gt;
+
 &lt;pre&gt;&lt;code&gt;&amp;#60;meta name=&quot;color-scheme&quot; content=&quot;dark light&quot;&amp;#62;
 &lt;/code&gt;&lt;/pre&gt;
+
 &lt;p&gt;Hopefully these changes reduce the overall scope of the project, which was a main point made on the README originally!&lt;/p&gt;</description>
 			<link>https://barf.btxx.org/cleanup</link>
 			<guid isPermaLink="false">https://barf.btxx.org/cleanup</guid>
diff --git a/build/websites/index.html b/build/websites/index.html
index 8a06384..f283b55 100644
--- a/build/websites/index.html
+++ b/build/websites/index.html
@@ -16,7 +16,9 @@
 
 <main>
 <h1 id="websites-built-with-">Websites Built with <code>barf</code></h1>
+
 <p>Send an email to bt [at] btxx [dot] org if you would like me to add your barf-generated website to this list.</p>
+
 <ul>
 <li><a href="https://jsfree.org">jsfree.org</a></li>
 <li><a href="https://barf.btxx.org">barf.btxx.org</a></li>
diff --git a/index.md b/index.md
index ea67516..92e98a2 100644
--- a/index.md
+++ b/index.md
@@ -26,7 +26,7 @@ For macOS:
 
 For OpenBSD:
 
-    doas pkg_add rsync lowdown coreutils gsed cmake gcc
+    doas pkg_add lowdown coreutils gsed cmake gcc
 
 **Clone barf:** 
 
-- 
cgit v1.2.3-54-g00ecf