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

Cleanup the fonts files #71

Open
dkozel opened this issue Nov 20, 2022 · 1 comment
Open

Cleanup the fonts files #71

dkozel opened this issue Nov 20, 2022 · 1 comment

Comments

@dkozel
Copy link
Contributor

dkozel commented Nov 20, 2022

In adding the Mastodon link in the footer I had to update the Font Awesome CSS and font files. I didn't notice that the old css had been edited to allow Hugo to automatically publish only the actually used files. I worked around the smarts by just putting the Font Awesome webfont files into a new static folder, but there are some unused extras that should be removed.

The Font Awesome CSS file could be edited to restore the file linking and smart exporting, but I'm a bit of two minds as it is nice to leave the CSS unaltered so future updates can be copied directly in.

For reference, here's the css edits from the old file.
d4a7a1b

@noc0lour
Copy link
Member

If I'm not mistaken fonts are also part of the minify & timestamp pipeline. So whenever we update the files they would circumvent the browser caching and with certainty load the new files since there is some content hash included in the filename.

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

No branches or pull requests

2 participants