Merge branch 'main' into kf/refactor-installation-page

Author: kevinfiol

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,5 +1,8 @@
 <!--- Provide a general summary of your changes in the Title above -->
 
+<!-- If you have questions about it, feel free to ask. We don't bite, I promise. -->
+- [ ] I have read https://mithril.js.org/contributing.html
+
 ## Description
 <!--- Describe your changes in detail -->
 
@@ -11,21 +14,3 @@
 <!--- Please describe in detail how you tested your changes. -->
 <!--- Include details of your testing environment, and the tests you ran to -->
 <!--- see how your change affects other areas of the code, etc. -->
-
-## Types of changes
-<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
-- [ ] Bug fix (non-breaking change which fixes an issue)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to change)
-- [ ] Documentation change
-
-## Checklist:
-<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
-<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
-- [ ] My code follows the code style of this project.
-- [ ] My change requires a change to the documentation.
-- [ ] I have updated the documentation accordingly.
-- [ ] I have read the **CONTRIBUTING** document.
-- [ ] I have added tests to cover my changes.
-- [ ] All new and existing tests passed.
-- [ ] I have updated `docs/changelog.md`

docs/contributing.md

@@ -20,9 +20,14 @@ Contribution guide for Mithril.js
 
 ## How do I go about contributing ideas or new features?
 
-Create an [issue thread on GitHub](https://github.com/MithrilJS/mithril.js/issues/new) to suggest your idea so the community can discuss it.
+Go to our [discussions forum](https://github.com/MithrilJS/mithril.js/discussions) to suggest your idea so the community can discuss it.
 
-If the consensus is that it's a good idea, the fastest way to get it into a release is to send a pull request. Without a PR, the time to implement the feature will depend on the bandwidth of the development team and its list of priorities.
+If the consensus is that it's a good idea, the fastest way to get it published is to send a pull request. Without a PR, the time to implement the feature will depend on the bandwidth of the development team and its list of priorities.
+
+Here's where you would submit that pull request:
+
+- Mithril.js core: https://github.com/MithrilJS/mithri.js
+- Mithril.js documentation: https://github.com/MithrilJS/docs