From 9f369b5193851f6f929c8463e5a7b4f9b6801df8 Mon Sep 17 00:00:00 2001 From: Cory Dransfeldt Date: Wed, 1 May 2024 09:51:39 -0700 Subject: [PATCH] fix: image --- ...ling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md b/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md index d457e1e8..ccd49528 100644 --- a/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md +++ b/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md @@ -14,7 +14,7 @@ To simplify file uploads to B2, I mount the bucket for my site using [Mountain D My music charting feature relies on JSON maps of artist and album metadata — if a new artist or album isn't present in either, it assumes that the image it needs is in the format of `artist-name.jpg` or `artist-name-album-name.jpg`. I store the canonical copies of these image files in a separate GitHub repo and have Hazel watch the `artist` and `album` directories contained therein. It renames the files to match the aforementioned format, strips characters that typically break URLs and copies them to my mounted B2 Bucket. -{% image 'https://coryd.dev/.netlify/images/?url=/media/blog/albums-hazel-rule-example.png&w=1000', 'An example of my album art Hazel workflow', 'image-banner' %} +{% image 'https://coryd.dev/media/blog/albums-hazel-rule-example.png', 'An example of my album art Hazel workflow', 'image-banner' %} ---