I was thinking about creating a “built with Meteor” badge with shields.io to put in my repositories.
I wanted to ask the community here because maybe we can agree on a style so we can all use it.
What do you all think?
11 Likes
I don’t have any suggestions, I just wanted to say I’d add it to my meteor projects if it were available.
2 Likes
I love the idea! Will make it easy to quickly see if it is a Meteor project. Using a Meteor logo is a must. Maybe adding a Meteor version tag could be useful as well.
1 Like
Some inspirations:
Using the color of the logo (#df4f4f):
Using the color of the get started button on the Meteor website (#595dff):
Variations with white logo:
Using the color of the logo (#df4f4f):
Using the color of the get started button on the Meteor website (#595dff):
Edit:
I haven’t figured out the shields.io query system but I think it would be possible to read the Meteor release version from the project’s repo. If I found out, I could create a PR on the shields repo to make the Meteor shield being configurable easily in the version page.
If the links don’t show a badge you can also copy the URL in the browser address bar.
2 Likes
Looks good. A stretch goal would be that the background color should be red if not the most current version and some other color when up-to-date, but I think I want too much. 
Maybe we could define, how many minor versions behind the latest is okay?
For example 1.9.2 is still okay and should not be red red red bad etc. but I think 1.7 has already security implications. Maybe we say
- v == latest = green
- latest > v > latest - 2 = orange
- v < latest - 2 = red
I am still analyzing the shields.io repo. Basically I could go for a PR so you can dynamically get the badge from shields using a query by your given GitHub repository where the project is placed.
It should then search in the folder recursively for a .meter/release pattern and use this entry for generating the badge.
Similar could be done for atmosphere packages that are hosted on GitHub.
2 Likes