Updated contributing guidelines

Author: joshwilsonvu

.github/ISSUE_TEMPLATE/bug_report.md

@@ -7,28 +7,27 @@ assignees: joshwilsonvu
 ---
 
 **Describe the bug**
-A clear and concise description of what the bug is.
+<!-- A clear and concise description of what the bug is. -->
 
 **To Reproduce**
-Steps to reproduce the behavior:
-
-1. Go to '...'
-2. Click on '....'
-3. Scroll down to '....'
-4. See error
+<!-- Example code that produces the unexpected lint result, or steps to reproduce the behavior. -->
+<!-- Include your ESLint config if you're not using only `plugin:solid/recommended` or `plugin:solid/typescript`. -->
 
 **Expected behavior**
-A clear and concise description of what you expected to happen.
+<!-- A clear and concise description of what you expected to happen. -->
 
 **Screenshots**
-If applicable, add screenshots to help explain your problem.
+<!-- If applicable, add screenshots to help explain your problem. -->
 
-**Desktop (please complete the following information):**
+**Environment (please complete the following information):**
 
 - OS: [e.g. Mac OS 11, Windows 10]
 - Node version (`node --version`):
 - `eslint-plugin-solid` version (`npm list eslint-plugin-solid`/`yarn why eslint-plugin-solid`):
 - `eslint` version (`npm list eslint`/`yarn why eslint`):
 
 **Additional context**
-Add any other context about the problem here.
+<!-- Add any other context about the problem here. -->
+
+<!-- Never expected, always appreciated! -->
+- [ ] I would be willing to contribute a PR to fix this issue

.github/ISSUE_TEMPLATE/feature_request.md

@@ -7,13 +7,16 @@ assignees: joshwilsonvu
 ---
 
 **Describe the need**
-What kind of problem do you want solved?
+<!-- What kind of problem do you want solved? -->
 
 **Suggested Solution**
-What would you like to see added to this plugin?
+<!-- What would you like to see added to this plugin? -->
 
 **Possible Alternatives**
-Is there a way to work around the problem? If so, give a few details.
+<!-- Is there a way to work around the problem? If so, give a few details. -->
 
 **Additional context**
-Add any other context about the idea here.
+<!-- Add any other context about the idea here. -->
+
+<!-- Never expected, always appreciated! -->
+- [ ] I would be willing to contribute a PR to implement this feature

.github/ISSUE_TEMPLATE/question.md

@@ -7,4 +7,5 @@ assignees: joshwilsonvu
 ---
 
 **Your Question**
-A question or comment about this plugin.
+
+<!-- A question or comment about this plugin. -->

CONTRIBUTING.md

@@ -0,0 +1,48 @@
+# Contributing to `eslint-plugin-solid`
+
+Thanks for your interest in improving this project! We welcome questions, bug reports, and feature
+requests. Please file an issue before submitting a PR, and fill out applicable details in the chosen
+issue template.
+
+> Please see our [Code of Conduct](./CODE_OF_CONDUCT.md) before contributing.
+
+## Development
+
+This project uses `pnpm` for package management. Run `pnpm i` to install dependencies after cloning
+the repo.
+
+To type-check and build the code, run `pnpm build`. This will also regenerate the docs from source
+code descriptions and test cases, using `scripts/docs.ts`.
+
+`pnpm lint` runs ESLint on the repo (so meta!).
+
+Testing is _extremely_ important to maintaining the quality of this project, so we require
+comprehensive tests for every rule, and we check against example code provided in the docs. To run
+tests for individual rules as well as integration/e2e tests, run `pnpm test`. To run tests for a
+specific rule like `reactivity`, run `pnpm test reactivity` or `pnpm test reactivity --watch`.
+Before releasing new versions, we run tests against various ESLint parsers with `pnpm test:all`.
+
+### Adding a new rule
+
+For each rule, there's a few things to do for it to be ready for release. Let's say you have
+received approval to add a rule named `solid/some-name` in an issue:
+
+1. Create `src/rules/some-name.ts`. Add the necessary imports and a default export of the form `{
+   meta: { ... }, create() { ... } }`.
+   [`solid/no-react-specific-props`](./src/rules/no-react-specific-props.ts) is a good, brief
+   example of what's necessary.
+2. Create `test/rules/some-name.test.ts`. Add `valid` and `invalid` test cases, using other files
+   for inspiration. Be sure to `export const cases` so `scripts/docs.ts` can pick up the test cases.
+3. Create `docs/rules/some-name.md`. You can copy the content of
+   `docs/rules/no-react-specific-props.md` directly, as all of its content is auto-generated. Run
+   `pnpm build` and then verify that the content has been updated to reflect the new rule.
+4. When good tests are written and passing, open `src/index.ts` and import your new rule. Add it to
+   `allRules` and the `recommended` and `typescript` configs as appropriate.
+5. Submit your PR and await feedback. When any necessary changes have been made, it will be merged.
+   Congratulations!
+
+## Publishing
+
+Publishing is currently done manually by @joshwilsonvu. When publishing a new version of
+`eslint-plugin-solid`, we also publish a corresponding version of `eslint-plugin-standalone`, which
+is a package primarily intended to support linting on https://playground.solidjs.com.