docs(*): update contributing guide.

Author: Ehesp

CONTRIBUTING.md

@@ -1,28 +1,60 @@
-# How to Contribute
+# Contributing
 
-We'd love to accept your patches and contributions to this project. There are
-just a few small guidelines you need to follow.
+It's great to receive contributions from the community! If you'd like to contribute to this project, make sure to review and follow the guidelines below.
 
 ## Contributor License Agreement
 
 Contributions to this project must be accompanied by a Contributor License
 Agreement. You (or your employer) retain the copyright to your contribution;
-this simply gives us permission to use and redistribute your contributions as
-part of the project. Head over to <https://cla.developers.google.com/> to see
+this agreement simply gives us permission to use and redistribute your contributions as
+part of the project. Head over to [https://cla.developers.google.com](https://cla.developers.google.com) to see
 your current agreements on file or to sign a new one.
 
 You generally only need to submit a CLA once, so if you've already submitted one
 (even if it was for a different project), you probably don't need to do it
 again.
 
-## Code reviews
+## Code and copy reviews
 
 All submissions, including submissions by project members, require review. We
 use GitHub pull requests for this purpose. Consult
 [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
 information on using pull requests.
 
-## Community Guidelines
+## Community guidelines
 
 This project follows [Google's Open Source Community
 Guidelines](https://opensource.google.com/conduct/).
+
+## Report an issue
+
+Report all issues through GitHub Issues using the [Report a Bug](https://github.com/firebase/extensions/issues/new?template=bug.md) template.
+
+To help resolve your issue as quickly as possible, read the template and provide all the requested information.
+
+## File a feature request
+
+We welcome all feature requests, whether it's to add new functionality to an existing extension or to offer an [idea for a brand new extension](https://firebase.google.com/support/troubleshooter/report/features/).
+
+Here's how to submit a feature request for an existing extension:
+
+1. File your feature request through GitHub Issues using the [Feature Request template](https://github.com/firebase/extensions/issues/new?template=fr.md).
+
+1. File a new [Firebase support request](https://firebase.google.com/support/troubleshooter/report/features/) via the Firebase website. Make sure to reference your feature request's GitHub Issue in the support ticket.
+
+## Create a pull request
+
+When making pull requests to the repository, make sure to follow these guidelines for both bug fixes and new features:
+
+- Before creating a pull request, file a GitHub Issue so that maintainers and the community can discuss the problem and potential solutions before you spend time on an implementation.
+- In your PR's description, link to any related issues or pull requests to give reviewers the full context of your change.
+- For commit messages, follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format.
+  - For example, if you update documentation for a specific extension, your commit message might be: `docs(extension-name) updated installation documentation`.
+- For your PR to be merged:
+
+  - You must sign the [Google Contributor License Agreement](https://cla.developers.google.com/clas).
+  - All tests must pass.
+
+### Features
+
+Before creating pull requests for new features, first file a GitHub Issue describing the reasoning and motivation for the feature. This gives maintainers and the community the opportunity to provide feedback on your idea before implementing it.