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
We switched from CDNs to serving typefaces as static assets. When a new version of the font is released, this requires the manual step of pulling fonts builds from their upstream websites, clean up unrelated variants, remove them from their entrypoint CSS (e.g. inter.css) and commit the changed files.
This could be automated and made reproducible by switching to a package manager (e.g. npm) to pull the typefaces at build time.
I'd prefer if this was not done unconditionally at build time, and instead there was a script to update the font file which is otherwise cached in the source.
This cuts back on the number of deps strictly required to run the site, as well as build times, at the cost of a comparatively modest amount of storage.
We switched from CDNs to serving typefaces as static assets. When a new version of the font is released, this requires the manual step of pulling fonts builds from their upstream websites, clean up unrelated variants, remove them from their entrypoint CSS (e.g. inter.css) and commit the changed files.
This could be automated and made reproducible by switching to a package manager (e.g. npm) to pull the typefaces at build time.
E.g. inter on npm: https://www.npmjs.com/package/inter-ui
The text was updated successfully, but these errors were encountered: