-
Notifications
You must be signed in to change notification settings - Fork 22
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
Cache busting (Was: Some questions/remarks after viewing the source code) #382
Comments
Hey Bernard, not taking it as criticism (of the bad kind), we just want a good end product! If you see anything funny that you know how to fix, your help is very welcome!
|
@bnijenhuis Can you check this for me? :) #383 |
If you want the font to preload, they cannot go. |
@SleeplessByte The -tags for the fonts should handle the preload, right? Not an inline style with the font declarations? Correct me if I'm wrong. The cache busting thing is (as I understand) a temporary JS "hack", and is going to be replaced or removed. |
@bnijenhuis do you mean the |
Not sure where to put this, so I figured this was the best place (because 'Discussions' isn't used). I was just looking at the source code of the homepage, and I have some questions:
<link rel="alternate" hreflang="en-US" href="/">
;head
? They are in the CSS as well;To be clear, this is not meant as criticism, although it could come over as such. I haven't been involved in implementing everything, so it's not my place to criticize, but I was just wondering what the reasoning is behind some choices. Or maybe it was just overlooked.
The text was updated successfully, but these errors were encountered: