-
-
Notifications
You must be signed in to change notification settings - Fork 387
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
NEW DESIGN: Host Google font for Material icons locally #7474
Comments
Current fonts we use: https://fonts.googleapis.com/css2?family=Public+Sans&family=Material+Icons on Chrome, this returns:
With wget:
|
We can host fonts, but then we lose all the "smart" things Google Font does by returning fonts specific to what the user can use (e.g. woff2 instead of ttf, and variable fonts instead of fixed fonts). We could also try to replicate that, by specifying both woff2 and ttf fonts in the CSS. We lose also the automated updates. On the up side, we are less dependent on an external server and we don't send data to it. |
I'm more in favor of hosting fonts locally as google fonts is known to be a tracker on users. https://github.com/neverpanic/google-font-download can help ? It seems capable of generating the CSS supporting different browser. |
Also https://google-webfonts-helper.herokuapp.com is really easy to use. |
Thanks for the links. The first one is very outdated and does not support the newest changes: neverpanic/google-font-download#27 But I think I can copy the format generated by the second one (it has Public Sans but not Material Icons for some reason). I'll give it a try. |
As I wrote on slack, we could use another CDN service that is more privacy-friendly than Google, for example https://bunny.net/fonts/. It's hosted in EU so it has to comply with GDPR. |
@VaiTon Bunny fonts seems really interesting and provides "a Google Fonts drop-in compatible API". They provide the "Public Sans" we use, but unfortunately I can't find Material Icons. |
What
Part of
The text was updated successfully, but these errors were encountered: