Blog Initial Tech Stack Thoughts

Published: Sun 04 June 2017
Updated: Sun 04 June 2017

In Blog.

tags: blog tech stack

Ok, let’s start a blog.

First of all, we need a tech stack. My initial thoughts are to use a static site generator. None of the blog code needs to be dynamic, and I can import a javascript comment system (such as discus) later. Probably end up using google analytics as well.

I’ll be using either markdown or restructured text so that I can track the blog configuration using git.

Perfect, so we’ve got a static site generator, markdown/restructured text, third party analytics and commenting… now on to hosting. Since I don’t feel like taking on the hosting thing for now, and the domain name isn’t important, let’s just stick with github pages. I’m pretty sure it’s free.

The only other things that I would like would be some responsive design (I primarily read using my smart phone) and some way to embed a jupyter notebook directly in the page.

I’ll save the responsive design for another day (and a more complicated folder directory as well), but the desire for jupyter notebook means I’ll probably be using some sort of python stack instead of the (likely more popular) Github incarnation of Jekyll.

A quick google search shows that Pelican is likely the largest/most supported python static site generator. Looks like it can work with either markdown or restructured text (I’ll probably stick with restructured text since I’ve written some README’s with it). Perfect. Another quick search shows there’s a plugin that allows for Jupyter-Notebooks to be in embedded. We’re cooking with fire now. So let’s review our tech.

  • Git (version control)
  • Resturctured Text (text markup)
  • Github Pages (website hosting/Domain)
  • Pelican (static site generator)

Tech to be implemented later (third party and potentially hard)

  • Discourse (comments)
  • Google Analytics (analytics)

Awesome, let’s start implementing.

Comments !

Subscribe to the mailing list

* indicates required

links

social