Explore Public Sans typeface

[francisrupert]

The good folks of 18F designed an Open Source typeface, Public Sans (GH), and is the default typeface for US Web Design System.

It's a core part of their v2 Design System, and while we've already determined updating to [email protected] is out of scope anytime soon - per #286 (comment) - it would be prudent to explore Public Sans and understand impacts, pros/cons, etc; and if it would be good (and usable) fit for the Design System.

One thing that's significantly inhibited us from true Typography exploration has been ability (or relative inability) to freely install or budget for font installation - let alone manage installation among many staff machines. The fact that Public Sans is Open Source and created by a peer agency can make that path smoother. Additionally, there appears to be a strong likelihood it will wind up in Google Fonts (tracking uswds/public-sans#29). If nothing else, that'll make Figma use and adoption smoother as well.

Design Principles

• Be available as a free, open source webfont on any platform.
• Use metrics similar to common system fonts for smoother progressive enhancement.
• Have a broad range of weights and a good italic.
• Perform well in headlines, text, and UI.
• Be straightforward: have as few quirks as possible.
• Have good multilingual support.
• Allow for good data design with tabular figures.
• Be strong and neutral.
• Encourage continuous improvement — strive to be better, not necessarily perfect.

-via https://github.com/uswds/public-sans

[francisrupert]

Since Milestone 2.5.2 is relatively ahead of schedule, going to see if this is worthwhile for 2.5.2 as well -- and more directly, how much of an impact (good or bad) would it have to legacy products implemented with Source Sans?

If so, it might warrant a release of 2.6.0 instead.

[francisrupert]

Currrent Status:

Findings

• Pleasing rendering. Far more readable and easier on eyes than Source Sans on tested screens and devices.
• Significant improvement in rendering data tables, particularly numbers.
• Not too burdensome to update across the board. Anticipate little-to-no impacts for apps that update.
• Potential discrepancy between public-facing USDA or FPAC properties. Could likely make both Public Sans and Source Sans typefaces available for Product Teams to decide.

Outcome

• Not a feature update that can be snuck into a patch release (e.g. 2.5.2).
• Requires care and attention to detail in selectively tuning across the board. That is, it's not merely a swap of font-family, but potentially select adjustments of font-weight and font-size. (e.g. <hN> refactor #431)
• Consider moving to next Feature release (e.g. 2.6.0), pairing with next significant set of features to launch.
• Requires more stress-testing across legacy products to understand implications and validate presumptions of little-to-no impact when updating.

Screenshot

Animated toggling between Public Sans and Source Sans (current typeface).