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
I'm commissioned with updating Big Shoulders on Google Fonts.
I was wondering whether I shall clean up the repository structure to reflect the fact that the "Text" and "Display" families are no longer needed (for Google Fonts) or leave everything in place because they're still needed elsewhere.
Cheers
The text was updated successfully, but these errors were encountered:
please feel free to clean it up. the city government has no opinion on Text and Display variants existing. they know that the two versions were a stopgap until the dual-axis version was available. I can make that transition work.
the only other major lens into this repo besides Google Fonts is Adobe Fonts, and they, like the city government, can be managed on my end.
On Jan 15, 2025, at 9:37 AM, Yanone ***@***.***> wrote:
Hi,
I'm commissioned with updating Big Shoulders on Google Fonts.
I was wondering whether I shall clean up the repository structure to reflect the fact that the "Text" and "Display" families are no longer needed (for Google Fonts) or leave everything in place because they're still needed elsewhere.
Cheers
—
Reply to this email directly, view it on GitHub <#47>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMRMUXHP7Q43AX6WXBQEJVD2KZ6EXAVCNFSM6AAAAABVHRBEUKVHI2DSMVQWIX3LMV43ASLTON2WKOZSG44TAMJXG4ZTGNA>.
You are receiving this because you are subscribed to this thread.
Hi,
I'm commissioned with updating Big Shoulders on Google Fonts.
I was wondering whether I shall clean up the repository structure to reflect the fact that the "Text" and "Display" families are no longer needed (for Google Fonts) or leave everything in place because they're still needed elsewhere.
Cheers
The text was updated successfully, but these errors were encountered: