Ayu

> Sorry if I've overlooked it, but is there some documentation on what the appropriate steps are for making a PR to add a font? I'd be glad to help...

@teauxfu, I added documentation [here](https://github.com/fontsource/fontsource/tree/main/scripts/generic). Let me know if there are any questions. The fontId's we should go for are: - iosevka-aile - iosevka-etoile - iosevka-curly (it should be fine...

Unfortunately, the process is typically very laborious and tedious for fonts like this. The renamer only does a little to help, but usually I'd then have to use a tool...

I'm surprised we haven't caught this bug before. We just don't have `$type` as an available parameter when passing into `fontFaceVariableCustom`. It can be easily fixed by editing the templates...

I don't have an issue adding this. I just don't have enough time these days and for the rare days where I do have time, I'm addressing the more problematic...

> Are the symbols (or lack thereof) the reason things like `wallet` are not resolving with the current material ui included with Material Icons delivered by Fontsource? What's the easiest...

This also might be better done using Git submodules, and then processing the data directly with scripts and GH actions. However, this data processing and submoduling should be done in...

I don't think we'll ever pursue this and it's a bit unnecessary, so I'll close this.

This one is quite an undertaking and needs a lot of consideration. For example, a lot of the Google Fonts are metafont descendants and I'm not sure how much overlap...

> The defaults could be moved onto the `@mixin` fontFace definition, meaning defaults are scoped and thus won't affect the global scope. The result is you could do something like...