With FontAwesome 6, CDN URLs are now personalized, which means that in order to support FontAwesome 6, we need users to input a token into BULMA_SETTINGS.
How does FontAwesome 6 work, then?
Well, it lets you create a kit on a page that looks like this:
And whether you are a Pro user or a Free user, the kit URL always looks the same:
<script src="https://kit.fontawesome.com/IDENTIFIER.js" crossorigin="anonymous"></script>
Where IDENTIFIER is some hex value.
Okay, so what do we do?
Here's what I'm thinking:
If the user provides a fontawesome_token, we create a CDN url like the one above.
If no token is provided, we just do what we're doing now - put a CDN to FontAwesome 5. This ensures backwards compatibility, and will work for users who don't need the latest icons and features.
We update the README with a guide for how to set up FontAwesome 6 Free and where to get this token. We also document that this is optional, and what will happen if you don't specify it.
With FontAwesome 6, CDN URLs are now personalized, which means that in order to support FontAwesome 6, we need users to input a token into
BULMA_SETTINGS.How does FontAwesome 6 work, then?
Well, it lets you create a kit on a page that looks like this:
And whether you are a Pro user or a Free user, the kit URL always looks the same:
<script src="https://kit.fontawesome.com/IDENTIFIER.js" crossorigin="anonymous"></script>Where
IDENTIFIERis some hex value.Okay, so what do we do?
Here's what I'm thinking:
fontawesome_token, we create a CDN url like the one above.