-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[$1000] [HOLD for payment 2022-12-15] Update New Dot Fonts #12443
Comments
Hey @shawnborton, I fiddled around in Figma for a while to see if I could get the font files out of it, but alas, I could not. Would you be willing to provide them here? |
Can you let me know the exact font files we're currently using? I think I see that Android and iOS need |
In the meantime, here are the files. You'll have to grab the exact ones you need from these folders, but I think it should be self-explanatory. Expensify Mono: https://www.dropbox.com/sh/yp1s3pdnbwak5mc/AABLu3m4Fw0MZhctS5DS1w01a?dl=0 |
That first PR was to add the fonts as assets. Now I'll begin switching them out. |
I'm realizing that we do indeed need the New Kansas .eot and .woff files. |
Holding. Reason in above comments |
Yup, still waiting to get the final formats for New Kansas once we sign the EULAs and pay final licensing. Will keep you posted! |
If it's a pain, we could always follow up with New Kansas in a different PR? |
@Luke9389 thinking more on this, I think we can probably follow up with a separate PR for New Kansas. This way we can get Expensify Neue out with the color and logo changes at least. Thoughts on that? |
I think that'd be fine! The Help Site should probably hold til all 3 are done since its external. Do you agree? |
I think it would be fine if the help site uses Expensify Neue for headlines for the time being. |
I'm just realizing that I think I'll need |
I think I already added the new help site logo to the Help Site issue. Curious why you need .eot files? It's pretty standard to just use woff files for web/mWeb. |
Oh sick! Sorry bout missing that. I see those now.
Honestly, I don't really know anything about font file types n' stuff. But I do see that we have an .eot reference for every font in the app. Idk, if we need these exactly, but I'm assuming we do bc they're there. I dunno. You know more about this than me so lmk what you think. One thing is that this code isn't just for web and mWeb, it's compiling to iOS and Android. |
I think Android and iOS end up using .otf font files, so we should be good there. Then for web/mWeb, yeah - let's try to only use woff files and see what happens. |
Ok I just did some reading and it looks like I know you're OOO, and we can just add them later. For now I'll continue w the PR. |
Could we please try just implementing the woff files? I think it's pretty standard practice to only use these file types for serving up web/mWeb fonts. |
Still working on this one. |
This one should be getting merged very soon (hopefully today) |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.36-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2022-12-15. 🎊 After the hold period, please check if any of the following need payment for this issue, and if so check them off after paying:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Idk why this one says |
Sorry about that @sobitneupane, I'll get a CM assigned right now. |
Job added to Upwork: https://www.upwork.com/jobs/~01fd6b44212c9f53b2 |
Triggered auto assignment to @jliexpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr ( |
Hey, @jliexpensify, would you be willing to pay @sobitneupane above? Looks like there was never a CM for this one. |
@sobitneupane - invited you. Once you accept, I can get the $1000 payment sorted :) |
@jliexpensify Thanks. Submitted proposal. |
Paid and job closed! |
Thanks @jliexpensify! |
Tracking Issue: #12251
Design Doc Section: https://docs.google.com/document/d/197fXHLlHM_RJA4-3MITwdu0N5e0HX5Q74sA4W80YMD8/edit#bookmark=id.h4aw0750hafm
Update Fonts
Adding fonts to a React Native project requires a few steps for each platform, which are spelled out here.
Body Font
Our new body font will be Expensify Neue. We only need four weights: Regular, Regular Italic, Bold, and Bold Italic
Monospaced Font
Our new monospaced font (used for code blocks and inline code) will be Expensify Mono. We only need two weights: Regular and Bold.
Headline Font
Our new headline font is Expensify New Kansas. We only need two weights: Medium and Medium Italic. We currently do not have a separate headline font in the NewDot repo, so this will be a new addition.
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: