-
Notifications
You must be signed in to change notification settings - Fork 24
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
Change HPE theme to brand Metric font #2990
Change HPE theme to brand Metric font #2990
Comments
🎉 |
Tracking the work, rationale, and recommendation in this FigJam: https://www.figma.com/file/yEueZRtVp6AuofGfzwb055/MetricHPE-Font?node-id=0%3A1 |
Can you also try with a label that has lowercase descenders, like "jgqyp"? I'm curious to see how those will align. |
I've added that to the label "This label big jump" -- let me know if you have any concerns. |
When I zoom in and use a rule, the Windows with MetricHPE looks a hair too low and the Mac with MetricHPEXS looks a hair too high. All that to say that I don't think MetricHPE is overall worse and would be fine with switching it to it now. I seem to recall Sam Goff suggesting that we could do something in CSS to improve alignment but I cannot remember what it was. |
I would agree re: alignment. Readability is definitely improved with MetricHPE -- so net positive to me.
I have a meeting scheduled on Thursday with Scott, Matt, Chris, Sam and myself to discuss font stuff. I'll bring the topic up to see if Sam has suggestions. |
Update here: Chris is going to reach out to Robert Folk's team to find out who is managing the fonts on the CDN. |
Hey @taysea These fonts are not actually CDN'd. They are being served up over HTTP/1.1 😱 from Also, I have a HPE Fonts app in progress that will add CDN'ing, as well as make standardization & adoption among teams a no-brainer. |
Got it, Chris connected with Bob Folk and he's going to direct towards whichever team is currently managing. Once we have that info, I'll connect with you to see how your work might fold in here. |
What are the specific font weights and variations that we need? |
Hey @ericsoderberghp that's the thing: we should be using lazy-loading such that only fonts that actually get used on a page or in a view get loaded. I see the following getting loaded, en toto:
That may actually expand if we browse other HPE properties, but if we're using lazy-loading, it won't impact performance. |
From a CDN standpoint, I think we will likely want to serve the full spectrum of font weights from thin to black. Specifically:
The type ramp being explored primarily is making use of 300, 400, 500, and 900 weights. However, adding all weights allows for future flexibility and very minimal extra storage cost. I do not see a need for adding italic variants at this time, but again, minimal incremental cost in doing so. |
Hey @halocline I agree: cover the full monty. It's all of 2¢ (if that) to cover all the variants. One clarification: Black is 800, Ultra Black or Extra Black is 900. The Brand Central version includes Black (800), but not Ultra Black (900). It also does not include Ultra Light / Extra Light (200), which is why it's omitted from both of these lists. |
I see. I guess I was thinking we'd follow common mapping conventions (MDN, OpenType). Soft opinion. |
No worries. I got this from MDN, which gets it from OpenType, but they vary slightly on the labels for those last 2. Actually, upon looking at it again, MDN seem to have updated this list to include 950, adding even more to the confusion. I personally prefer MDN's scale for web fonts, but when sourcing & self-hosting custom fonts, I will sometimes make a judgement call about the weight that the foundry calls it versus what it actually IS, and adjust the stylesheet accordingly. |
I feel like I'm taking crazy pills. I could've sworn I JUST looked at the MDN and black was 800. I stand corrected. Sorry, @halocline. This is why I shouldn't be working when I have the flu & a fever 🤪 |
Friday status summary:
|
Friday 1/13/23 update:
|
1/23/22 -- followed up with Artur via email. |
A long time ago ...
In a sprint week far far away ...
We decided to address some issues we were having with the HPE Metric font by making our own font files. This caused some unexpected side effects and we would like to go back to using the original HPE Metric font. But, what about the issues we were having with it you ask? Well, that's what this ticket is about.
The text was updated successfully, but these errors were encountered: