Ayu
Looks great! Thank you for contributing!
Would #555 be a solution for you? While TTF/OTF files aren't in our NPM packages (due to NPM package size restrictions), we do actually have downloads including TTF/OTF files available...
Perhaps email notifications for updates could be a feature to extend #555 and be more useful to you.
Thanks! This gives me a lot more insight into how I would want to structure #562 to be beneficial to many people. I want to make most of the functionality...
I don't think we need to do anything? To change the ligatures, you can set it with your own [CSS class](https://developer.mozilla.org/en-US/docs/Web/CSS/font-variant-ligatures#examples). It doesn't need any modification to the `@font-face` rules...
I'd be interested in seeing what Google Fonts says on this if you make an issue relating to this topic on their repo. I don't think their API modifies `@font-face`...
I'll close this as I don't see this being implemented unless Google themselves follow through with this. This is out of scope for this project. Thanks for making this issue!
Would #64 fit as a suitable resolution to your problem? While it is easy to make SASS files customisable, I don't know if there are any alternatives that could apply...
I'm not necessarily sure how to go ahead implementing that, but it is a plausible idea. Another alternative to consider could be utilising PostCSS to create a plugin that makes...
I've created #133 for PostCSS specific discussion. This issue can still be used to discuss other viable alternatives.