shields.io rebranding #82
Comments
|
I don't think it's worth the effort to try to correct the entire world in its use of a proper descriptor. These things are all badges. Not all of them are Shields badges: Travis, Code Climate, Coveralls, Gemfury and Gemnasium all happen to be using Shields badges. There are many people out there trying to imitate the style with varying degrees of success and many more who don't really seem to understand (or know) how important information design is. If the purpose of this issue was to have all these different services to refer to badges as Shields, I'd rather we close it. |
|
This was written before @whit537 filled me in on the backstory of renaming badgr to shields. It was a question of how we're marketing ourselves. How does someone using Travis CI badge know the badge is from Shields.io and therefore support Shields? You used the words "Shields badge", so I guess we can still refer to these as badges (like everyone does) but hopefully say "badges provided by Shields.io" |
ghost
assigned
|
While I agree with not trying to change everyone to call badges shields instead, I think "badges provided by Shields.io" is relevant to the content @bryanveloso uses for the new web site, in the part targeting sites/companies offering the badges. |
+1 |
|
@nathany What's the action item on this ticket? |
|
Let's close it. We can open a new ticket for content/terminology as part of #90 issue reorg. |
Per #82 (comment), we're calling these "Shields badges" or "badges by Shields."
On #82 (comment) we decided to refer to "badges by Shields." We're not trying to change the name of the thing itself to a "shield."
and others
I'm still getting used to calling these things shields #63, and spelling shields correctly. (i before e) :-P Personally I rather like "badgr" but now that we're calling this thing Shields, what can be done about:
The text was updated successfully, but these errors were encountered: