You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Agreed at higher-level design+leadership, EMBL and EMBL-EBI are moving to a new typeface: Plex. I won't get into the background on that here, but it has been discussed at length. (if needed, I'm sure I can find links)
That new font will be the default for VF 2.0, however what we've yet to iron out is:
How can VF 1.x sites can opt-in to the new font? and
If/when VF 1.1/2/3 are "forced" to the new font?
I think No. 2 isn't a near-term thing (and may never happen), so I think we can stick to No. 1.
Currently the "best" approach I have in mind is to create a new optional Sass file + standalone CSS file that can be included in a build process or HTML document.
Included by <link rel="stylesheet" href="https://dev.assets.emblstatic.net/embl-design-system/develop/assets/ebi-vf1-integration/ebi-vf1-integration.css" />
Activated by adding .ebi-vf1-integration to a wrapping element or — ideally — doing body.ebi-vf1-integration
That means this can be scaled to cover an entire page or just specific areas
Agreed at higher-level design+leadership, EMBL and EMBL-EBI are moving to a new typeface: Plex. I won't get into the background on that here, but it has been discussed at length. (if needed, I'm sure I can find links)
That new font will be the default for VF 2.0, however what we've yet to iron out is:
I think No. 2 isn't a near-term thing (and may never happen), so I think we can stick to No. 1.
Currently the "best" approach I have in mind is to create a new optional Sass file + standalone CSS file that can be included in a build process or HTML document.
To illustrate:
some-repo/theme__new-type-for-embl-ebi.css
helvetica -> plex
Final question is where would this new code live?
And then we'd need to go through and update various templates and documentation to reference the new approach.
The text was updated successfully, but these errors were encountered: