diff options
Diffstat (limited to 'build/hello-jekyll/index.html')
| -rw-r--r-- | build/hello-jekyll/index.html | 78 |
1 files changed, 47 insertions, 31 deletions
diff --git a/build/hello-jekyll/index.html b/build/hello-jekyll/index.html index c15154a..93c5035 100644 --- a/build/hello-jekyll/index.html +++ b/build/hello-jekyll/index.html @@ -1,55 +1,71 @@ <!doctype html> -<html lang="en" id="top"> +<html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <link rel="icon" href="data:,"> <title>Goodbye WordPress, Hello Jekyll (Again)</title> - <link href="https://bt.ht/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" /> - <style>*{box-sizing:border-box;}body{font-family:sans-serif;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{overflow:auto;}table{text-align:left;width:100%;}</style> + <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> </head> <nav> - <a href="#menu">Menu ↓</a> + <a href="#menu">Menu ↓</a> </nav> <main> -<h1>Goodbye WordPress, Hello Jekyll (Again)</h1> +<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've officially switched back over to Jekyll. I'm not going to spend too much time delving into <em>why</em> I made the transition back, but I'll leave some cliff-notes for any interested parties.</p> -<h2>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 / hosting choices with WordPress - this is not a direct reflection of WP itself.</p> + +<p>For the past four months this blog has been running on WordPress - but that ended today. I’ve officially switched back over to Jekyll. I’m not going to spend too much time delving into <em>why</em> I made the transition back, but I’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 / hosting choices with WordPress - this is not a direct reflection of WP itself.</p> + <ol> -<li><strong>No theme editor access</strong></li> -</ol> -<p> - I was using EasyWP (Namecheap etc.) for my web hosting. It only cost me $3.88/month, which was very cheap for the quality of service provided. Unfortunately, this low price came with some setbacks. EasyWP doesn'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.</p> +<li><strong>No theme editor access</strong> -<ol start="2"> -<li><strong>Super cache</strong></li> -</ol> -<p> - 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).</p> +<ul> +<li>I was using EasyWP (Namecheap etc.) for my web hosting. It only cost me $3.88/month, which was very cheap for the quality of service provided. Unfortunately, this low price came with some setbacks. EasyWP doesn’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> -<ol start="3"> -<li><strong>Monthly cost</strong></li> -</ol> -<p> - 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.</p> +<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> -<ol start="4"> -<li><strong>Future proofing</strong></li> +<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 & CSS FTW.</li> +</ul></li> </ol> -<p> - In the end, having the core website generate itself into static files means it will stand the test of time on the interwebs. HTML & CSS FTW.</p> -<h2>What I lost in the switch</h2> + +<h2 id="what-i-lost-in-the-switch">What I lost in the switch</h2> + <ol> -<li><strong>Comments</strong></li> -</ol> -<p> - I loved the concept of owing / 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></p> +<li><strong>Comments</strong> -<ol start="2"> -<li><strong>Blog anywhere</strong></li> +<ul> +<li>I loved the concept of owing / 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> -<p> - 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.</p> -<h2>Moving forward</h2> -<p>I've learned to stick with what keeps me productive (and in this case, keeps me writing consistently). I still love WordPress and won't hesitate to reach for it when the need arrives. Unfortunately, it seems my personal website isn't one of those instances.</p> + +<h2 id="moving-forward">Moving forward</h2> + +<p>I’ve learned to stick with what keeps me productive (and in this case, keeps me writing consistently). I still love WordPress and won’t hesitate to reach for it when the need arrives. Unfortunately, it seems my personal website isn’t one of those instances.</p> <footer role="contentinfo"> <h2>Menu Navigation</h2> <ul id="menu"> |