You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: