chore: update contribution guidelines and templates to direct users to the LangChain Forum (#32050)

docs/docs/contributing/index.mdx

@@ -27,15 +27,15 @@ More coming soon! We are working on tutorials to help you make your first contri
 
 ## Community
 
-### 💭 GitHub Discussions
+### 💭 Forum
 
-We have a [discussions](https://github.com/langchain-ai/langchain/discussions) page where users can ask usage questions, discuss design decisions, and propose new features.
+We have a [LangChain Forum](https://forum.langchain.com/) where users can ask usage questions, discuss design decisions, and propose new features.
 
 If you are able to help answer questions, please do so! This will allow the maintainers to spend more time focused on development and bug fixing.
 
 ### 🚩 GitHub Issues
 
-Our [issues](https://github.com/langchain-ai/langchain/issues) page is kept up to date with bugs, improvements, and feature requests.
+Our [issues](https://github.com/langchain-ai/langchain/issues) page is kept up to date with bugs, docs improvements, and triaged feature requests that are being worked on.
 
 There is a [taxonomy of labels](https://github.com/langchain-ai/langchain/labels?sort=count-desc)
 to help with sorting and discovery of issues of interest. Please use these to help
@@ -59,7 +59,7 @@ We have a [community slack](https://www.langchain.com/join-community) where you
 ### 🙋 Getting Help
 
 Our goal is to have the simplest developer setup possible. Should you experience any difficulty getting setup, please
-ask in [community slack](https://www.langchain.com/join-community) or open a [discussion on GitHub](https://github.com/langchain-ai/langchain/discussions).
+ask in [community slack](https://www.langchain.com/join-community) or open a [forum post](https://forum.langchain.com/).
 
 In a similar vein, we do enforce certain linting, formatting, and documentation standards in the codebase.
 If you are finding these difficult (or even just annoying) to work with, feel free to ask in [community slack](https://www.langchain.com/join-community)!

docs/docs/contributing/reference/review_process.mdx

@@ -32,7 +32,7 @@ by the submitter.
 
 ## Review Guidelines
 
-1. **PRs that touch /libs/core**:
+1. **PRs that touch `/libs/core`**:
    - PRs that directly impact core code and are likely to affect end users.
    - **Triage Guideline**: most PRs should either go straight to `In Review` or closed.
    - These PRs are given top priority and are reviewed the fastest.
@@ -40,13 +40,13 @@ by the submitter.
    - PRs that don't have unit tests are likely to be closed.
    - Feature requests should first be opened as a GitHub issue and discussed with the LangChain maintainers. Large PRs submitted without prior discussion are likely to be closed.
 
-2. **PRs that touch /libs/langchain**:
+2. **PRs that touch `/libs/langchain`**:
    - High-impact PRs that are closely related to core PRs but slightly lower in priority.
    - **Triage Guideline**: most PRs should either go straight to `In Review` or closed.
    - These are reviewed and closed aggressively, similar to core PRs.
    - New feature requests should be discussed with the core maintainer team beforehand in an issue.
 
-3. **PRs that touch /libs/partners/**:
+3. **PRs that touch `/libs/partners/`**:
    - PRs involving integration packages.
    - **Triage Guideline**: most PRs should either go straight to `In Review` or closed.
    - The review may be conducted by our team or handed off to the partner's development team, depending on the PR's content.
@@ -59,7 +59,7 @@ by the submitter.
    - PRs in the `Needs Support` status for 20 days are marked as “stale” and will be closed after 30 days if no action is taken.
 
 5. **Documentation PRs**:
-   - PRs that touch the documentation content in docs/docs.
+   - PRs that touch the documentation content in `docs/docs`.
    - **Triage Guideline**:
       - PRs that fix typos or small errors in a single file and pass CI should go straight to `In Review`.
       - PRs that make changes that have been discussed and agreed upon in an issue should go straight to `In Review`.
@@ -88,8 +88,3 @@ Our goal is to provide the best possible development experience by focusing on m
 - Is easy: Is intuitive to use and well-documented.
 
 We believe this process reflects our priorities and are open to feedback if you feel it does not.
-
-## Github Discussion
-
-We welcome your feedback on this process. Please feel free to add a comment in 
-[this GitHub Discussion](https://github.com/langchain-ai/langchain/discussions/25920).