Skip to content

Latest commit

 

History

History
52 lines (30 loc) · 1.78 KB

CONTRIBUTING.md

File metadata and controls

52 lines (30 loc) · 1.78 KB
Raw

Welcome to GitHub docs contributing guide

Thank you for investing your time in contributing to our project! Just to let you know, your contribution is reflected in the readme.

Read our Code of Conduct to keep our community approachable and respectable.

Contributor Guidelines

We follow the same guidelines used by Awesome. To add, update, or remove the item in our project.

Do Not

  • We do not accept any promotion links.

Do It

  • We accept only those packages actively contributed by the maintainer or community.

How to contribute

You start to contribute with the following syntax. Could you make sure you do not add any promotions or spam links?

Adding subcategory

Your subcategory is not listed there, and you can create a subcategory yourself.

## Name of the subcategory

Adding item

Using the following syntax, you can add any npm package or library in the existing subcategory.

- [title](link) : Basic introduction.

Make changes locally

  1. Fork the repository and install the package using the node package manager (npm, yarn, or pnpm).
  2. Adding a new package, library, tool, and template name.
  3. You can explain the package, library, tool, and template you added; if Your package category does not exist, you can also create it.
  4. Lastly, run pnpm format and pnpm lint to format and fix the lint issue before applying the pull request.

Commit your update

Commit the changes once you are happy with them. Ensure that the document does not contain grammar mistakes and that your package name and link work properly.

Pull Request

When you're finished with the changes, create a pull request called a PR. Your PR is merged!