file-icons

Open source

Crispy, file-specific vector icons for improved visual grepping.

Become a contributor

Financial contributions

Custom contribution

Donation

Make a custom one time or recurring contribution.

1 individual and 3 organizations have contributed

Recurring contribution

backer

Become a backer for $5.00 per month and help us sustain our activities!

$5 USD / month

1 organization has contributed

Recurring contribution

sponsor

Become a sponsor for $100.00 per month and help us sustain our activities!

$100 USD / month

1 organization has contributed

Top financial contributors

Organizations

1
Tipe

$700 USD since Jul 2018

2
Triplebyte

$50 USD since Jan 2019

3
TakeShape

$45 USD since Mar 2019

Individuals

1
Justin Ireland

$50 USD since Jan 2019

Budget

See how money openly circulates through file-icons. All contributions and all expenses are published in our transparent public ledger. Learn who is donating, how much, where is that money going, submit expenses, get reimbursed and more!

2-night accommodation

by John Gardner6/17/2020

-$63.44USD
Paid
Receipt #20429

Project maintenance

by John Gardner6/16/2020

-$599.00USD
Paid
Invoice #20289

Monthly financial contribution to file-icons (backer)

from TakeShape11/1/2019

+$5.00USD
Completed

Today’s balance

$0.42 USD

Estimated annual budget

~ $8.10 USD

file-icons is all of us

Our contributors 5

Everyone who has supported file-icons. Individuals and organizations that believe in –and take ownership of– our purpose.

Tipe
Financial Contributor

Total contributions

$700 USD

Tipe

Justin Ireland
Financial Contributor

Total contributions

$50 USD

Triplebyte
Financial Contributor

Total contributions

$50 USD

TakeShape
Financial Contributor

Total contributions

$45 USD

backer

About

There are two parts to the project:

  1. An icon set. These icons are carefully cleaned up by hand in Adobe Illustrator to be as sharp as possible at 16×16px size, eliminating excess geometry, spacing details that become blurry at small sizes, etc.

  2. A file-recognition API. Or at least, I hope to extend it to become one. Its original focus was more narrow and Atom-specific, but I'd like to replace this with something that can benefit any JS environment (browsers, other editors, Node programs, etc).

The problems:

  1. I've used Adobe software for ~11 years, and I'm very fast with it. Sadly, my subscription expired and I can't afford to renew it. Of course I can use Inkscape, but I work painfully slow and I'm learning how to ride a bike all over again.

  2. I need a new MacBook because the last one "mysteriously" broke (specifically, the screen cracked and I never found out why). My remaining computers are an old laptop (this thing) and a desktop computer I have sporadic access to. The laptop runs OpenBSD (which has no Atom support) and the desktop runs Linux (which DOES have Atom support, but it's shared and I can't guarantee my access.

  3. Not having money to fix either of the above sucks. Being jobless sucks. Having to panhandle for hardware money sucks, and I wouldn't be doing this had somebody not mentioned it.

Oh yeah, and I use Atom for previewing/developing syntax highlighting grammars that're used across GitHub (That's completely unrelated to this of course, I know).