Name of the project
Additional information or tagline
A brief description of your project, what it is used for and how does life get awesome when someone starts to use it.
Installing / Getting started
A quick introduction of the minimal setup you need to get a hello world up & running.
packagemanager install awesome-project awesome-project start awesome-project "Do something!" # prints "Nah."
Here you should say what actually happens when you execute the code above.
Some projects require initial configuration (e.g. access tokens or keys,
This is the section where you would document those requirements.
Here's a brief intro about what a developer must do in order to start developing the project further:
git clone https://github.com/your/awesome-project.git cd awesome-project/ packagemanager install
And state what happens step-by-step.
If your project needs some additional steps for the developer to build the project after some code changes, state them here:
./configure make make install
Here again you should state what actually happens when the code above gets executed.
Deploying / Publishing
In case there's some step you have to take that publishes this project to a server, this is the right time to state it.
packagemanager deploy awesome-project -s server.com -u username -p password
And again you'd need to tell what the previous code actually does.
What's all the bells and whistles this project can perform?
- What's the main functionality
- You can also do another thing
- If you get really randy, you can even do this
Here you should write what are all of the configurations a user can enter when using the project.
State what an argument does and how you can use it. If needed, you can provide an example below.
awesome-project "Some other value" # Prints "You're nailing this readme!"
Copy-paste as many of these as you need.
When you publish something open source, one of the greatest motivations is that anyone can just jump in and start contributing to your project.
These paragraphs are meant to welcome those kind souls to feel that they are needed. You should state something like:
"If you'd like to contribute, please fork the repository and use a feature branch. Pull requests are warmly welcome."
If there's anything else the developer needs to know (e.g. the code style
guide), you should link it here. If there's a lot of things to take into
consideration, it is common to separate this section to its own file called
CONTRIBUTING.md (or similar). If so, you should say that it exists here.
Even though this information can be found inside the project on machine-readable format like in a .json file, it's good to include a summary of most useful links to humans using your project. You can include links like:
- Project homepage: https://your.github.com/awesome-project/
- Repository: https://github.com/your/awesome-project/
- Issue tracker: https://github.com/your/awesome-project/issues
- In case of sensitive bugs like security vulnerabilities, please contact firstname.lastname@example.org directly instead of using issue tracker. We value your effort to improve the security and privacy of this project!
- Related projects:
One really important part: Give your project a proper license. Here you should state what the license is and how to find the text version of the license. Something like:
"The code in this project is licensed under MIT license."