Our great sponsors
-
-
FiraSourceMono
Discontinued A customized version of Fira Code with some non-default stylistic sets baked-in
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
> Is it what you call "freeze opentype axes based on font-feature-settings" or is it something else?
I was talking in context of variable fonts which come with lots of features mapped to opentype tags and axes. font-feature-settings property selects (or activates) those features. Usually this is done at few CSS selector levels. The variable fonts can be trimmed by freezing those features. I did something like this with Fira Sans a few years ago. [1]
> I would like to do the subset font optimization. I'm just not sure how much of an improvement it's going to be. Have you done it manually before?
It can be quite an improvement for fonts like Inter which ship with massive number of glyphs to support different languages.[2]
[1]: https://github.com/naiyerasif/FiraSourceMono
I'm interested in the notion of identifying "critical" CSS that should be inlined rather than live in its own stylesheet.
I was hoping there was some principled way of identifying critical and non-critical CSS (e.g. user interaction effects like :hover would always be considered non-critical), but it looks like the library it's using just tries to render your page and do a best-effort detection on which rules are considered critical, which is a little unsatisfying: https://github.com/GoogleChromeLabs/critters