Hello, my name is Matt.
There is still a lot of cool Jekyll stuff I’ve yet to write about and I will, but January/February lines up with the end of the Winter semester here at good ol’ Mt. SAC and with my journey in applying for new positions related to my field. The good news is that my job search might be over, as I’m going over some preliminary details with a new employer for a Technical Support position supporting a fairly popular software product that is currently on the market and receiving lucrative investments. It’s a great opportunity that I’m crossing my fingers for, but the Jekyll writing has been on the backburner for now.
In my previous post I wrote about Jekyll and it’s integration with Github Pages, and I mentioned how Github Pages whitelists Jekyll dependencies in your build, essentially building our Jekyll site with the
--safemode flag. As I thought about how we might go around this, switching over to Netlify was a thought that came up that could get comments and syntax highlights going. I also realized I could just build the site locally and push my static pages over to the Github repo for my site, but seemed hacky.
Jekyll feels like a great place to start, again. Ruby and RubyGems is familiar, I’ve gotten the hang of switching between Ruby environments with rbenv, and I like the idea of packaging Jekyll themes in a RubyGem. With Jekyll we can also style with SCSS, write posts in markdown (kramdown), and do kinda-dynamic stuff using HTML with Liquid—sweet.
My experience with web tools fell exponentially after high school, when computer science courses intrigued me with ‘actual’ programming languages like C++ and Java, with a little Python mixed in with discrete math curriculum.
I’ve finally started to get projects up and running thanks to GitHub and frameworks that make deploying a site or web app easy.