New Year, New Blog


Image by Hannah Markley via Unsplash

It’s that time again: time to continue being indecisive about my website and trying something to see how long it lasts. However I’ve been working on this site for a few weeks now and I’m definitely happy with how it turned out and I think I will be sticking with it for a long time!


This post is about my old blog site. Click here to view my new post about the current design.

After months of not having a website due to some IRL difficulties, I decided it was time to get back into the swing of things. The site is completely static, being generated with Pelican. The theme is a custom one I created that is meant to emulate the traditional blog website design but with a more modern look. The website is currently hosted on I tried Netlify first and, while I had no problems with it,’s restrictions were much more lax.

Because I like to do things my own way (in terms of setting up my website work flow) it took a day or two just to get my static asset build process and deployment set up. As with pretty much all of the websites I make, it uses Gulp + Webpack to process static assets. After the build system was set up and integrated with Pelican, I started adding features to at least bring some sort of dynamicy to an otherwise static website. One such feature is the cache busting you can observe in the HTML source. Unfortunately this feature does not extend to asset URLs inside JS and CSS files without major changes to my build process.

There are more features I have planned for my website such as:

  • Light/dark theme switch
  • Additional dynamic features (such as entry views, upvotes, etc) through a custom API server
  • Adding more general core blog features
    • journal entry “neighbors”
    • random entry
    • author page
    • etc

A challenge with this new site is ensuring it looks good when viewed on a mobile device. A little known fact about me is that I hate developing websites to look good on mobile. At the time of writing this entry, I highly doubt that the site is mobile-friendly. The site may stay like that forever, or I may get around to updating it. In the mean time, dear reader, it is highly recommended to view my site in desktop mode (if you haven’t already…)

Another challenge with this website isn’t related to anything technical, but rather writing the content. I’m not that good of a writer (as you may or may not have noticed). Perhaps finally having a proper platform to write on can help me improve?

2019 ended kind of rough for me, but hopefully 2020 goes far better. Starting out with a brand new website and having a place to just write what’s on my mind seems like it can benefit me in the long run.

Here’s to a new year!

Photo courtesy of Hannah Markley via Unsplash