< [](https://changelog.com/podcast/226) ### The iconic font and CSS framework Font Awesome is a full suite of 675 pictographic icons for easy scalable vector graphics on websites, created and maintained by [Dave Gandy](https://twitter.com/davegandy). Stay up to date with the latest release and announcements on Twitter: [@fontawesome](http://twitter.com/fontawesome). Get started at http://fontawesome.io! ## License - The Font Awesome font is licensed under the SIL OFL 1.1: - http://scripts.sil.org/OFL - Font Awesome CSS, LESS, and Sass files are licensed under the MIT License: - https://opensource.org/licenses/mit-license.html - The Font Awesome documentation is licensed under the CC BY 3.0 License: - http://creativecommons.org/licenses/by/3.0/ - Attribution is no longer required as of Font Awesome 3.0, but much appreciated: - `Font Awesome by Dave Gandy - http://fontawesome.io` - Full details: http://fontawesome.io/license/ ## Changelog - [v4.7.0 GitHub pull request](https://github.com/FortAwesome/Font-Awesome/pull/10012) - [v4.6.3 GitHub pull request](https://github.com/FortAwesome/Font-Awesome/pull/9189) - [v4.6.2 GitHub pull request](https://github.com/FortAwesome/Font-Awesome/pull/9117) - [v4.6.1 GitHub pull request](https://github.com/FortAwesome/Font-Awesome/pull/8962) - [v4.6.0 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?q=milestone%3A4.6.0+is%3Aclosed) - [v4.5.0 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?q=milestone%3A4.5.0+is%3Aclosed) - [v4.4.0 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?q=milestone%3A4.4.0+is%3Aclosed) - [v4.3.0 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?q=milestone%3A4.3.0+is%3Aclosed) - [v4.2.0 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?milestone=12&page=1&state=closed) - [v4.1.0 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?milestone=6&page=1&state=closed) - [v4.0.3 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?milestone=9&page=1&state=closed) - [v4.0.2 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?milestone=8&page=1&state=closed) - [v4.0.1 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?milestone=7&page=1&state=closed) - [v4.0.0 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?milestone=2&page=1&state=closed) - [v3.2.1 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?milestone=5&page=1&state=closed) - [v3.2.0 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?milestone=3&page=1&state=closed) - [v3.1.1 GitHub milestones](https://github.com/FortAwesome/Font-Awesome/issues?milestone=4&page=1&state=closed) - v3.1.0 - Added 54 icons, icon stacking styles, flipping and rotating icons, removed Sass support - v3.0.2 - much improved rendering and alignment in IE7 - v3.0.1 - much improved rendering in webkit, various bug fixes - v3.0.0 - all icons redesigned from scratch, optimized for Bootstrap's 14px default ## Contributing Please read through our [contributing guidelines](https://github.com/FortAwesome/Font-Awesome/blob/master/CONTRIBUTING.md). Included are directions for opening issues, coding standards, and notes on development. ## Versioning Font Awesome will be maintained under the Semantic Versioning guidelines as much as possible. Releases will be numbered with the following format: ` . . ` And constructed with the following guidelines: * Breaking backward compatibility bumps the major (and resets the minor and patch) * New additions, including new icons, without breaking backward compatibility bumps the minor (and resets the patch) * Bug fixes, changes to brand logos, and misc changes bumps the patch For more information on SemVer, please visit http://semver.org. ## Author - Email: dave@fontawesome.io - Twitter: http://twitter.com/davegandy - GitHub: https://github.com/davegandy ## Component To include as a [component](https://github.com/componentjs/component), just run $ component install FortAwesome/Font-Awesome Or add "FortAwesome/Font-Awesome": "*" to the `dependencies` in your `component.json`. ## Hacking on Font Awesome **Before you can build the project**, you must first have the following installed: - [Ruby](https://www.ruby-lang.org/en/) - Ruby Development Headers - **Ubuntu:** `sudo apt-get install ruby-dev` *(Only if you're __NOT__ using `rbenv` or `rvm`)* - **Windows:** [DevKit](http://rubyinstaller.org/) - [Bundler](http://bundler.io/) (Run `gem install bundler` to install). - [Node Package Manager (AKA NPM)](https://docs.npmjs.com/getting-started/installing-node) - [Less](http://lesscss.org/) (Run `npm install -g less` to install). - [Less Plugin: Clean CSS](https://github.com/less/less-plugin-clean-css) (Run `npm install -g less-plugin-clean-css` to install). From the root of the repository, install the tools used to develop. $ bundle install $ npm install Build the project and documentation: $ bundle exec jekyll build Or serve it on a local server on http://localhost:7998/Font-Awesome/: $ bundle exec jekyll -w serve
Catalyst HTML CSS Template Catalyst .01 Welcome Sed tempus, quam vitae lobortis vulputate, sapien nisi ultricies metus, in eleifend ipsum mauris eget magna. Nullam massa nisi, pellentesque eu pretium quis, pulvinar a nulla. Sed tempus finibus lacus, vestibulum condimentum nibh blandit vel. .02 Mauris viverra Morbi vestibulum convallis dui, in tristique neque malesuada eleifend. Sed tempus, quam vitae lobortis vulputate, sapien nisi ultricies metus, in eleifend ipsum mauris eget magna. In dapibus blandit congue. Sed quam nulla, pellentesque eget metus eu, sollicitudin sodales nisl. Integer tempus id lectus quis cursus. Read More .03 Morbi vehicula suscipit Curabitur ornare pulvinar sapien, accumsan malesuada mauris ultricies non. Sed id tempor arcu. Pellentesque tortor sapien, molestie at purus vitae, blandit pretium dolor. Curabitur ornare pulvinar sapien, accumsan malesuada mauris ultricies non. Sed id tempor arcu. Pellentesque tortor sapien, molestie at purus vitae, blandit pretium dolor. Curabitur ornare pulvinar sapien, accumsan malesuada mauris ultricies non. Sed id tempor arcu. Pellentesque tortor sapien, molestie at purus vitae, blandit pretium dolor. .04 Contact Info In dapibus blandit congue. Sed quam nulla, pellentesque eget metus eu, sollicitudin sodales nisl. Integer tempus id lectus quis cursus. Tel: 010-020-0120 Fax: 060-070-0670 Email: info@company.com Submit Message Submitted! Copyright © 2017 Company | Design: templatemo
# Contributing to Font Awesome Looking to contribute something to Font Awesome? **Here's how you can help.** ## Requesting new icons New icons mostly start as requests by the [Font Awesome community on GitHub](../../issues). Want to request a new icon? Here are some things to keep in mind: 1. Please be nice. Font Awesome is a happy place. 2. Please do not request comprehensive sets of icons related to a very specific field. 3. Please [search](../../search?type=Issues) to see if your icon request already exists. If a request is found, please add a 👍 reaction to that one. 4. Please make requests for single icons, unless you are requesting a couple of strictly related icons (e.g., thumbs-up/thumbs-down). 5. Please and thank you if you include the following: - Title your [new issue](../../issues/new?title=Icon%20Request:%20icon-) `Icon request: icon-name` (e.g., `Icon request: icon-car`). - Include a few use cases for your requested icon. How do you plan on using it? - Attach a single color image or two that represent the idea you're going for. - Request concrete objects: it's harder to make an icon to represent happiness, it's easier to make a smiley face. ☺ ## Suggesting icon keyword addition/removal Icon filters are maintained by the [Font Awesome community on GitHub](../../pulls?q=is%3Apr+label%3Adoc). If you feel that an icon * is missing keyword(s) * contains invalid keyword(s) please send a [PR](https://help.github.com/articles/using-pull-requests/) to the `master` branch. ## Reporting issues We only accept issues that are icon requests, bug reports, or feature requests. Bugs must be isolated and reproducible problems that we can fix within the Font Awesome core. Please read the following guidelines to ensure you are the paragon of bug reporting. 1. **Search for existing issues.** We get a lot of duplicate issues, and you'd help us out a lot by first checking if someone else has reported the same issue. Moreover, the issue may have already been resolved with a fix available. 2. **Create an isolated and reproducible test case.** Be sure the problem exists in Font Awesome's code with a [reduced test case](http://css-tricks.com/reduced-test-cases/) that should be included in each bug report. 3. **Include a live example.** Make use of jsFiddle, jsBin, or Codepen to share your isolated test cases. 4. **Share as much information as possible.** Include operating system and version, browser and version, version of Font Awesome, etc. where appropriate. Also include steps to reproduce the bug. ## Key branches - `master` is the latest, deployed version (use for pull request if they only affect the docs) - `gh-pages` is the hosted docs (not to be used for pull requests) - `*-wip` branches are the official work in progress branches for the next releases. All pull requests should be submitted against the appropriate branch ## Notes on the repo As of v3.2.0, Font Awesome's CSS, LESS, SCSS, and documentation are all powered by Jekyll templates and built before each commit and release. - `_config.yml` - much of the site is driven off variables from this file, including Font Awesome and Bootstrap versions - `src/` - All edits to documentation, LESS, SCSS, and CSS should be made to files and templates in this directory - `src/icons.yml` - all LESS, SCSS, and CSS icon definitions are driven off this single file ## Pull requests - At the moment we are not accepting pull requests containing icons - Submit all pull requests against the appropriate `*-wip` branch for easier merging - If your PR only affect the docs, feel free to push against the `master` branch - Any changes to the docs must be made to the Liquid templates in the `src` directory - Any changes to the styles must be made to the .less and .scss files in the `src` directory - If modifying the .less and .scss files, always recompile and commit the compiled files - Try not to pollute your pull request with unintended changes--keep them simple and small - Try to share which browsers your code has been tested in before submitting a pull request ## Coding standards: HTML - Two spaces for indentation, never tabs - Double quotes only, never single quotes - Always use proper indentation - Use tags and elements appropriate for an HTML5 doctype (e.g., self-closing tags) ## Coding standards: CSS - Adhere to the [Recess CSS property order](http://markdotto.com/2011/11/29/css-property-order/) - Multiple-line approach (one property and value per line) - Always a space after a property's colon (.e.g, `display: block;` and not `display:block;`) - End all lines with a semi-colon - For multiple, comma-separated selectors, place each selector on its own line - Attribute selectors, like `input[type="text"]` should always wrap the attribute's value in double quotes, for consistency and safety (see this [blog post on unquoted attribute values](http://mathiasbynens.be/notes/unquoted-attribute-values) that can lead to XSS attacks) ## License By contributing your code, you agree to license your contribution under the terms of the MIT License: - http://opensource.org/licenses/mit-license.html ## Thanks Thanks to Bootstrap for their wonderful CONTRIBUTING.MD doc. It was modified to create this one.
]]>
_1.svg)
_1_(1).svg)
.svg)
_1.svg)
_1_(1).svg)
.svg)
.svg)
.svg)