Anyone looking for a Jekyll to 11ty post, this one is a little old, but a good starting point. And another post here too.
I hope they help!
1 Like
so my understanding is that today the asset optimziation settings (we have it turned on but all the checkboxes turned off) is what is giving us the fingerprinted assets (ie, letting the images, etc on our site be cached and only loaded when updated, etc. apologies if i am incorrect)
so when this goes away, we lose that.
we use a static site generator in hugo. we have thousands of images and they are not all “code” images. I don’t see how we can use webpack or whatnot to accomplish this.
so the entire "we handle the caching settings and stuff for you!’ feature of netlify is just…gone?
is there some other netlify way to do this?
Unfortunately, you’re incorrect. The fingerprinted assets have nothing to do with cache handling on Netlify. Give this a read: Better Living Through Caching
yeah, i think that was true several years ago (the fingerprinting affecting deployement to the edge) and likely was fixed a long time ago and my understanding is out of date 
so it would sound like we have no need to fingerprint assets
Did a Support Guide ever get written for this?
To those following this thread, Netlify is working with Cloudinary to offer a solution for sites impacted by the deprecation of post-processing asset optimization. This is in addition to other alternatives.
We’ll be hosting a webinar with Cloudinary on October 5, 2023 to discuss image and video optimization on Netlify with Cloudinary. With the Cloudinary integration enabled for your Netlify site, Cloudinary serves images optimized in the most performant format without any quality loss.
Register here: Cloudinary Asset Optimization For Netlify Customers | Webinar | Cloudinary