-
Notifications
You must be signed in to change notification settings - Fork 92
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
Consider also providing a badge #141
Comments
Nice! I like it. |
Shields are usually for status; not call to action. I personally don't click on them often. Would this be an alternative "button"? |
I think it's known that even for status, clicking on them leads you somewhere. Just an idea, as I was playing with GitPod and saw that's what they do. |
I can't point to research, but I've heard folks use the presence of ecosystem appropriate buttons on a README as a sign the repo is well-integrated with it's community. Personally I look for and click on them to do things like get to package repositories, find docs, check build status. I would not expect clicking on them to lead me into a flow where a VM is launched, but I could see it going to a landing page explaining "Hey, click this larger button and we'll deploy to Cloud Run". Not sure that has value unless we can show stats or something else of interest on that page. |
Many GitHub READMEs have badges at the top.
We could create a ΅Run on Google Cloud" badge as an alternate version of the button, quick prototype:
This is for example what GitPod does:
The text was updated successfully, but these errors were encountered: