Configure default font settings as Public Sans

[aduth]

Why: To reconcile differences between the brochure site and design system, update design system to reflect current typographic preferences.

Consuming projects can still upgrade and choose to temporarily bypass this change by reconfiguring it to the old setting on a per-project basis.

[zachmargolis]

LGTM, this seems like a big jump (even though it has an escape hook to set the font back via variable)... WDYT of making it default to the current way and then changing the default in a bigger version bump?

Or since we're realistically the only consumers of this repo, it's prob fine

[aduth]

this seems like a big jump (even though it has an escape hook to set the font back via variable)... WDYT of making it default to the current way and then changing the default in a bigger version bump?

Good question. It's something I've contended with in how best to version changes in this project, since technically most any visual change could be counted as backwards-incompatible by some interpretations. To avoid major version bumps for basically any change, my personal view is to consider these sorts of things under the realm of "this is now the new status quo", and as long as it doesn't require any updates to markup / usage on the consuming end, it's a minor version. I feel the same way here, even though in practice we may need to temporarily use the escape hatch for at least the IdP. I generally feel this is a safe change that wouldn't require changes on the consuming end, or at least the changes which come up are likely to be the sort I'd classify as existing bugs (with text reflow in particular) that are only incidentally revealed by a change in font family.

[zachmargolis]

my personal view is to consider these sorts of things under the realm of "this is now the new status quo", and as long as it doesn't require any updates to markup / usage on the consuming end, it's a minor version

that seems like a good enough reason for me! So "you don't need to touch the HTML" = minor/patch and "you definitely need to change the HTML too" = major?

[aduth]

that seems like a good enough reason for me! So "you don't need to touch the HTML" = minor/patch and "you definitely need to change the HTML too" = major?

Yeah, that sounds right to me. Which I think is where this one rides close to the line, since ideally it won't require any changes, but it might in some specific brittle implementations. For the IdP, we're tracking these at LG-4792 and LG-4791.