-
Notifications
You must be signed in to change notification settings - Fork 85
GitHub badges in SVG format #150
Comments
WoW! Loved the idea. 👍 |
a big 👍 |
👍 |
@mathiasbynens Have you seen this repo? |
@fhemberger Awesome! It looks like the generated code in that repo could be improved/cleaned up a little bit, but other than that it looks like the first task on the TODO list is as good as finished :) |
Tried something quick here: https://thefiletree.com/gh-badges/build-passed.svg However, in stable Firefox, |
👍 Relevant: badges/shields#80 |
I think I have something competitive here: [gist] https://gist.github.com/espadrine/8218740 Fork this gist to add images! |
Quick size comparison:
|
@espadrine Nice! (I was the one who helped a little bit, but really you really did all the hard work :)) How about setting up a repository for this instead of a gist? Would make it a better place to point to, as we could add documentation for badge services (i.e. how to change |
Any reason these couldn't simply be HTML / CSS? |
@simonowendesign Because |
@espadrine created a repo for the SVG badge boilerplate/template: https://github.com/espadrine/gh-badges Feedback and improvements on the code are welcome there! |
I get that if an image tag has been previously used SVG would be the right way to go, but wondering if an imageless alternative would be beneficial as well going forward? |
@simonowendesign |
@simonowendesign Everything but an image makes embedding in Markdown or reStructuredText (that's what most READMEs on Github are written in) unnecessarily complicated. Images can be embedded like this in Markdown:
"imageless" would mean adding HTML and CSS to a Markdown document which is ugly. Or using |
Not just ugly, but (more importantly) it would also mean that the content wouldn’t be dynamic anymore. |
Gotcha, and guess something like a button styling for Markdown would be overkill? |
Definitely :) Also it would have the same issue: in this case, the content must come from a third party server (not from the README source itself). |
Good news! This is now pretty much solved by http://gh-badges.herokuapp.com/ (repo: https://github.com/espadrine/gh-badges). There are just a few annoying browser bugs in the way of using these beautiful SVG badges: badges/gh-badges#5 |
Cross-post from badges/shields#80 (comment) :
|
Hi, thank for the service. |
@hhfrancois Thanks for telling us! We hope we fixed it. Tell us if it works better. As a side-node, it may be unstable this week, but will be better next week. |
@espadrine Thank for the response. |
@espadrine I don't find a better place to ask this: How about adding beerpay.io as well? |
@svoop Don't hesitate to create an issue on the project! |
hi, all i can easily get unresponsive state. |
here from here |
… since it stop working.
A lot of GitHub repositories have badges like these in their README:
There are several services that can be used to serve these badge images based on some URL parameters, e.g. shields.io (repo).
Currently these badges are all bitmaps (usually in JPG or PNG format). It would be nice to have them in SVG format, for the following reasons:
TODO
Any SVG gurus/ninjas/unicorns out there that want to give the first task a try?
The text was updated successfully, but these errors were encountered: