-
Notifications
You must be signed in to change notification settings - Fork 153
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
Self-Host Fonts #12351
Self-Host Fonts #12351
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! Thanks @robdivincenzo ! I didn't realize this many files would be affected until I saw your PR 😅
As a follow-up discussion, I wonder if we want to move fonts related bits out of the SCSS/SASS ecosystem to improve our build time. It's very unlikely that we wanna modify those font files (we probably shouldn't anyway). If we can convert the font .scss
files into .css
and just include them as is, it will shorten the watch/build cycle during development. SCSS does take very looooong to compile and that is that one thing I dislike about SCSS. I will file a new ticket to discuss about this.
@robdivincenzo Awesome. Thank you! |
➤ Simon Acosta Torres commented: PR has already been merged. |
Description
This PR will introduce self-hosted fonts rather than relying on google's font delivery service.
Link to sample test page: https://foundation-s-tp1-671-12-isi5mm.herokuapp.com
Related PRs/issues: TP1-671 #12348
To Test
Nunito Sans
andZilla Slab
should load from static files without regression.Caveat
font should also load from static files without regression (see names of on the love letters)Changa
should also load from static files without regression (see headline for example)┆Issue is synchronized with this Jira Story