Closed wappsdotgr closed 6 years ago
As the icon count increases it would be a good idea to add categories (file,devices,social,bla bla...) and/or search at the showcase page (https://feather.netlify.com/)
Absolutely. Adding search to the project page is next on my agenda. I'd love to split the set into categories but I'm struggling to come up with good category names. Do you have any ideas?
You could add a boilerplate (AI,EPS,whatever) with guides so we can contribute by sending you a new icon which you can fine-tune and include in the set or just dismiss it. This could also be done via wiki if you provide some ground rules (artboard=24x24pt / stroke = 2pt / artboard padding / etc)
Great idea. After I launch v2.0.0, I'm planning to write up some Design Guidelines including some simple rules, a boilerplate template, and instructions for contributing. I'd love to start taking contributions from the community!
For whoever prefers using iconfont will you be updating the icon set at https://icomoon.io/app/ ?
I'm not sure who can update the icomoon set but it looks like it's been updated recently. The Feather set on icomoon now contains 163 icons (up from 130). https://icomoon.io/app/#/select/library
Thanks for the great suggestions!
About:
PS: Idk if here is the place to post it but I attached a "user-delete" icon which is your "user-plus" one with the "+" rotated. You probably have the "user-minus" covering that usage but seems kinda odd. The extension is txt and not svg due to github attaching limitation. user-delete.txt
Thanks for the icon! Maybe I'll add user-check
and user-x
icons to keep things consistent.
I'll have to think about the icon font. I tend to discourage the use of icon fonts in general because I think SVGs are a much better alternative. Also, tools like Icomoon make it super easy to generate your own icon font from a set of SVGs. I would argue that using Icomoon is actually better because you can create a set with only the icons you need.
Here are some good articles comparing SVG to icon fonts:
I ve read those articles from your changelog, personally I think both svgs and iconfonts have optimal use-cases. Due to icomoon's restriction of stroke shaped svgs I guess I could fork your repo, expand shapes and have only the converted icons for icomoon usage (if you are ok with this ofc).
Also, I ll research and try to setup some categories to send you. I hope you find them usefull (may take some days, im a little busy right now)
Thx for your replies m8, looking forward for Feather 2.0 and for boilerplates to start contributing icons :)
Feel free to customize Feather however you'd like!
I didn't know Icomoon had that restriction. The built-in Feather icon library seems to work fine though. Someone must have converted strokes to outlines.
Hey, i didnt have time to research more, hope the following are enough to get you started for whatever you end up with :)
Some categories not analyzed:
Some analyzed:
Some resources:
Ridiculously categorized icons collection:
Thanks so much for doing that research! That's more than enough to get me started ๐
I found a reference to his iconset in a project I stopped working on ages ago (https://hikar.io). I'm working on it again and am pleased to see that you're still working on Feather!
Highjacked this thread to say thanks.
@NetOperatorWibby Thank you for the kind words! ๐
There is a way to use svg icon with the same ease than iconfont ?
Possible experiment
.fth.fth-box::before {
width: 20px;
height: 20px;
display: inline-block;
content: url(icons/core/box.svg);
}
@Swizz That's an interesting idea. One issue with this approach is that when content
is used to display an SVG, we are no longer able to control attributes of that SVG. For example, we'd have no control over the stroke
color or stroke-width
of the icons.
And what about inheritance ?
<svg [...] width="inherit" height="inherit" fill="inherit" stroke="inherit" stroke-width="inherit">
<path [...] fill="inherit" stroke="inherit" stroke-width="inherit"/>
<polyline [...] fill="inherit" stroke="inherit" stroke-width="inherit"/>
<line [...] fill="inherit" stroke="inherit" stroke-width="inherit"/>
<line [...] fill="inherit" stroke="inherit" stroke-width="inherit"/>
</svg>
.fth.fth-package {
width: 200px;
height: 200px;
fill: none;
stroke: #0f0f0f;
stroke-width: 2;
display: inline-block;
}
Work well with svg in place not with content...
The next idea, could be the use of svg <symbol>
and svg <use>
Any update on the boilerplate/template?
- You could add a boilerplate (AI,EPS,whatever) with guides so we can contribute by sending you a new icon which you can fine-tune and include in the set or just dismiss it. This could also be done via wiki if you provide some ground rules (artboard=24x24pt / stroke = 2pt / artboard padding / etc)
Are there any plans to provide the feather icon set in the ttf or otf format, similar to FontAwesome? I would like to use this superb icon set to customize my desktop environemt.
@Colebemis provided some stuff about that : https://github.com/colebemis/feather/issues/8#issuecomment-302803298
Anyways, awesome work m8, keep it up!