I haven't used them for a long time, and I suspect they are part of what's causing >2000ms load times on the website.

More immediately recognizable

Better match the banner branding I'm using across social media.

I'm emphasizing other aspects of my personality beyond tech. That will help me share more of those other interests while staying "on brand". I also hope that people will be intruiged by the combination -- moreso than the prior one at least.

`html-proofer` was flagging catb.org for not being linked via HTTPS. That site does not have a valid cert right now and doesn't really pose a security risk for readers, so there's no reason to fail the build for that reason.

I got tired of typing the bundle command. `make dev` is much easier to remember

While I currently use LinkedIn as my main place to build a following, I want the flexibility to easily change it later if I so desire.

Effectively creates short, dynamic URLs for badges. Once I point badges here, I can update them in one place and have them automatically reflected everywhere I used them.

A "Low Quality Image Placeholder" can improve Largest Contentful Paint (LCP) times, provided the placeholder visually and dimensionally the full-size image which gets loaded later.

Most importantly, the LQIP loads eagerly, so it appears almost immediately, instead of after the rest of page.

Google's PageSpeed insights flagged this image as the primary contributor to the key "Largest Contentful Paint" metric.

So, even though it was already only 48KB, I added a few more size optimizations to drop the size further to 25KB.

Both Cloudflare and Google have been reporting that my site takes 6-10 seconds to load, dramatically longer than I had expected.

A detailed report via Google's PageSpeed Insights pointed out this image's 4MB as a major contributor to the slowdown/bandwidth. The

The new image is down to ~74KB (a 55x reduction) making it now one of the smallest images on the site.

The choir's website didn't exist when I wrote this article. Now that it does, I want to pass along any positive SEO metrics my site gains onto the choir.

Part of my efforts to clarify more prominently that I have a Master's Degree in Software Engineering.

The new CI scripts from Chirpy are excellent!

We want to use a custom script instead of the default GitHub Pages build.

Allow the website to appear under my apex domain instead of
GitHub's subdomain.

Making sure old links will still work after the migration to Chirpy.

Chirpy has lots of fancy tools for beautifying technical writing.

This commit updates each of my posts to take advantage of those features.