HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
FortAwesome
Font-Awesome
JavaScript2012–2026
FortAwesome / Font-Awesome

Font-Awesome

The iconic SVG, font, and CSS toolkit

Web DevelopmentLearning & ReferenceCreative & Media
Explore on GitHubRead Hacker News discussions
38Distinct people
41Mentions
0Explicit recommenders
77KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The iconic SVG, font, and CSS toolkit

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:01:12 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year41 dated mentions

Observed mentions: 2012-03-07 04:16:41 UTC to 2026-04-12 16:41:51 UTC.

02468102012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 8 mentions; 3 submissions, 5 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC303
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC10010
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC826
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC312
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC835
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC211
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC220
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC110
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC110
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Version 7 Font Awesome is the Internet's icon library and toolkit, used by millions of designers, developers, and content creators. Documentation Learn how to get started with Font Awesome and then dive deeper into other and advanced topics: Docs for version 7 Where did Font Awesome 6, 5, 4 (or 3) go? Now that Font Awesome 7 has been released we are marking version 6 as Long Term Support (LTS). Version 6 will get critical bug fixes only. Version 3, 4, and 5 are now end-of-life and we don't plan on releasing any further versions of these. You can see a complete list of versions on our Versions page. Change log The change log for releases is now available directly on our site. Looking for older versions of Font Awesome? Check the releases. Upgrading From time-to-time we'll have special upgrading instructions from one version to the next. Web upgrading guide Desktop upgrading guide Code of conduct We will behave ourselves if you behave yourselves. For more details see our CODE_OF_CONDUCT.md. Contributing Please read through our contributing guidelines. Included are directions for opening issues. Versioning Font Awesome will be maintained under the Semantic Versioning guidelines as much as possible. Releases will be numbered with the following format: <major>.<minor>.<patch> For more information on SemVer, please visit https://semver.org. The major version "7" is part of an umbrella release. It includes many different types of files and technologies. Therefore we deviate from normal SemVer in the following ways: Any release may update the design, look-and-feel, or branding of an existing icon We will never intentionally release a patch version update that breaks backward compatibility A minor release may include backward-incompatible changes but we will write clear upgrading instructions in UPGRADING.md A minor or patch release will never remove icons Bug fixes will be addressed as patch releases unless they include backward incompatibility then they will be minor releases License Font Awesome Free is free, open source, and GPL friendly. You can use it for commercial projects, open source projects, or really almost whatever you want. Icons — CC BY 4.0 License In the Font Awesome Free download, the CC BY 4.0 license applies to all icons packaged as .svg and .js files types. Fonts — SIL OFL 1.1 License In the Font Awesome Free download, the SIL OFL license applies to all icons packaged as web and desktop font files. Code — MIT License In the Font Awesome Free download, the MIT license applies to all non-font and non-icon files. Attribution is required by MIT, SIL OFL, and CC BY licenses. Downloaded Font Awesome Free files already contain embedded comments with sufficient attribution, so you shouldn't need to do anything additional when using these files normally. We've kept attribution comments terse, so we ask that you do not actively work to remove them from files, especially code. They're a great way for folks to learn about Font Awesome. Team https://github.com/orgs/FortAwesome/people
Read the full README on GitHub

What Hacker News says

3 sources
bergie·Mar 27, 2012
Tooltips! Good point! Done: https://github.com/bergie/hallo/commit/259c6172e475188f01fd9... Selecting text in the middle of a paragraph and choosing a header type or pre or blockquote affects the whole paragraph. This isn't immediately intuitive. I don't have a good solution to this, but it's something to consider. Yeah, this is what browsers do by default when issuing commands to the contentEditable. The way to fix this would be to recognize the command before it issued and splitting the text before and after a selection to their own block-level elements. https://github.com/bergie/hallo/issues/54 Once I select text in the middle of a paragraph and mark it as pre there doesn't seem to be a way to back out this change, selecting blockquote just embeds a blockquote in the pre block. Yeah, pre is kind of difficult to handle. I'm thinking abo
Read the rest
ut solutions. Previous Hallo didn't have pre enabled to work around this, but I really would like to be able to add code snippets when I write. The <= and => icons are not intuitive as undo/redo. I'm using FontAwesome, and they will hopefully add a proper undo at some point (https://github.com/FortAwesome/Font-Awesome/issues/16). The actual undo/redo implementation comes from the browser, so it is a bit hard to do much about it. But whenever we get to doing OT with ShareJS there might come a better way to handle editing history.
In Show HN: WYSIWYG-editing Markdown with Hallo Editor

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.