A/B Testings Button Color?

[chadwhitacre]

Reticketing from a private Gratipay email support request:

The "Support via Gratipay" button's green is (nearly?) the same as the build passing color, I didn't even recognize it as actionable or something besides a code quality metric of some kind.

I think changing the color (as a simple testable factor) could have a significant effect on folk's propensity to click it (tip/sign up?).

I wouldn't have written in normally, but I really like the idea of contributing some beers/coffees ($$$) to folks for creating and sharing great work. So I took a moment to think about why the button wasn't noticed by me upon first glance.

Good luck! Hope this isn't beating a dead horse for y'all (i.e. you're already doing it/well aware).

[twolfson]

I am open to trying out different colors. The initial coloring is the same gradient as GitHub's CSS to make it feel like a GitHub button.

However, I should mention that there are other badges that use other colors entirely (e.g. blue, orange):

http://shields.io/

I believe the root cause of our anonymous requester's problem is that there is no hierarchical distinction between badges (i.e. nothing delimiting they are in separate sections/should be considered separate content). I prefer to solve this by providing the "Support badge" after some introductory text to indicate it's an action.

https://github.com/gratipay/gratipay-badge/tree/2.3.0#donating

Here's an example of people using a Heroku button with a similar delineation:

https://github.com/rauchg/slackin/tree/0.5.0#how-to-use