Project Name
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,
- Travis CI
- AppVeyor
- Coveralls
- Gitter
- Shields.io
- Others
Features or Example
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.
Motivation
A short description of the motivation behind the creation and maintenance of the project. This should explain why the project exists.
Requirements
This section is optional if there isn't any special dependencies. Else a bulletlist will suffice, e.g.,
Installation or Getting Started
Provide code examples and explanations of how to get the project, e.g.,
git clone https://github.com/Jasonnor/README.md.git
cd README.md
npm install README.md
npm start
Usage
Show how to use the project or library.
Reference
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.
Contributors
Let people know how they can dive into the project, include important links to things like issue trackers, irc, twitter accounts if applicable.