Upgrade to FontAwesome 6

[samiahmedsiddiqui]

(Edit: @chalin)

• Waiting on Drop FontAwesome static/webfonts file copies, mount package #1164
• Closes Font Awesome static files seem 3 years old? #872

Preview: https://deploy-preview-1102--docsydocs.netlify.app/docs/

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[samiahmedsiddiqui]

@LisaFC @narrenfrei @raum51

[polarweasel]

@LisaFC and @raum51 could you have a look at this one? Fontawesome 6 would be very good to have by default, instead of us having to work around and add it manually. It looks like there's a Docsy release planned for fall, and we'd love to help get this into that.

[LisaFC]

Will take a look - @chalin, can you take a look as well? Agree would be good to have the latest version for the next Docsy release. It doesn't look like it's likely to break anything but do FontAwesome themselves document any breaking changes? Don't want any users to suddenly end up with unexpected icons.

[chalin]

Will take a look as soon as I can.
Please rebase & resolve the conflicts, thanks.

[samiahmedsiddiqui]

@chalin conflicts resolved.

[polarweasel]

Backward compatibility information from the project: https://fontawesome.com/docs/web/setup/upgrade/whats-changed#backward-compatibility

Lots of icons got renamed, but the v5 names will still work. It'd be worth pointing to this table in the release notes, though, to make people aware that they should pick up the new names at some point.

[chalin]

LGTM. Note that I haven't done an exhaustive search to see if any FA class names might have been missed, but what has been updated here works. Thanks!

See inline comment for suggested improvements for this or a followup PR.

[chalin]

Thanks @samiahmedsiddiqui for the PR. Thanks @polarweasel for the link to the backwards compatibility page.

FYI, some prep work which I'd like reviewed and merged before this PR:

• Drop FontAwesome static/webfonts file copies, mount package #1164

Comments are welcome over on that PR.

[chalin]

See inline comment regarding an issue with search placeholder text styling.

[chalin]

Very nice step forward, doing the bulk of the upgrade. Will merge now (as agreed during PSC meeting) and follow up with further changes.

[chalin]

I've collected the followup tasks in:

• FontAwesome 6 upgrade: followup items #1171