-
Notifications
You must be signed in to change notification settings - Fork 17
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
Alternative for FontAwesome and Google fonts? #313
Comments
(FYI, regarding problematic Google Fonts usage, there is this EU-based drop-in replacement https://fonts.bunny.net/about ) |
I wasn't aware that FA uses Google Fonts. Do we have a good alternative for FA? I'm not sure how I can use Bunny Fonts with FA yet... |
A possible solution is including the static assets in the deployment, instead of loading them from external sources and CDNs to avoid HTTP requests and related cookies to these services . However I'm not sure if that comes with legal implications |
@soxofaan Could you clarify why/how FA is using Google Fonts? I don't see that being in the CSS. The license of FA5 Free seems to be CC/SIL so I think we could just add them to this repo and ship/bundle/host them ourself. We should use the Web Fonts due to the Vue Components, which also use some of the icons if available. PRs are welcome, I have no Web Editor funding right now. |
Not sure. I'm not that familiar with how the app is packaged, but I currently see |
I suspect the Ubuntu font comes from a different dependency, maybe Snotify? |
I noticed this accidentally when web editor seemed stuck/slow on some google fonts request: apparently webeditor depends on FontAwesome and consequently on Google Fonts.
openeo-web-editor/public/index.html
Lines 9 to 10 in 366e9d7
Assuming we're in the free FontAwesome plan: there is apparently a limit to 10.000 page views per month in that plan. We're probably still far below that, but it's not very high threshold either (333 views per day).
Also, as far as I understand, usage of Google Fonts is bit problematic regarding GDPR and tracking, so we might want to avoid that, especially for usage in projects involving ESA/EC.
The text was updated successfully, but these errors were encountered: