--- layout: base title: Get Started with Font Awesome navbar_active: get-started relative_path: ../ --- {% capture jumbotron_h1 %} Get Started{% endcapture %} {% capture jumbotron_p %}Easy ways to get Font Awesome {{ site.fontawesome.version }} onto your website{% endcapture %} {% include jumbotron.html %} {% include stripe-social.html %}
Setting up Font Awesome can be as simple as adding two lines of code to your website, or you can be a pro and customize the LESS yourself! Font Awesome even plays nicely with Bootstrap 3!
{% endcapture %} {% include stripe-ad.html %}Add Font Awesome into your website with a single line of code. You don't even have to download or install anything!
<head>
section of your site's HTML.
{% highlight html %}
{% endhighlight %}
Use this method to get the default Font Awesome CSS with the default Bootstrap CSS.
font-awesome
directory into your project.<head>
of your html, reference the location to your font-awesome.min.css.
{% highlight html %}
{% endhighlight %}
Use the Official Font Awesome LESS Ruby Gem to easily get Font Awesome LESS into a Rails project. Generously maintained by @supercodepoet.
Use the Official Font Awesome SASS Ruby Gem to easily get Font Awesome SASS into a Rails project. Generously maintained by @supercodepoet.
Use this method to customize Font Awesome {{ site.fontawesome.version }} using LESS or SASS.
font-awesome/
directory into your project.font-awesome/less/variables.less
or font-awesome/scss/_variables.scss
and edit the @fa-font-path
or $fa-font-path
variable to point to your font directory.
{% highlight scss %}
@fa-font-path: "../font";
{% endhighlight %}
The font path is relative from your compiled CSS directory.
If you need IE7 support, you have my condolences. Really. Font Awesome {{ site.fontawesome.version }} doesn't support IE7, but an older version does. You'll need to check out the 3.2.1 instructions for using IE7. Then go complain to whomever decided your project needs IE7 support.
If you're having trouble with Font Awesome, make sure to check out the troubleshooting wiki page. Generously maintained by @gtagliala.