Embed Font Awesome locally

[endigo9740]

Link to the Page

No response

Describe the Issue

For GDPR compliance we'll need to remove the remote embed of Font Awesome and instead reference this locally. This will also include performance benefits.

Are you able to create a Pull Request with the fix?

Yes

[Sarenor]

Using web fonts apparently needs npm integration via env variable during the build as demonstrated here:
https://fontawesome.com/docs/web/setup/packages

Might be a problem during local development and definitely needs to be set up during build time, which only people with Vercel access can do.

[endigo9740]

@Sarenor if you were referring to setting up the font awesome token, that's only for pro plans. We stick to free icons, which means we can skip that step!

I'll follow through the rest of the instructions and see if I can get this going now.

edit

I see...

Or if you're using environment variables, you can do this instead:

But again I think we can skip this as it does seem optional. The free set should suffice for us.