-
-
Notifications
You must be signed in to change notification settings - Fork 447
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
Add JuliaMono webfonts to /assets/ ? #1272
Comments
Obviously code on the website should use it! |
So is the benefit here that users don't have to use |
Well I don't know anything about these CDNs - which ones are good, which aren't, whether two are better than one, how much downloads cost, etc - so I can't put any numbers on the benefits of using "julialang.org" or another. Might as well leave everything as it is for now... 😀 |
I thought I'd just chime in from the Documenter perspective: Documenter sites currently use two CDNs: Google Fonts and CDNJS, for fonts and JS deps, respectively. I am quite hesitant to add another CDN to that list (whether that is jsDelivr or julialang.org/Fastly). The reason is that once any CDN fails, the Documenter sites will fail to load. That is because the browsers will block the site load until they are able to fetch the dependencies or they get some sort of an error response. However, if the there is e.g. a true network issue, the CDN will never respond and the browsers will wait at least until the TCP 300s timeout expires (IIRC). We had an incident a few years ago when the various docs across the ecosystem were not loading properly for about 12 or so hours just because of this. So, to switch Documenter over to Julia Mono (which we should totally do), the easiest option from my perspective is to get Julia Mono onto Google Fonts. That said, we could also possibly look into switching everything over the jsDelivr, but that would mean making sure that we can fetch the other deps from there as well. |
Ha, yes, I remember that. I now wonder why the docs didn't all just load with Times and Courier fallback fonts instead... JuliaMono won't be joining Google Fonts any time soon - there's a lot of work involved adapting to their processes, and there's no guarantee of being accepted anyway. Looks like people are happy using |
What about CDNJS though? I discovered we could get Lato from there. It looks like it's a matter of dropping a JSON file into a repo? |
I'll give it a go. |
We could add the JuliaMono webfonts to the julialang.org website. They could live in, say,
www.julialang.org/assets/fonts/JuliaMono/webfonts/
as the files:The total size of this new directory would be about 5MB. People would then be able to use the fonts for package documentation, blog posts, etc.. To do this, they would add something like this to a CSS file:
I've no idea what the bandwidth would be, or whether that would be a cost/pricing issue? At present, the actual OpenType fonts are stored on github, but the webfonts (WOFF) are served from there via the NPM/JavaScript-focussed https://www.jsdelivr.com CDN. It works fine (but I have no more information than that).
There would be no visible changes to this website. (And I'm not saying that people should start using the fonts anywhere, unless they want to. 😄)
I don't know whether you would want a disclaimer in the directory somewhere to the effect that the fonts aren't "official"? Although it does promote Julia, in a way...
The text was updated successfully, but these errors were encountered: