From 95532252a85d1ed086b116bb49bc94d1185ac7d8 Mon Sep 17 00:00:00 2001 From: Brandon Silver Date: Wed, 31 Oct 2018 23:57:44 -0500 Subject: [PATCH] Update draft of new post about switching to hugo --- .gitignore | 1 + .../2018-10-29-switching-to-hugo.markdown | 18 -------- ...ng-my-website-from-jekyll-to-hugo.markdown | 43 +++++++++++++++++++ 3 files changed, 44 insertions(+), 18 deletions(-) delete mode 100644 content/post/2018-10-29-switching-to-hugo.markdown create mode 100644 content/post/2018-11-02-switching-my-website-from-jekyll-to-hugo.markdown diff --git a/.gitignore b/.gitignore index 340b6b0..d8a6a80 100644 --- a/.gitignore +++ b/.gitignore @@ -1,2 +1,3 @@ public/** **/.DS_Store +*.bak diff --git a/content/post/2018-10-29-switching-to-hugo.markdown b/content/post/2018-10-29-switching-to-hugo.markdown deleted file mode 100644 index e6dc32b..0000000 --- a/content/post/2018-10-29-switching-to-hugo.markdown +++ /dev/null @@ -1,18 +0,0 @@ ---- -date: "2018-10-31T00:00:00Z" -tags: -- wordpress -- security -- code -- analysis -- encryption -title: Switching to Hugo ---- - -I recently spent some time dusting off my blog and getting it into decent shape. - - - -I've switched from my old (and janky) Jekyll + Polymer setup to Hugo. I've -needed to do this for a very long time but I procrastinated due to a lack of -interest, time, and energy. But no longer! diff --git a/content/post/2018-11-02-switching-my-website-from-jekyll-to-hugo.markdown b/content/post/2018-11-02-switching-my-website-from-jekyll-to-hugo.markdown new file mode 100644 index 0000000..3544976 --- /dev/null +++ b/content/post/2018-11-02-switching-my-website-from-jekyll-to-hugo.markdown @@ -0,0 +1,43 @@ +--- +date: "2018-11-02T00:00:00Z" +tags: +- wordpress +- security +- code +- analysis +- encryption +title: Switching my website from Jekyll to Hugo +--- + +I've switched from my old (and janky) Jekyll + Polymer setup to Hugo, a similar +static content management system written in Go. I've needed to do this for a +very long time but I procrastinated due to a lack of interest, time, and energy. +In this post I'll go over why I've switched, including an overview of how I was +previously generating my website with Jekyll. + + + +## The old setup +I used Jekyll for a very long time. Over the years I went through a few +different template designs, even creating several of my own that I never +ultimately published. I was always trying to find a balance between client-side +functionality and compatibility / simplicity. I wanted a "modern" website with +contemporary creature comforts (like a responsive, mobile-friendly frontend) +that would also work with really basic web browsers. + +Sometime last year I settled on [a really cool combination +of two different templates](https://github.com/brandonsilver/jekyll-polymer/tree/customized): +one using the Polymer front-end library with oodles of Material Design elements, +and another very basic one of my own creation for users with JavaScript +disabled. Building my website entailed running a gulp script, which in turn first built the +Polymer-using version of my website (the default one), and then built the basic version. Sounds +great, right? I finally had the best of both worlds. All of the benefits of modernity with full +backwards compatibility. + +As it turned out, Polymer didn't age well. And the build tooling required to build my Polymer +template didn't age well either. Add to that the complexity of said build tooling and its inability +to fully optimize the final product and you get a mildly frustrated developer looking for +alternatives. + +## The new setup +