Skip to content

Latest commit

 

History

History
119 lines (78 loc) · 4.71 KB

README.md

File metadata and controls

119 lines (78 loc) · 4.71 KB
Raw

Your-Project-Title

Description

Provide a short description explaining the what, why, and how of your project. Use the following questions as a guide:

  • What was your motivation?
  • Why did you build this project? (Note: the answer is not "Because it was a homework assignment.")
  • What problem does it solve?
  • What did you learn?

Built With

This section should list any major frameworks/libraries used to bootstrap your project. Leave any add-ons/plugins for the acknowledgements section. Here are a few examples.

Installation

What are the steps required to install your project? Provide a step-by-step description of how to get the development environment running.

Usage

Provide instructions and examples for use. Include screenshots as needed.

Project Screen Shot

To add a screenshot, create an assets/images folder in your repository and upload your screenshot to it. Then, using the relative filepath, add it to your README using the following syntax:

```md
![alt text](assets/images/screenshot.png)
```

Roadmap

  • Add Changelog
  • Add back to top links
  • Add Additional Templates w/ Examples
  • Add "components" document to easily copy & paste sections of the readme
  • Multi-language Support
    • Chinese
    • Spanish

See the open issues for a full list of proposed features (and known issues).

Features

If your project has a lot of features, list them here.

Tests

Go the extra mile and write tests for your application. Then provide examples on how to run them here.

Version History

Credits

List your collaborators, if any, with links to their GitHub profiles.

If you used any third-party assets that require attribution, list the creators with links to their primary web presence in this section.

If you followed tutorials, include links to those here as well.

License

The last section of a high-quality README file is the license. This lets other developers know what they can and cannot do with your project. If you need help choosing a license, refer to https://choosealicense.com/.

How to Contribute

If you created an application or package and would like other developers to contribute it, you can include guidelines for how to do so. The Contributor Covenant is an industry standard, but you can always write your own if you'd prefer.

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

Contact

Your Name - @your_twitter - [email protected]

Project Link: https://github.com/your_username/repo_name

Acknowledgments

Inspiration, code snippets, etc.