Use Bunny Fonts instead of Google Fonts #5475
Replies: 1 comment 4 replies
|
Thanks for suggesting. This is a pretty fundamental change, as we would be switching to an entirely different CDN. Checking their font explorer, Bunny Fonts does not seem to be a full replacement, as Google Fonts has 1,508 and Bunny Fonts has 1,492 fonts. I'm not sure how they sync fonts and functionality, but it doesn't seem to be a transparent proxy. IMHO, swapping out Google Fonts for another solution is only solving part of the problem. The canonical way to achieve full GDPR compliance is to use the built-in privacy plugin, which will automatically download and inline all external assets. However, since you would only need to replace an URL, you could also just use a hook and replace the URL, and be done: def on_post_page(output, page, config):
return output.replace(
"https://fonts.googleapis.com/css",
"https://fonts.bunny.net/css"
)Then save that to hooks:
- hooks/fonts.pyFour lines of code, so it's ridiculously simple. |
Uh oh!
There was an error while loading. Please reload this page.
Google Fonts is not GDPR compliant. Bunny Fonts is a GDPR compliant drop-in replacement for Google Fonts. Bunny Fonts is fully compatible with the Google Fonts CSS v1 API, meaning the only change required would be swapping
https://fonts.googleapis.com/cssforhttps://fonts.bunny.net/css.I would like to see this change, because it would give website operators the option to use a globally available font provider without having to subject their users to Google's tracking, which is in line with the "fast and lightweight" project philosophy.
All reactions