I really like this photo of a street crossing in Omotesandō, but I didn’t mean to take it. I had no idea it even existed until my most recent Lightroom photo dump.
Accidental captures are always nice for two reasons.
During my migration from Netlify to Cloudflare Workers Sites, one of the things I had to figure out was how to deal with redirects. Over the years, I’ve accumulated nearly 900 redirects from URL slug and permalink syntax changes. On Netlify, creating redirects was really simple – all that was required was a _redirects file containing all the redirects. Cloudflare Workers Sites doesn’t have support for redirects built in, so I had to create my own redirect handling.
In this article, I’ll show you how I’m redirecting URLs with Cloudflare Workers and Workers KV on a Hugo-generated static site.
We stayed at Hoshinoya Fuji for a few days last month. Even though it was mostly cloudy during our stay, it was still a relaxing experience. I have many thoughts on the “glamping” concept, but I don’t really have the time to write about it right now. For now, here’s a photo I took from inside our cabin at Hoshinoya Fuji.
Update: Check out my full review of Hoshinoya Fuji here.
Since publishing my original post about migrating from Netlify to Cloudflare Workers Sites, I’ve made a few tweaks to my deployment process. Instead of building this Hugo site on a free Google Compute Engine VM, I’ve moved the build process to a serverless GitHub Actions workflow. Serverless building was always the goal from the start, but I was too busy to figure out how to set up GitHub Actions during the initial migration from Netlify to Cloudflare.
A few weeks ago, I finally had time to set everything up on GitHub Actions. In this article, I’ll share how I deploy my Hugo-generated static site to Cloudflare Workers Sites with a GitHub Actions workflow.
In the context of music production, quantization is the process of snapping sounds to a musical grid. In most cases, quantization is used to line up transients with the beat. When used correctly, and with taste, quantization can help boost the production quality of your projects. In this article, you’ll learn how to quantize both audio and MIDI in Logic Pro X.
Yesterday, I received an email with the subject “Your Ledger Assets Might Be Vulnerable”. Since I do use a Ledger Nano to protect a small portion of my crypto portfolio (I still prefer paper wallets for cold storage), I decided to look into this email more. My first instinct was that this was a phishing email, and I’m glad that I was correct. With that in mind, I wanted to write this blog post in case anyone else may be wondering whether this email is legit or not.
Cloudflare Automatic Platform Optimization (APO) for WordPress is a brand new optimization service that intelligently distributes your WordPress site’s HTML and third-party fonts across Cloudflare’s globally-replicating Workers KV database and edge network in 200 cities worldwide. Since the release of Cloudflare APO, I’ve noticed a number of misconceptions about the new service. In this post, I’ll highlight four misconceptions about Cloudflare APO to help you get a better understanding of how the WordPress performance optimization service works.
In Part 1 of this series titled “WordPress vs. Jamstack in 2020”, we discussed an articled penned by Richard MacManus of The New Stack. In this post, which was an interview of sorts with Automattic CEO Matt Mullenweg, MacManus highlighted Mullenweg’s criticisms against Jamstack. Tribalism is rampant in technology. Whether it’s iPhone vs. Android, HEY vs. Gmail, or Notion vs. Trello, calling out the opposition will typically result in backlash. In this case, Mullenweg’s criticisms against Jamstack spawned various rebuttals, one of which came from Matt Biilman, the CEO of Netlify. In this post, we’ll take an in-depth look at Biilman’s response from a blog post titled “On Mullenweg and the Jamstack – Regression or Future?” – Don’t you just love Big Tech drama?
Let’s get started.
I’ve been catching up on WordPress podcasts recently, and I came across an episode of The Matt Report (one of my favorite WordPress podcasts) that discussed an ongoing feud between Matt Mullenweg (CEO of Automattic) and Matt Biilmann (CEO of Netlify). The topic of this podcast really caught my attention because I’m a huge supporter of both WordPress and the Jamstack, and I actually use both of these web technologies on a daily basis. In this post, we’ll take a look at the arguments from both sides, and I’ll share my thoughts on why I think this debate is a silly one to be having in the first place.
Last week, Cloudflare released “Automatic Platform Optimization” (APO), a new performance optimization service for WordPress sites. At first glance, APO may seem like yet another WordPress optimization service, but it’s actually the most important development in the world of WordPress performance since people figured out how to do page caching a long time ago. If you use WordPress to power your site, you need to do yourself a favor and check out Cloudflare APO!
Let me tell you why.