From 16d28628aca9b2d356de31c319f5e7bc0f5b2b02 Mon Sep 17 00:00:00 2001
From: Bradley Taunt <bt@btxx.org>
Date: Sat, 8 Jun 2024 13:43:37 -0400
Subject: Remove incorrectly generated files, fix up markdown articles

---
 build/hello-jekyll/index.html | 18 ++----------------
 1 file changed, 2 insertions(+), 16 deletions(-)

(limited to 'build/hello-jekyll')
diff --git a/build/hello-jekyll/index.html b/build/hello-jekyll/index.html
index 93c5035..15ecda0 100644
--- a/build/hello-jekyll/index.html
+++ b/build/hello-jekyll/index.html
@@ -3,11 +3,12 @@
 <head>
 	<meta charset="utf-8">
 	<meta name="viewport" content="width=device-width, initial-scale=1">
+	<meta name="color-scheme" content="dark light">
 	<link rel="icon" href="data:,">
 	<title>Goodbye WordPress, Hello Jekyll (Again)</title>
 	<link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" />
 	<link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" />
-<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
+<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
 </head>
 
 <nav>
@@ -16,55 +17,40 @@
 
 <main>
 <h1 id="goodbye-wordpress-hello-jekyll-again">Goodbye WordPress, Hello Jekyll (Again)</h1>
-
 <p>2020-08-13</p>
-
 <p>For the past four months this blog has been running on WordPress - but that ended today. I&#8217;ve officially switched back over to Jekyll. I&#8217;m not going to spend too much time delving into <em>why</em> I made the transition back, but I&#8217;ll leave some cliff-notes for any interested parties.</p>
-
 <h2 id="the-big-issues-with-my-wordpress-setup">The big issues with <em>my</em> WordPress setup</h2>
-
 <p>I have to state that these problems existed based on <em>my own</em> setup &#47; hosting choices with WordPress - this is not a direct reflection of WP itself.</p>
-
 <ol>
 <li><strong>No theme editor access</strong>
-
 <ul>
 <li>I was using EasyWP (Namecheap etc.) for my web hosting. It only cost me $3.88&#47;month, which was very cheap for the quality of service provided. Unfortunately, this low price came with some setbacks. EasyWP doesn&#8217;t allow users to edit <code>header.php</code> or <code>functions.php</code> files directly in the theme editor. Having to resort to FTP for simple one-line change was annoying.</li>
 </ul></li>
 <li><strong>Super cache</strong>
-
 <ul>
 <li>Caching web pages is wonderful for users on subsequent visits, but EasyWP took this to the extreme. Making minor styling updates sometimes required code changes in the <code>header.php</code> file directly in order to persist (see problem with editing these files in point #1).</li>
 </ul></li>
 <li><strong>Monthly cost</strong>
-
 <ul>
 <li>As I stated above, spending $3.88 on a monthly basis was peanuts in the grand scheme of things. Still, an extra monthly subscription for a side hobby seemed overkill for my use case.</li>
 </ul></li>
 <li><strong>Future proofing</strong>
-
 <ul>
 <li>In the end, having the core website generate itself into static files means it will stand the test of time on the interwebs. HTML &#38; CSS FTW.</li>
 </ul></li>
 </ol>
-
 <h2 id="what-i-lost-in-the-switch">What I lost in the switch</h2>
-
 <ol>
 <li><strong>Comments</strong>
-
 <ul>
 <li>I loved the concept of owing &#47; hosting comments directly on each post but this seemed like a fair trade-off when compared to the positives listed above. I might circle back around and use something like <a href="https://commento.io/">Commento</a> or <a href="https://github.com/imsun/gitment">Gitment</a></li>
 </ul></li>
 <li><strong>Blog anywhere</strong>
-
 <ul>
 <li>Having the ability to hop on any machine, log in to my site and blog was awesome. Over time though, I found myself not doing this very often. Most times when composing an article I found I would write it out, edit and publish all in one sitting. Cool concept - just not as useful.</li>
 </ul></li>
 </ol>
-
 <h2 id="moving-forward">Moving forward</h2>
-
 <p>I&#8217;ve learned to stick with what keeps me productive (and in this case, keeps me writing consistently). I still love WordPress and won&#8217;t hesitate to reach for it when the need arrives. Unfortunately, it seems my personal website isn&#8217;t one of those instances.</p>
 <footer role="contentinfo">
     <h2>Menu Navigation</h2>
-- 
cgit v1.2.3-54-g00ecf

