This is RichStone's collection of different types of READMEs. Check out the types folder for more types or let me know about new cool READMEs :)
this README.md template was originally created by Dan Bader and extend by RichStone
An example project that uses this extensive template is my data collection tool
(let me know if you need any translations of the template.)
Short blurb about what your product does.
One to two paragraph statement about your product and what it does.
OS X & Linux:
npm install my-crazy-module --saveWindows:
edit autoexec.batA few motivating and useful examples of how your product can be used. Spice this up with code blocks and potentially more screenshots.
For more examples and usage, please refer to the Wiki.
Describe how to install all development dependencies and how to run an automated test-suite of some kind. Potentially do this for multiple platforms.
make install
npm test- 0.2.1
- CHANGE: Update docs (module code remains unchanged)
- 0.2.0
- CHANGE: Remove
setDefaultXYZ() - ADD: Add
init()
- CHANGE: Remove
- 0.1.1
- FIX: Crash when calling
baz()(Thanks @GenerousContributorName!)
- FIX: Crash when calling
- 0.1.0
- The first proper release
- CHANGE: Rename
foo()tobar()
- 0.0.1
- Work in progress
Your Name – @YourTwitter – YourEmail@example.com
Distributed under the XYZ license. See LICENSE for more information.
https://github.com/yourname/github-link
- Fork it (https://github.com/yourname/yourproject/fork)
- Create your feature branch (
git checkout -b feature/fooBar) - Commit your changes (
git commit -am 'Add some fooBar') - Push to the branch (
git push origin feature/fooBar) - Create a new Pull Request
- Feature One
- Feature Two
- refactor this
- refactor that
Use Future Features and Neccessary Refactorings rather sparingly and only as long as collaboration and project size are overseeable.
Let people know how you worked on this project.
- How did you plan it?
- How much time did it take?
- What was easy, where did you struggle? e.g.: this project
