Skip to content

Instantly share code, notes, and snippets.

@lktslionel
Last active January 31, 2023 08:52
Show Gist options
  • Save lktslionel/9cc85d3a636962eaf472fb0022460a27 to your computer and use it in GitHub Desktop.
Save lktslionel/9cc85d3a636962eaf472fb0022460a27 to your computer and use it in GitHub Desktop.
https://excalidraw.com/#json=pfPDpI2_tY4RdrhkZpAmQ,ZeanSwLNWUmcebxTqPLfKg

{{ hero image }}

docker/image Image from skillsicons

{{ SCOPE }}

{{ Project Name}}

{{ Description }}

{{ Goals}}

{{ Features }}

Bagdes

status/exprimental

status/active

status/retired

status/retired

release/X.Y.z


Contents




1 Overview

dfdf

1.1 Prerequisites


2 Quickstart

2.1 Install

Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.

2.2 Usage

Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.

2.3 Demo

2.4 Uninstall

Show instructions

Step 1:

Step 2:


3 Learning

3.1 How-tos

3.2 Tutorials

3.3 Resources


4 Roadmap

If you have ideas for releases in the future, it is a good idea to list them in the README.


5 References

5.1 Concepts

5.2 Motivation

5.3 Testing


6 Contributing

6.1 Instructions

Fork it (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

6.2 Code of Conduct


7 Feedback & Support

Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.

7.1 Feedback

  • Ask a question on Stack Overflow
  • Request a new feature
  • Upvote popular feature requests
  • File an issue
  • Follow @code and let us know what you think!

7.2 Help

7.3 Sponsors



8 Acknowledgments

Show your appreciation to those who have contributed to the project.

9 Maintainer(s)


10 License

For open source projects, say how it is licensed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment