✅ Deploy Preview for tabi-demo ready!

Name	Link
🔨 Latest commit	3404092
🔍 Latest deploy log	https://app.netlify.com/sites/tabi-demo/deploys/67ed894831d6890008d53aec
😎 Deploy Preview	https://deploy-preview-504--tabi-demo.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Thank you! Appreciate this PR.

A few things:

• are there any disadvantages to enabling cache busting? I can't think of any, so perhaps it should be on by default
• related: perhaps it shouldn't be configurable? Unless we can think of a use-case for disabling it, I'd enable it by default

What are your thoughts?

I was also thinking of creating a theme-wide config option and/or a post-wide config option for this. I can't currently think of any reason to disable it either.

I can't currently think of any reason to disable it either.

Let's go with default = on + no way to disable it, until someone complains :)

Thank you so much!

I just noticed an issue with this. Images which cannot be found by Zola at the time of build don't work: Error: Reason: `get_url`: Could not find or open file netconfig1.svg

Thanks for letting me know. I see this as a feature, no? Or is there a use-case I'm missing?

Thanks for letting me know. I see this as a feature, no? Or is there a use-case I'm missing?

I'm not sure. It was a real error from my side, and dynamic content will use raw_path (if it even uses the image shortcodes).