Awesome

font-logos

font-logos is an icon font containing logos of popular linux distributions and other open source software.

Note: All brand icons are trademarks of their respective owners and should only be used to represent the company or product to which they refer.

Installation

Install the font by downloading and unpacking the latest release's zip manually or installing it from npm:

npm install font-logos

To use the font, include assets/font-logos.css as well as the fonts in your project and use the CSS classes listed below.

<link href="/assets/font-logos.css" rel="stylesheet">

Alternatively just link to it using a CDN such as jsDelivr:

<link href="//cdn.jsdelivr.net/npm/font-logos@1/assets/font-logos.css" rel="stylesheet">

Usage

Include an icon using the corresponding CSS class in an empty element:

<i class="fl-[icon]"></i>

Add fl-fw as class for a fixed width icon.

If you want to insert a glyph of this font on a GNU/Linux system press Ctrl + Shift + u, release the keys and then type the code point, for instance: Ctrl + Shift + u and f31a will insert the Tux glyph.

Available logos are:

Building

Make sure you have the following dependencies installed:

• Node, Python and jq to run the build scripts
• FontForge to generate the fonts
• wkhtmltopdf to generate this readme's preview image

Then run npm install/yarn install and make.

Releasing

If you are a maintainer of this repository and a new release is to be published

• Make sure all PRs (that shall be pulled) are pulled
  • The PRs add new svgs in vectors/
  • The icons.tsv is ammended (i.e. new icons added at the bottom)
• Every time the svgs or icons.tsv is touched in the master branch (i.e. through pulling) the preview image is updated
• Note that the README.md is NOT updated. You can manually modify it to indicate/add recently added but not released icons.
• Once the release seems ready:
• Edit the version number in package.json (and push that change to master)
• Trigger the "Draft a Release" workflow manually on the Actions page (on the master branch)
  • The workflow will add a git tag for the release
• Go to the releases list and find the draft release
  • Edit the description etc pp and finally
  • Push "publish release"
  • The release is published on Github
• Automatically the "Update README" workflow is triggered
  • The README.md is regenerated (the preview should already be up to date, see above)
  • Maybe the autotriggered workflow does not work, then manually trigger
• Automatically the "Publish release to npm" workflow is triggered
  • If the npm token is not expired the release is pushed to NPM
  • You need to publish on NPM manually if token is expired (expected)
    • npm update (and commit/push updates if there were any)
    • npm adduser to log into npm with MFA
    • npm publish