FontAwesome V6

[SpeedyD]

While we're on the subject of upgrading- FontAwesome also comes to mind. V6 has been out for quite a while..

But we're still on V5 nonetheless.

I found this document on migrating to v5: (https://docs.fontawesome.com/web/setup/upgrade).

Fortunately, it seems that upgrading THAT is less of a hassle, as they heavily support backwards compatibility.

[liwoyadan]

Hi! So I have a question about this one, since I'm planning to get to it sometime within September while also tackling the Bootstrap v5 update.

I've done this already for a handful of sites and while v6 does offer backward compatibility - so pre-existing icons like fas fa-crown (for the admin panel link) don't need to be changed to the new v6 icon classes - they will specifically show the v6 version of the icon despite using the v5 classes. With that in mind, I recall seeing people mention in the Discord once or twice that they prefer the v5 icon style compared to the v6 icon style - for example: the crown icon in v5 has a base on the bottom and is a little more angular, whereas the crown icon in v6 is lacking the base and is more rounded.

So then my question is: would it be reasonable to add a site setting for this? I'm thinking of allowing the option of staying with v5 icons completely, switching to v6 icons completely, and maybe an option to allow icons with v5 classes (fas fa-crown) to remain with their v5 look while icons with v6 classes (fa-solid fa-crown) will look like the v6 versions. This won't be too difficult - I can easily compile a minimized stylesheet for this with SCSS.

Let me know if that sounds like a good option to have, and I'll go ahead and make a note of it for when I do the update!

[itinerare]

I think that'd be a good option, if you're willing to sort it out! A config setting seems to me to make the most sense, and that's fairly easy to implement anyhow.

[SpeedyD]

Thanks @liwoyadan - I'm leaving this issue open until it auto-closes eventually, but with your last contribution, this issue is officially resolved. :)