-
Notifications
You must be signed in to change notification settings - Fork 61
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
Onboarding Geist to Google Fonts #99
Comments
Hi @yanone! I’m helping the designers team to solve some issues and improve the tech quality of the font. After #25 we have been discusing internally about onboarding to GF and I mentioned the required breaking changes. It‘s very likely that those changes will be done to avoid having different versions of Geist but it will happen in the next month or so. I will keep you posted. |
Excellent, thank you. |
We also need to resolve the rfn which can be done by someone from vercel emailing [email protected] with an rfn permission, there's an example email in the gf guide :) https://googlefonts.github.io/gf-guide/license-file.html |
This would be very helpful, thank you! |
@guidoferreyra What's the status here? |
any news? |
Thank you for the update. I'll be out for July and August, so not much time left. If the fonts are ready during that time, better connect with Dave about handing the work to another onboarder. But summers are generally slow as other people also take time off. |
Re-assigning from Yanone to @vv-monsalve. Let's see if we can land this in Fonts in Q3 |
Hello.
I've been commissioned to onboard Geist to Google Fonts.
Here are a few things I found that we would require to change:
gftools builder
Normally, I would make those changes and send you a PR back. But at least one of them (UltraLight instance name) may break existing text, so I wanted to communicate about that first. I mean, fonts hosted on GoogleFonts are in a separate environment to existing Geist fonts, but it may be inconvenient to keep two versions of sources around. I may also be able to come up with a build script that can rename the instance and not change the source.
Looking forward to your reply.
The text was updated successfully, but these errors were encountered: