Initial Content

So, I'm slowly building things out. I'm at the early stages of building out this idea, but I like so far where I'm going.

The idea is to build off something I started not too long after college. I had this idea to take a notebook and to copy things I really wanted to know and have handy. This was pre-smartphone, so in some cases, having a portable reference was really useful.

Flash forward to today. I was looking through the immense digital clutter I have at my fingertips - the trove of links I hope to read or maybe have read and forgotten that could have been useful, but now may not even exist.

I decided it was time to purge it down to the things I really thought was important. But instead of keeping them in my bookmarks, I figured it made more sense to put them in a website, where I can create context.

I guess this blog will be me writing notes about my journey. The first entries I've made are for Jekyll itself and markdown. On the Jekyll front, the goal is to write enough so you can skip ahead of what I had to go through. Honestly, if you are planning to run the site through GitHub and just write basic content, there's no real reason you need to install Ruby and go through that, you really just need a basic folder structure and dump it in GitHub and let the magic happen.

Sure, it's kinda nice to be able to run it locally, but given that I will probably be writing from all manner of machines along the way, it's a luxury that isn't necessary. I mean, the ability to deploy it in this manner is the principle reason I picked Jekyll in the first place. Sure, Gatsby and Hugo and Jupyter Book and a miriad of other solutions are neat, but if I want to sit down and type away at a Chromebook or my Windows machine, I don't want step 1 to always be setup a development environment. In this case, the least friction possible is the goal.