-
-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for flat icons #10
Comments
I'm planning to support flat badge, thinking use |
It's online now https://flat.badgen.net 🤗 |
Nice! 🤘 |
Why .net instead of the .now.sh TLD? |
BTW, As of (1), I even thought about shrink |
Well the original badge is:
Why not use this for flat badges:
|
I guess my point is: the domain name should remain the same, regardless of the "style" of badge. |
That's ok for static badge, but a little complicated for live badges |
Segments in URL are like arguments for functions, I wish to keep them as less as possible |
I see what you mean. So changing the route isn't really an option. I think it's fine to add a query string parameter for badge style. This is what shields does: https://img.shields.io/npm/v/copee.svg This also gives you flexibility if you want to add more options, no need to mess with the routes. |
I'm OK with query string, just not a fan of it. I was thinking if we could offer a better option than Shields does? My thoughts on this can be divided into two parts: Is there a better way for switching badge style?What about put that info into hostname, compare these:
I prefer the latter one. This also brings an extra benefit: we could easily serve a full preview of all flat badges within a single server(
I like the simplicity. And there's another extra benefit 🤪: Put "flat" in the hostname makes it feels more "official" like, stand at the same level as "classic" style. After all, if someone want to use flat style badge, he would use it on all badges rather than in a mixed style, I was think of this recently, to provide consistent style across all badges could be a goal/value of Badgen. That's why Badgen use to redirect That's why I tend to use hostname to switch style. If so, (the second part): What hostname looks better?Here's some options came to me:
(3) looks best in this situation 😋 |
Yes that's a good point I didn't consider, but surely this could be accomplished with a query string parameter and maybe a dropdown to pick the style. Take a look at https://shields.io/#styles which also shows additional options beyond
Yep, I agree, that's a good goal.
If I had to pick, 3 would be best. One thing to note is that shields calls this style |
I'm agree too. In anyway there should have support for query params anyway. Because there we should allow passing Lets have both And actually i'm agree with @styfle for the naming. It may be confusing, but it would suck if we name it |
Just realizing that I just tried and we don't have way to get queryparams with this router. I highly think to start a branch with |
@olstenlarck As the
I like |
Exactly. Why not? Even more, we need just As about the proposals.. i'm for |
Overall I haven't do benchmarks but from the docs,
|
Oh, don't why i thought they parse them, hm. Anyway, cool for the |
😂 Just thought the shape of fork kinda like paths of route. Maybe I should create a logo for explanation. |
and nodemon => micro-dev and support query params: style, label, emoji, list Regarding #10 (comment)
https://flat.badgen.net online now 💃 |
I think it would be better the "Query Params" to be on the top of the site, between "Usage" and the "Examples" sections. Because badges number will grow. Also think that |
@olstenlarck Fixed in #32 |
Agree 👍 At first I put that block on top, latter change to bottom for a little nicer(very opinionated) first screen. I'm planing move index.md to a fully customizable jsx page, with more refinement on the looks, I'll be happy to move "Query Params" to top. |
I see that you support flat badges in
badgen
, are they supported here? I'm not seeing anything about flat icons inside the docs.The text was updated successfully, but these errors were encountered: