Skip to content
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

shields.io rebranding #82

Closed
nathany opened this issue Nov 16, 2013 · 7 comments
Closed

shields.io rebranding #82

nathany opened this issue Nov 16, 2013 · 7 comments
Labels
question Support questions, usage questions, unconfirmed bugs, discussions, ideas
Milestone

Comments

@nathany
Copy link
Contributor

nathany commented Nov 16, 2013

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:

@olivierlacan
Copy link
Member

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.

@thedrow
Copy link

thedrow commented Dec 5, 2013

I agree with @olivierlacan.

@nathany
Copy link
Contributor Author

nathany commented Dec 5, 2013

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 ghost assigned bryanveloso Jan 3, 2014
@nathany
Copy link
Contributor Author

nathany commented Jan 3, 2014

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.

@chadwhitacre
Copy link
Contributor

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

@chadwhitacre
Copy link
Contributor

@nathany What's the action item on this ticket?

@nathany
Copy link
Contributor Author

nathany commented Jan 3, 2014

Let's close it. We can open a new ticket for content/terminology as part of #90 issue reorg.

@nathany nathany closed this as completed Jan 3, 2014
chadwhitacre added a commit that referenced this issue Jan 9, 2014
Per #82 (comment),
we're calling these "Shields badges" or "badges by Shields."
chadwhitacre added a commit that referenced this issue Jan 15, 2014
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."
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Support questions, usage questions, unconfirmed bugs, discussions, ideas
Projects
None yet
Development

No branches or pull requests

5 participants