Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Please update the Font Awesome library, I now have to look for the 4.7 reference, while Font Awesome 5 is out already. I first wondered why for example this wouldn't work in my navbar:
- text: 'Manual'
The reason appeared to be that fa-book-open is not available in older Font Awesome libraries.
Please update it, and replace the fa class with fas in your CSS classes as described here: https://fontawesome.com/how-to-use/on-the-web/referencing-icons/basic-use.
The text was updated successfully, but these errors were encountered:
For those who cannot wait: you can add the reference to the updated library yourself by updating the <head> on all your pages as follows:
$('head').append('<!-- Updated Font Awesome library --><link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.6.3/css/all.css" integrity="sha384-UHRtZLI+pbxtHCWp1t77Bi1L4ZtiqrqD80Kn4Z8NTSRyMA2Fd33n5dQ8lWUE00s/" crossorigin="anonymous">');
(got text from https://fontawesome.com/start)
Now you can you use Font Aweome 5.6.3! Everything on https://fontawesome.com/icons is now available for you website 😉
Icons for brands (like fa-github for the GitHub icon) are now in a different font file than the other icons. To also support icons for brands:
/* Support icons for brands using Font Awesome by forcing the right font family */
font-family: "Font Awesome 5 Brands" !important;
- text: 'Home'
- text: 'Source Code'
icon: 'fab fa-gitlab'
So Home does not need the fab, since fa-home is not a brand icon, but fa-gitlab is.
Sorry, something went wrong.
fontawesome is not on cdnjs yet; we will migrate once it's available there.
Update fontawesome to 5.7.1
fontawesome deprecated the fa prefix in version 5. now using the fas and fab (for brands) prefixes.
Update fontawesome to 5.7.1 (#979)
Successfully merging a pull request may close this issue.