-
Notifications
You must be signed in to change notification settings - Fork 471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serve Source Sans locally - avoid law suits #2077
Comments
Hi @koppor, Thanks for your report. I acknowledge the issue of Google Fonts and GDPR and I can confirm Storefront is loading Source Sans directly from Google Fonts as you described.
Thanks for your suggestion. Our team will need to discuss this before taking any action. Because Storefront is now in maintenance mode, the process can take a while. In the meantime, you can use a plugin to make your site GDPR-compliant: https://wordpress.org/plugins/local-google-fonts/. Can you please test that plugin to see if it solves your issue? |
Thank you for the quick response. The plugin works great, thank you for the hint! |
Heads-up that in #845 (comment) there is a suggested snippet that might also work. There is also this filter that might be useful. |
Is your feature request related to a problem? Please describe.
In Germany, it is forbidden to fetch Fonts from Google. If one doesn't follow this rule, one has to play (at least) 300€ per case. See https://ll-ip.com/aktuelles/raag-kanzlei-dikigoros-nikolaos-kairis/ for details.
Describe the solution you'd like
Storefront should ship the font in its distribution.
Describe alternatives you've considered
There is a hint at https://wordpress.org/support/topic/css-font-display-how-to-add/ to create a child theme. It seems, however that 300+ lines of code need to be copied - only for replacing one font.
The text was updated successfully, but these errors were encountered: