Add clarification that remote fonts are downloaded
📚 Subject area/topic
Fonts
📋 Page(s) affected (or suggested, for new content)
https://docs.astro.build/en/reference/experimental-flags/fonts/
📋 Description of content that is out-of-date or incorrect
Add some clarification about how remote fonts are handled, specifically that they are downloaded to the project
This, in my case, actually caused the "remote" fonts to be more performant than when using the same fonts locally. (I presume this is due to them being downloaded to node_modules somewhere)
Additionally, this will clarify to users concerned about GDPR that the fonts are being downloaded and effectively "self-hosted"
🖥️ Reproduction in StackBlitz (if reporting incorrect content or code samples)
No response
@florian-lefebvre
Yes I think that would be good! I'm not sure where this info should be explained. @sarah11918 do you have ideas?
I would put this as the 3rd paragraph right near the top, if it's a "feature/benefit"! Something after the "Web fonts can affect..." paragraph:
The Fonts API focuses on performance and privacy by downloading and caching fonts so they're served from your site. This avoids calls to / data transfer/requests... (someone had a great explanation of this somewhere, but I can't remember where now)
Like the neutral docs version of Matt's post without words like "broligarch" 😅
Fwiw I'm totally fine with the use of broligarch if it's needed