Readme.md template with best practices
Short introduction or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
You can also add some badges/states next to Project Name, e.g,
Do you have a README(.md) that explains the following things?
You can remove this section after finishing.
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.
A short description of the motivation behind the creation and maintenance of the project. This should explain why the project exists.
This section is optional if there isn’t any special dependencies. Else a bulletlist will suffice, e.g.,
What things you need to install the software and how to install them:
Give examples
Provide code examples and explanations of how to get the project, e.g.,
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
git clone https://github.com/Jasonnor/README.md.gitcd README.mdnpm install README.mdnpm start
Show how to use the project or library.
Depending on the size of the project, if it is small and simple enough the reference docs can be added to the README. For medium size to larger projects it is important to at least provide a link to where the API reference docs live.
Let people know how they can dive into the project, include important links to things like issue trackers, irc, twitter accounts if applicable.
See also the list of contributors who participated in this project.
This project is licensed under the MIT License - see the LICENSE.md file for details