docs: create contribute section

Author: developer-bandi

website/docs/contributing/development.mdx

@@ -0,0 +1,23 @@
+---
+sidebar_position: 2
+---
+
+The repository is structured as a yarn monorepo and largely consists of codemod-kit packages and a website.
+
+First, run yarn install to install dependencies.
+
+## packages
+
+The main function of the package is to execute predefined transforms using jscodeshift.
+
+This package mainly consists of two files for providing cli and programmatic methods, and one more file for running the transformer in a browser.
+
+When adding new transformers or options, please take care to add test code and documentation for them.
+
+## webstie
+
+The website is built with docusarus and can be run from root via `yarn start:website`.
+
+If you want to edit a document, try editing it in the docs or transformer folder.
+
+If you need to modify a playground, browse inside `src/page/playground`.

website/docs/contributing/index.md

@@ -0,0 +1,19 @@
+---
+id: contributing
+title: Contributing
+---
+
+Thank you for your interest in contributing to codemod-kit
+
+codemod-kit is a 100% community-driven project.So, from the bottom of our hearts, thank you.
+
+## Getting Started
+
+If you're new to open source, you may also find the [How to Contribute to Open Source](https://opensource.guide/how-to-contribute) guide from https://opensource.guide useful.
+
+## Next Steps
+Contributions are generally made through the following process:
+
+1. [Finding or opening an issue](./issue.mdx): In the issue tab, finding or creating an issue to work on.
+2. [Setting up a local environment](./development.mdx): Learning how to set up the local environment to start development.
+3. [Making a PR](./pr.mdx): Sending in your changes to resolve an accepted issue.

website/docs/contributing/issue.mdx

@@ -0,0 +1,19 @@
+---
+sidebar_position: 1
+---
+
+## Issue Claiming
+
+Anything is fine, be it a bug, documentation request, feature suggestion, etc. Please post it in the issue.
+
+Please select an issue template, fill in the required fields, and submit. We will review and edit/comment on your content as quickly as possible.
+
+> Please also post questions about features as issues so that we can document and work on preventing such questions from occurring in the future.
+
+## Finding Issues
+
+For issues with the help wanted label, you can create a pr after working on them without asking permission. 
+
+However, since you may be doing duplicate work, it is better to prevent this by specifying this in the issue or linking a pr in the wip state.
+
+> If this is your first contribution, look for issues labeled good first issue

website/docs/contributing/pr.mdx

@@ -0,0 +1,7 @@
+---
+sidebar_position: 3
+---
+
+If you have worked on an issue, please create a pr. However, please do not create a pr that is not linked to an issue.
+
+If you have no response for 1 month or have any questions, please ping the maintainer at any time.