a525dfa28f
When we try to add a badge service to [visual studio gallery](visualstudiogallery.msdn.microsoft.com), we find Shield is the best option but there is no .NET implementation. So we port it to [.NET](https://github.com/rebornix/DotBadge) for better code integration. I'll appreciate it if you can add a link to C# port of Shield badge library and CLI, which can bring more audience to this tiny draft project. But we can understand if you don't, as it's not an official one :) |
||
|---|---|---|
| ass-stubs | ||
| spec | ||
| templates | ||
| .buildpacks | ||
| .gitignore | ||
| .travis.yml | ||
| 404.html | ||
| badge.js | ||
| CNAME | ||
| colorscheme.json | ||
| CONTRIBUTING.md | ||
| coverage.svg | ||
| Dockerfile | ||
| favicon.png | ||
| gh-badge.js | ||
| index.html | ||
| INSTALL.md | ||
| LICENSE.md | ||
| logo.svg | ||
| lru-cache.js | ||
| Makefile | ||
| package.json | ||
| phantomjs-svg2png.js | ||
| README.md | ||
| server.js | ||
| suggest.js | ||
| svg-to-img.js | ||
| test.js | ||
| try.html | ||
Shields 
An image server for legible & concise information.
Installation Instructions: INSTALL.md.
Contributions: CONTRIBUTING.md.
Specification: SPECIFICATION.md.
License: LICENSE.md.
Problem
Many GitHub repos sport badges for things like:
- Travis CI build status:
- Gemnasium dependency checks:
- RubyGems released gem version:
As you can see from the zoomed 400% versions of these badges above, nobody is (really) using the same badge file and at normal size, they're hardly legible. Worst of all, they're completely inconsistent. The information provided isn't of the same kind on each badge. The context is blurry, which doesn't make for a straightforward understanding of how these badges are relevant to the project they're attached to and what information they provide.
Solution
As you can see below, without increasing the footprint of these badges, I've tried to increase legibility and coherence, removing useless text to decrease the horizontal length in the (likely) scenario that more of these badge thingies crop up on READMEs all across the land.
This badge design corresponds to an old and now deprecated version which has since been replaced by beautiful and scalable SVG versions that can be found on shields.io.
Examples
What kind of meta data can you convey using badges?
- test build status:
build | failing - code coverage percentage:
coverage | 80% - stable release version:
version | 1.2.3 - package manager release:
gem | 1.2.3 - status of third-party dependencies:
dependencies | out-of-date - static code analysis GPA:
code climate | 3.8 - semver version observance:
semver | 2.0.0 - amount of gratipay donations per week:
tips | $2/week