This is a collection of my longer form posts / articles. It’s a “blog” in the most traditional sense.
You won’t find things here that are short-form, those will live under /micro when I eventually
get around to building it out 😅
I’ve been sick the past week or so. At first I was really hopeful that it wasn’t Covid. Even though my wife and kids had already tested positive. I really really hoped that now, at the tail end of this thing, I could feel like I had escaped. That I’d made it to the other side unscathed. But that was not meant to be.
I tested positive one week ago today.
The past few days I’ve been working on a proof-of-concept for this blog. It’s part of the roadmap I included in the post about this sites new theme. I already took care of basic styling (and code block styles) by using Simple.css. I also marked up all the posts on this site as an article (h-entry).
That means sending / receiving webmentions and adding micropub support is up next. But in order to do those things I needed to figure out how.
In my last post I mentioned that I wanted to keep this site simple. That I wanted to build on a solid foundation. I didn’t want to muck with that foundation to make my site look “pretty”.
I shared the un-styled version of this site on my socials when @Duffy mentioned Simple.css. I fell in love with the idea of it right away. A classless css framework that applies styling to semantic markup?
Things look a little — ahem — different around here, don’t they? I think if you look carefully you’ll notice a few things have changed 😅
I recently decided that I wanted to change up my personal site and build from a solid foundation. There wasn’t anything wrong with my old theme. Far from it! It worked really well. I just wanted to have something that was purpose built for what I wanted.
I recently found a really cool VSCode extension called FrontMatter. It allows you to manage your static site with a simple, intuitive interface, all within VSCode. This is the first post I’m writing with it.
It sort of feels like a halfway point between managing plain text / markdown files and having a full-blown CMS. For my use, I don’t need something like WordPress… Markdown files and Hugo is plenty. But having a nice interface to see a list of posts, media, etc.
In doing research on themes for this blog, I stumbled across one called Neofeed that had a really interesting Makefile. I was really intrigued by the idea of being able to run a command to start a new post or run the hugo dev server.
However, my needs where a bit different from the author of Neofeed. I modified their Makefile to suit, and I’m excited to write this post about the result!
Once upon a time there was a full-stack software developer who could NOT stop redoing his personal Website. I think this might be the 50th or 60th time I’ve done it in the last 10ish years that I’ve owned this domain. I have used all sorts of content management systems (even wrote a couple of my own) and static site generators. WordPress, OctoberCMS, Pelican, Hugo, etc.
But I keep coming back to Hugo.
Today is Father’s day, a day where we celebrate the dad’s in our lives. Rather than write an appreciation post though, I wanted to write about something that men everywhere can do better. That’s why I decided to write about apologizing. It’s something that few men do, and even fewer do well.
Even worse I’ve seen so many instances lately where men are directly asked to apologize and refuse to.
I have recently started using Qutebrowser (again, lol). I wanted to write / use some simple user scripts to add some functionality, but on OSX I was having some issues with things not being in my PATH. I didn’t realize why / what was happening so I asked in the issues of Qutebrowser on github and quickly got my answer.
It turns out that for GUI apps on OSX they don’t inheirit the path that you set in your shell profile.
I’ve been toying with the idea of setting up Mastodon on my own server for a while now. Today I finally got around to actually doing it (after a failed attempt a couple months ago). I found a guide that I loosely referred to and was immensely helpful at a couple points.
At first I tried running on a super small $5 instance, which seemed fine during setup, but died every few requests when I started using it.