Skip to content
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

feat: Support for GDPR compliant google font usage #202

Closed
wants to merge 2 commits into from

Conversation

uroybd
Copy link
Contributor

@uroybd uroybd commented Feb 20, 2023

This PR adds a toggle to choose whether the default google font shipped with the template (namely Roboto) will be served from a locally downloaded version or Google's CDN. This will allow it to be GDPR compliant.

#196

@oleeskild
Copy link
Owner

Nice 🙌

Do you have any good reasons for why this should be a toggle? Wouldn't it be better to just always serve the font "loacally" instead of from a cdn?

@uroybd
Copy link
Contributor Author

uroybd commented Feb 21, 2023

Well... fonts are best served from CDNs. Theoretically, people can also host digital garden in other platforms where they might not have global CDNs. Loading fonts from CDN might be better for them.

@uroybd
Copy link
Contributor Author

uroybd commented Feb 21, 2023

@oleeskild we can do away with google fonts entirely though. Bootstrap's native font stack is pretty solid. We can just use that. For everything else, users can add their fonts.

https://getbootstrap.com/docs/5.3/content/reboot/#native-font-stack

@uroybd
Copy link
Contributor Author

uroybd commented Feb 21, 2023

However, I found that it will be a problem with the extensive styles obsidian itself provides. So GDPR toggle is probably a much better option.

@uroybd uroybd changed the title Support for GDPR compliant google font usage feat: Support for GDPR compliant google font usage Feb 23, 2023
@uroybd uroybd closed this Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants