The team is now working on the WordPress Interactivity API. This unblocks the same UX Frontity framework enabled but directly in WordPress Core, fully compatible with the new Site Editor.
I do not see inspecting that element any css related with the class .fa above.
Is there something I am missing when importing the css?
Thanks in advance!
mburridge2
Hi @adpabloslopez
Can you provide a link to a repo so that members of the Frontity community can look at your code and clone your project in order to be able to help you. Thanks.
maurice.tadros5
Hello @adpabloslopez ,
I’m not sure if this is best practice but I use react-icons.
npm install react-icons --save
import { FaBeer } from 'react-icons/fa';
<h3> Lets go for a <FaBeer />? </h3>
you could try something like this in your index.js and pass them all into <GlobalStyle> but it’s messy and I’m not sure whether the url format is right
import fontCss from "../css/fonts.css"
import fontAwesomeCss from "../css/font-awesome/css/font-awesome.css"
import fontelloCss from "../css/fontello/css/fontello.css"
import faeot from "../css/font-awesome/fonts/fontawesome-webfont.eot"
import fawoff from "../css/font-awesome/fonts/fontawesome-webfont.woff"
import fattf from "../css/font-awesome/fonts/fontawesome-webfont.ttf"
import fasvg from "../css/font-awesome/fonts/fontawesome-webfont.svg"
const faCss = css`
@font-face {
font-family: 'FontAwesome';
src: url(${faeot}?v=4.0.3);
src: url(${faeot}?#iefix&v=4.0.3) format('embedded-opentype'),
url(${fawoff}?v=4.0.3) format('woff'),
url(${fattf}?v=4.0.3) format('truetype'),
url(${fasvg}?v=4.0.3#fontawesomeregular) format('svg');
font-weight: normal;
}`