Verified Commit 942e7822 authored by Roberto Bochet's avatar Roberto Bochet
Browse files

Remove Fork Awesome

parent e46aaca0
Pipeline #531 passed with stage
in 1 minute and 28 seconds
This diff is collapsed.
name: Icon request
about: Suggest an icon for this project
<!-- Please review open and closed issues that the icon hasn't been requested before. -->
## Icon
Please add an image for this icon
As a general rule, images with simple shapes and only one color are the best.
If this icon is a "brand" icon, let us know why this brand is important and what they do.
## Name Suggestion
<!-- What name should be used for this icon? -->
## Use Case
<!-- Describe how a user of fork-awesome would use that icon in their project. -->
# don't need these in the npm package.
- ruby
- node_js
- bundle install
- npm install
- npm run build
- provider: pages
skip-cleanup: true
github-token: $GITHUB_TOKEN
keep-history: true
local-dir: _site
branch: master
tags: true
- provider: npm
email: $NPM_EMAIL
api_key: $NPM_TOKEN
branch: master
tags: true
# blocklist
- gh-pages
# Changelog
## Changelog of Fork awesome
- v1.1.6
- Added icons: file-epub, python, archlinux, pleroma, unsplash, hackster, spell-check, moon, sun, f-droid, and biometric
- Some documentation correction and augmentation, mostly in the README
- Gave access to the @all-contributors [bot] to the repo for easier contributor list management
- Added a plugin to automatically update the Contributors badge when building the documentation
- Added an official domain name for the project:
- v1.1.5
- Just bumped the version number to trigger an automated deploy
- v1.1.4
- Added icons: Gitea, AT&T, Digitalocean, C (language), Wikidata, Emby, Jirafeau, Hashnode, DevTo, Pixelfed, Matrix, Inkscape, Syncthing.
- v1.1.3
- Added icons: Syncthing and Inkscape
- Fixed sizing with PHP icon
- Added the `sync` alias to the refresh icon
- v1.1.2
- Adds a `v5-compat.css` file in order to ease transition from Font Awesome v5 to Frok Awesome [#112](
- Adds full MIT license in the CSS, LESS and SCSS headers [#113](
- Ignoring some unnecessary files that were distributed with the CDN
- v1.1.1
- Adding a CI pipeline with Travis.
- Fixes bell and bell-o icons who were switched up [#88](
- Add a mention in the documentation that the SIL-OFL also applies to SVG glyphs [#62](
- v1.1.0
- Upgrade of build tools to latest versions ( Jekyll & svgo mainly)
- Change of Globe icon to be more world friendly
- Adds more icons: more globes (east & west views), zotero, nodejs, nextcloud, hackaday, laravel, signal, gnupg, php, ffmpeg amd joplin.
- v1.0.11
- Adds icons: Dogmazic, React, Tipeee, Mastodon Square.
- Fix variable names for generated SCSS variables.
- Fix old reference to Font Awesome in SCSS variables.
- v1.0.10
- Adding a few icons: Debian, Messenger, Freedombox
- v1.0.9
- Adding icons for & Xmpp
- Improving icons for QRcode & Barcode
- v1.0.8
- Bumping just for jsDelivr because it won't accept an array as default files.
- v1.0.7
- Prepares for jsDelivr CDN distribution
- Adds sourcemap for min version of CSS (jsDelivr requirement)
- Updates Medium icon to latest branding + adds Medium square icon.
- v1.0.6
- Removes Twitter js tracker in the doc and add Disapora* and Mastodon share button (Distributopia)
- Adding a few more icons: Shaarli, Key (modern)
- v1.0.5
- Solves a bug where CSS, LESS & SCSS folder were not updated
- v1.0.4
- Some build process changes
- Adds a SVG template file in src/icons for better icon placement and sizing comparison
- Adds Discord, Patreon, Snowdrift, Ethereum, ActivityPub and Keybase icons
- v1.0.3
- Adding Artstation icon [#19](
- Adding an SVG Inkscape template for icon sizing and positioning
- v1.0.2
- Solves a Makefile bug that packaged files that were not updated.
- Correction of typos in the documentation.
- v1.0.1
− Mainly solving a packaging bug.
- v1.0.0
- Forked from Font Awesome 4.7.0. Rename of the project to Fork Awesome.
- Cleaned up the doc and removed 3rd party trackers and advertisement from documentation.
- Extracted all the icons from the SVG webfont into individual SVG files.
- Added 12 new icons.
- Removed 3 imaginary brand icons.
- Added FontCustom as a build tool to create the webfonts.
## Changelog of Font Awesome
- [v4.7.0 GitHub pull request](
- [v4.6.3 GitHub pull request](
- [v4.6.2 GitHub pull request](
- [v4.6.1 GitHub pull request](
- [v4.6.0 GitHub milestones](
- [v4.5.0 GitHub milestones](
- [v4.4.0 GitHub milestones](
- [v4.3.0 GitHub milestones](
- [v4.2.0 GitHub milestones](
- [v4.1.0 GitHub milestones](
- [v4.0.3 GitHub milestones](
- [v4.0.2 GitHub milestones](
- [v4.0.1 GitHub milestones](
- [v4.0.0 GitHub milestones](
- [v3.2.1 GitHub milestones](
- [v3.2.0 GitHub milestones](
- [v3.1.1 GitHub milestones](
- 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 to Fork Awesome
Looking to contribute something to Fork Awesome? **Here's how you can help.**
## Requesting new icons
New icons mostly start as requests by the [Fork Awesome community on GitHub](../../issues). Want to request a new icon? Here are some things to keep in mind:
1. Please be nice. Fork Awesome is a happy place.
2. 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 or link to 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. ☺
## Adding a new icon
Adding a new icon is a couple steps process that will require your attention and eyes for details. It might be a bit intimidating at the beginning, but should be easy to repeat once you've gone through it once or twice.
0. Follow the []( to install the necessary tools.
1. All icons are originally designed in SVG and fit in a grid (see `src/icons/icon-template-inkscape.svg` for a template for Inkscape).
2. Most icons should fit a square that is centered vertically and aligned left in that template. (Try importing existing icons in that template to understand how they fit.)
3. Design your icon in black only. No transparency. No gradient. Use simple shapes and forms. Note that it will be automatically transformed into a glyph. So if the design is complex, it might not show in the font as expected. Change a few things and try again if that happens.
4. From the `src/icons` folder, use the `make` command to build the icon font. It will also generate a file called `src/icons/forkawesome/forkawesome-preview.html`. Open it with a browser and search your icon on the test page. This preview file will show you how your design behaves after conversion. It will also automatically associate a unicode code point for it. Be sure remember it.
5. Once you are satisfied with your design and the preview of it. Add the icon name, unicode point and icon information at the bottom of the `src/icons/icons.yml` file. Look at other entries to see how it's done and to give it a proper classification.
6. Once all this is done, commit your changes and make a pull request.
## Suggesting icon keyword addition/removal
Icon filters are maintained by the [Fork 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]( 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 Fork 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 Fork Awesome's code with a [reduced test case]( 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 Fork Awesome, etc. where appropriate. Also include steps to reproduce the bug.
## Key branches
- `master` is the latest, deployed version
- `gh-pages` is the hosted docs (not to be used for pull requests)
## Notes on the repo
Fork 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/doc/` - All edits to documentation, LESS, SCSS, and CSS should be made to files and templates in this directory
- `src/icons/icons.yml` - all LESS, SCSS, and CSS icon definitions are driven off this single file
## Pull requests
- Any changes to the docs must be made to the Liquid templates in the `src/doc` directory
- Any changes to the styles must be made to the .less and .scss files in the `src/doc` directory
- If modifying the .less and .scss files, always recompile and commit the compiled files
- 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](
- 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]( that can lead to XSS attacks)
## License
By contributing your code, you agree to license your contribution under the terms of the MIT License:
## Thanks
Thanks to Bootstrap for their wonderful CONTRIBUTING.MD doc. It was modified to create this one.
This diff is collapsed.
source ''
gem 'jekyll', '3.7.4'
gem 'safe_yaml', '~> 1.0.4'
gem 'sass', '~> 3.5'
gem 'libv8', '~>'
gem 'therubyracer'
gem 'fontcustom'
addressable (2.5.2)
public_suffix (>= 2.0.2, < 4.0)
colorator (1.1.0)
concurrent-ruby (1.0.5)
em-websocket (0.5.1)
eventmachine (>= 0.12.9)
http_parser.rb (~> 0.6.0)
eventmachine (1.2.7)
ffi (1.9.25)
fontcustom (2.0.0)
json (~> 1.4)
listen (>= 1.0, < 4.0)
thor (~> 0.14)
forwardable-extended (2.6.0)
http_parser.rb (0.6.0)
i18n (0.9.5)
concurrent-ruby (~> 1.0)
jekyll (3.7.4)
addressable (~> 2.4)
colorator (~> 1.0)
em-websocket (~> 0.5)
i18n (~> 0.7)
jekyll-sass-converter (~> 1.0)
jekyll-watch (~> 2.0)
kramdown (~> 1.14)
liquid (~> 4.0)
mercenary (~> 0.3.3)
pathutil (~> 0.9)
rouge (>= 1.7, < 4)
safe_yaml (~> 1.0)
jekyll-sass-converter (1.5.2)
sass (~> 3.4)
jekyll-watch (2.0.0)
listen (~> 3.0)
json (1.8.6)
kramdown (1.17.0)
libv8 (
liquid (4.0.0)
listen (3.1.5)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
ruby_dep (~> 1.2)
mercenary (0.3.6)
pathutil (0.16.1)
forwardable-extended (~> 2.6)
public_suffix (3.0.3)
rb-fsevent (0.10.3)
rb-inotify (0.9.10)
ffi (>= 0.5.0, < 2)
ref (2.0.0)
rouge (3.2.1)
ruby_dep (1.5.0)
safe_yaml (1.0.4)
sass (3.6.0)
sass-listen (~> 4.0.0)
sass-listen (4.0.0)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
therubyracer (0.12.3)
libv8 (~>
thor (0.20.0)
jekyll (= 3.7.4)
libv8 (~>
safe_yaml (~> 1.0.4)
sass (~> 3.5)
This diff is collapsed.
# Fork Awesome
### A fork of the iconic font and CSS toolkit
[![All Contributors](](
[![Build Status](](
Fork Awesome is a full suite of 744 pictographic icons for easy scalable vector graphics on websites, originally created by [Dave Gandy]( and now maintained by a community.
Following concerns regarding [the development of Font Awesome](, the PR Freeze since Oct 2016 and the direction [Fort Awesome]( is taking with the version 5.0 of their project, we are forking Font Awesome (4.7), in order to build on this amazing tool Dave Gandy has given us, while at the same time allowing this project to be run by a distributed community of contributors.
A tremendous gratitude is given to the whole team behind [Font Awesome](, and you are encouraged to support them and buy Font Awesome Pro for your project.
Though If you believe in distributed open source design and wish to be part of this new adventure, please start submitting patches and suggestions of improvement.
Also, if you care about owning the build process of your icon font, this project will give you that. The whole pipeline is shared and free to use for any purpose. You could be spinning your own icon font with your clever name by just forking this project and changing a few settings.
## How to use
There is a full page in our documentation website that explains [how to use Fork Awesome in your web project]( It ranges from just pointing to a CSS file on a CDN, hosting it on your own server or even adapting the LESS and SCSS files to your own liking.
## License
- The Fork Awesome font is licensed under the SIL OFL 1.1:
- Fork Awesome CSS, LESS, and Sass files are licensed under the MIT License:
- The Fork Awesome documentation is licensed under the CC BY 3.0 License:
## Contributing
Please read through our [contributing guidelines](
Included are directions for opening issues, coding standards, and notes on development.
We also take great pride in recognizing any contributions made to this project. Whether you've written a blogpost about it, fixed a typo in the documentation or submitted new icons or code patches, we will happily list you in our [contributors list](
## Versioning
Fork 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)
* Big changes, without breaking backward compatibility, bumps the minor (and resets the patch)
* Bug fixes, small adaptations, adding a few icons and misc changes bumps the patch
* The fork started from FontAwesome 4.7 (last commit by Dave is [bdfa9823](
* The project starts at version 1.0.0. All references to versions before the fork are named 0.4.7
For more information on SemVer, please visit
## Component
To include as a [component](, just run
$ component install ForkAwesome/Fork-Awesome
Or add
"ForkAwesome/Fork-Awesome": "*"
to the `dependencies` in your `component.json`.
## Building Fork Awesome
**Before you can build the project**, you must first have the following installed:
- [Ruby](
- Ruby Development Headers
- **Ubuntu:** `sudo apt-get install ruby-dev` *(Only if you're __NOT__ using `rbenv` or `rvm`)*
- **Windows:** [DevKit](
- **macOS:** no extra step required
- [Bundler]( (Run `gem install bundler` to install).
- [Node Package Manager (aka. `npm`)](
From the root of the repository, install the tools used to develop.
$ bundle install
$ npm ci
Build the font:
$:/src/icons make
Build the web documentation:
$ npm run build
Or serve it on a local server on http://localhost:7998:
$ npm run dev
safe: false
baseurl: /Fork-Awesome/ # Where GitHub serves the project up from
url: //
safe: false
port: 7998
url: http://localhost:7998
source: src/doc/
destination: _site
highlighter: rouge
permalink: pretty
# ensures SCSS files are compiled
# include: [_*.scss]
# used in building icon pages
icon_meta: src/icons/icons.yml
icon_layout: icon.html # Relative to _layouts directory
icon_destination: icon # Relative to destination
name: Fork Awesome
tagline: A fork of the iconic font and CSS toolkit
version: 1.1.7
minor_version: 1.1
major_version: 1
doc_blob: v1.1.7
css_prefix: fa
font_family: ForkAwesome
project: Fork-Awesome
org: ForkAwesome
version: SIL OFL 1.1
version: MIT License
version: CC BY 3.0
name: Font Awesome
minor_version: 4.7
name: Dave Gandy
twitter: davegandy
github: davegandy
project: Font-Awesome
org: FortAwesome
version: 3.3.5
version: 1.11.3
version: 1.13.1
"name": "fork-awesome",
"description": "Fork Awesome",
"keywords": ["font", "fork", "awesome", "icon" ],
"homepage": "",
"dependencies": {},
"devDependencies": {},
"license": ["OFL-1.1", "MIT", "CC-BY-3.0"],
"main": [
"ignore": [
"name": "fork-awesome",
"repo": "ForkAwesome/Fork-Awesome",
"description": "Fork Awesome",
"version": "1.1.7",
"keywords": [],
"dependencies": {},
"development": {},
"license": "SIL, MIT, CC BY 3.0",
"styles": [
"fonts": [
"name": "forkawesome/fork-awesome",
"description": "A fork of the iconic font and CSS framework",
"keywords": ["font", "awesome", "fontawesome", "forkawesome", "icon", "bootstrap"],
"homepage": "",
"type": "component",