We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
a continues of #41
We have a leftover from that issue to create a npm button as well to point to our npm tdd1t page.
npm
Also, while doing that, I suggest we change the buttons to use shields.io which can show the version number and add a logo.
So, here are the two github and npm buttons with shields.io:
Should be pretty much copy paste since the style itself is defined by the svgs.
I would suggest both buttons should inhabit a single line with a little margin between them, in the same location as the tdd1t on GitHub button.
tdd1t on GitHub
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered:
For social buttons, we can also use shields.io There might be more buttons worth adding, but here's my list:
Twitter:
GitHub Fork:
Linkedin:
These should also inhabit the same line as the last thing in the footer
Sorry, something went wrong.
No branches or pull requests
Add NPM & Social buttons to homepage
Feature
a continues of #41
We have a leftover from that issue to create a
npm
button as well to point to our npm tdd1t page.Also, while doing that, I suggest we change the buttons to use shields.io which can show the version number and add a logo.
So, here are the two github and npm buttons with shields.io:
Should be pretty much copy paste since the style itself is defined by the svgs.
I would suggest both buttons should inhabit a single line with a little margin between them, in the same location as the
tdd1t on GitHub
button.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: