Skip to content

FontAwesome integration #119

New issue

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? Sign in to your account

Closed
did opened this issue Mar 14, 2025 · 2 comments · Fixed by #144
Closed

FontAwesome integration #119

did opened this issue Mar 14, 2025 · 2 comments · Fixed by #144
Labels
documentation Improvements or additions to documentation

Comments

@did
Copy link
Contributor

did commented Mar 14, 2025

<link href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/css/all.min.css" rel="stylesheet">
<script type="text/javascript">window.FontAwesomeConfig = { autoReplaceSvg: false }</script>
<script src="https://kit.fontawesome.com/d7c95a53d0.js" crossorigin="anonymous"></script>
@did did added the documentation Improvements or additions to documentation label Mar 14, 2025
@mabras
Copy link
Contributor

mabras commented Apr 25, 2025

Following the docs:
https://docs.maglev.dev/guides/use-an-icon-library#fontawesome

I am having difficulty including Font Awesome icons because of schema name of the icons.

Not all icons have the same name schema:

<i class="fa-brands fa-accusoft"></i>
<i class="fa-solid fa-align-justify"></i>

It is not just fa fa-<name of the icon>
This will load some icons but not all of them:

Image

@did did linked a pull request May 10, 2025 that will close this issue
2 tasks
@did did closed this as completed in #144 May 11, 2025
@did
Copy link
Contributor Author

did commented May 11, 2025

Documentation updated (https://docs.maglev.dev/guides/use-an-icon-library). But it requires to release the new version of Maglev (1.9).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants