Closed
Bug 1351143
Opened 7 years ago
Closed 7 years ago
Typography - switch from Fira to Open Sans
Categories
(www.mozilla.org :: Pages & Content, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: erenaud, Assigned: craigcook)
References
Details
Attachments
(1 file)
User Story - https://tree.taiga.io/project/malexis-mozillaorg-durable-team/us/1123 Tasks - - Build list of pages w. Fira - Code conversions to Open Sans
Reporter | ||
Updated•7 years ago
|
Assignee: nobody → craigcook.bugz
Assignee | ||
Comment 1•7 years ago
|
||
The only pages using Fira Sans are those using the Pebbles framework, and there aren't many: 1. home 2. /technology 3. /internet-health 4. /internet-health/privacy-security 5. /internet-health/digital-inclusion 6. /internet-health/open-innovation 7. /about/leadership 8. /newsletter/firefox 9. /newsletter/mozilla 10. /newsletter/developer 11. /moss 12. /firefox/new/?xv=breakfree 13. /firefox/new/?xv=wayofthefox
Assignee | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Commits pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/c78175672e7635f6e1657028629debd60eb4c3e3 [fix bug 1351143] Switch Pebbles to Open Sans https://github.com/mozilla/bedrock/commit/d0ca20820bc541efeef581a2da5a29a158ebcaec Merge pull request #4739 from craigcook/bug-1351143-pebbles-open-sans [fix bug 1351143] Switch Pebbles to Open Sans
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Comment 4•7 years ago
|
||
A step backwards — switching to an overused (diluting your brand as a consequence), passé font with less readability features. I thought the plan was to use the new, bespoke font since 2014 (!), according to bug 1047087?
Comment 5•7 years ago
|
||
It goes without saying that Fira has more glyph coverage than Open, as well, so pages in other languages (such as Kabyle, which uses ɣ) look ugly and patchy. And I don’t see Google’s Open Sans mentioned anywhere in https://mozilla.ninja/typography. This is all wrong.
You need to log in
before you can comment on or make changes to this bug.
Description
•