landing page #789
Merged
landing page #789
+112
−36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull Request Overview
This PR updates the main documentation landing page to reorganize the structure and content presentation. The changes shift from a framework/platform-based organization to a more user-focused structure that emphasizes open-source frameworks and LangSmith offerings.
- Reorganized the main sections from "Frameworks", "Platforms", "Experimental" to "Open-source frameworks" and "LangSmith offerings"
- Updated card descriptions to be more descriptive and user-focused
- Modified the layout mode from "wide" to "custom" and updated the page description
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/index.mdx | Complete restructure of the landing page with new section organization, updated card content, and layout changes |
| src/docs.json | Removed the logo href redirect to allow the logo to link to the current landing page |
src/index.mdx
Outdated
| mode: "custom" | ||
| --- | ||
|
|
||
| [NEED COPY FOR HERE] |
There was a problem hiding this comment.
There's a placeholder comment that needs to be replaced with actual content. This should contain introductory text for the landing page.
Suggested change
| [NEED COPY FOR HERE] | |
| Welcome to the LangChain documentation hub! Here you'll find resources, guides, and reference materials for building, evaluating, and deploying reliable AI agents and applications using LangChain and LangSmith. Explore our open-source frameworks and platform offerings to accelerate your agent engineering journey. |
Copilot uses AI. Check for mistakes.
src/index.mdx
Outdated
| href="/langsmith/prompt-engineering" | ||
| icon="terminal" | ||
| > | ||
| Iterate on prompts with automatic version contol and collaboration features. |
There was a problem hiding this comment.
Corrected spelling of 'contol' to 'control'.
Suggested change
| Iterate on prompts with automatic version contol and collaboration features. | |
| Iterate on prompts with automatic version control and collaboration features. |
Copilot uses AI. Check for mistakes.
|
Preview ID generated: preview-landin-1759943050-adc3cb2 |
eyurtsev
added a commit
that referenced
this pull request
Oct 8, 2025
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
akosgintl
pushed a commit
to akosgintl/langchain-ai-docs
that referenced
this pull request
Oct 8, 2025
## Overview <!-- Brief description of what documentation is being added/updated --> https://linear.app/langchain/issue/ENT-145/add-us-tld-to-default-entra-id-overrides Adds the .us TLD for Azure Entry overrides, as well as the china and global endpoints ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: N/A - Feature PR: langchain-ai/langchainplus#12762 <!-- For LangChain employees, if applicable: --> - Linear issue: [ENT-145/add-us-tld-to-default-entra-id-overrides](https://linear.app/langchain/issue/ENT-145/add-us-tld-to-default-entra-id-overrides) - Slack thread: https://langchain.slack.com/archives/C08R92KKUJH/p1759433050576189 ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
github-actions
bot
added
python
|
Preview ID generated: preview-landin-1759948704-0733793 |
hntrl
approved these changes
Oct 8, 2025
Co-authored-by: Hunter Lovell <40191806+hntrl@users.noreply.github.com>
src/index.mdx
Outdated
| href="/langsmith/prompt-engineering" | ||
| icon="terminal" | ||
| > | ||
| Iterate on prompts with automatic version contol and collaboration features. |
There was a problem hiding this comment.
Corrected spelling of 'contol' to 'control'.
Suggested change
| Iterate on prompts with automatic version contol and collaboration features. | |
| Iterate on prompts with automatic version control and collaboration features. |
Copilot uses AI. Check for mistakes.
|
Preview ID generated: preview-landin-1759950247-cb3cc3b |
|
Preview ID generated: preview-landin-1759953108-c21f414 |
src/index.mdx
Outdated
| # The agent engineering platform for developers building reliable agents | ||
|
|
||
| # Frameworks | ||
| [NEED COPY FOR HERE] |
There was a problem hiding this comment.
Placeholder text should be replaced with actual content before merging.
Suggested change
| [NEED COPY FOR HERE] | |
| Build, evaluate, and deploy robust AI agents with our open-source frameworks and LangSmith platform. Explore tools and resources to accelerate your agent development journey. |
Copilot uses AI. Check for mistakes.
|
Preview ID generated: preview-landin-1759953209-2b315e2 |
|
Preview ID generated: preview-landin-1759959035-8289a15 |
| sidebarTitle: Home | ||
| description: "The platform for reliable agents" | ||
| mode: "wide" | ||
| title: |
There was a problem hiding this comment.
The title field in the frontmatter is empty. This should contain a descriptive title for the homepage, such as 'LangChain Documentation Home' or 'LangChain Platform'.
Suggested change
| title: | |
| title: LangChain Platform |
Copilot uses AI. Check for mistakes.
src/index.mdx
Outdated
| # The platform for developers building reliable agents | ||
|
|
||
| # Frameworks | ||
| Tools for every step of the agent development lifecycle-- built to unlock powerful AI in production. |
There was a problem hiding this comment.
Replace double dash '--' with proper em dash '—' for better typography.
Suggested change
| Tools for every step of the agent development lifecycle-- built to unlock powerful AI in production. | |
| Tools for every step of the agent development lifecycle— built to unlock powerful AI in production. |
Copilot uses AI. Check for mistakes.
|
Preview ID generated: preview-landin-1760026924-038a5f5 |
lnhsingh
pushed a commit
that referenced
this pull request
Oct 9, 2025
## Overview <!-- Brief description of what documentation is being added/updated --> * include option of updating sharing settings in the UI since we do support this <img width="831" height="376" alt="Screenshot 2025-10-01 at 1 51 45 PM" src="https://github.com/user-attachments/assets/c8bc9982-ddf2-4299-80c4-ba23d774d84a" /> ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: closes ent-133 - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> --------- Co-authored-by: Kathryn May <44557882+katmayb@users.noreply.github.com>
lnhsingh
pushed a commit
that referenced
this pull request
Oct 9, 2025
## Overview <!-- Brief description of what documentation is being added/updated --> fix typo in langchain-v1.mdx ## Type of change **Type:** Fix typo ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
lnhsingh
pushed a commit
that referenced
this pull request
Oct 9, 2025
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
lnhsingh
pushed a commit
that referenced
this pull request
Oct 9, 2025
## Overview Adding an egress section to the lgp hybrid docs that give more color to how this traffic is sent, encrypted, authenticated. Once diagram is updated to be excalidraw, i can add an icon showing this encrypted traffic for egress. ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: INF-900 - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> Tested by running locally: <img width="1465" height="661" alt="Screenshot 2025-10-02 at 1 15 49 PM" src="https://github.com/user-attachments/assets/b2b95617-d34e-44dd-a96c-5f063dbdc32b" />
lnhsingh
pushed a commit
that referenced
this pull request
Oct 9, 2025
## Overview <!-- Brief description of what documentation is being added/updated --> Updating vectorstore docs to confirm multi-tenant and standard tests support on the MongoDBAtlasVectorSearch class ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> Co-authored-by: Mason Daugherty <mason@langchain.dev>
lnhsingh
pushed a commit
that referenced
this pull request
Oct 9, 2025
## Overview <!-- Brief description of what documentation is being added/updated --> * fix broken links * remove incorrect SCIM setup steps (these were for without using OIN, but Okta requires using OIN) * add missing supported features for Okta SCIM ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: part of ent-100 - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
lnhsingh
added a commit
that referenced
this pull request
Oct 9, 2025
## Overview <!-- Brief description of what documentation is being added/updated --> **OpenDataLoader PDF** (`langchain-opendataloader-pdf`) document loader, including installation, initialization, quick start and parameters documentation. ## Type of change **Type:** New documentation page ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> - New file: `docs/src/oss/python/integrations/document_loaders/opendataloader_pdf.mdx` `docs/src/oss/python/integrations/providers/opendataloader_pdf.mdx` - Also appended `OpenDataLoader PDF` to the loader index (`index.mdx`) and `all_providers.mdx` for discoverability。 Co-authored-by: Lauren Hirata Singh <lauren@langchain.dev>
lnhsingh
added a commit
that referenced
this pull request
Oct 9, 2025
…ilt (#754) ## Overview fixed typos. Corrected `langgraph.prebuilts` → `langgraph.prebuilt` and `create_agent` → `create_react_agent` ## Type of change **Type:** Fix typo ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> Co-authored-by: Lauren Hirata Singh <lauren@langchain.dev>
lnhsingh
pushed a commit
that referenced
this pull request
Oct 9, 2025
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> --------- Co-authored-by: Mason Daugherty <mason@langchain.dev>
lnhsingh
pushed a commit
that referenced
this pull request
Oct 9, 2025
## Overview <!-- Brief description of what documentation is being added/updated --> * reference `LangSmithURL` configuration for Okta, as this is required for SCIM * fix location of Okta supported features ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: part of ent-100 - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
|
Preview ID generated: preview-landin-1760039830-4783101 |
github-actions
bot
added
langchain
| LangGraph is very low-level, and focused entirely on agent **orchestration**. Before using LangGraph, we recommend you familiarize yourself with some of the components used to build agents, starting with [models](/oss/langchain/models) and [tools](/oss/langchain/tools). | ||
|
|
||
| If you are just getting started with agents, or want a higher level abstraction, it is recommended that you use LangChain's [agents](/oss/langchain/agents). | ||
| We will commonly use [LangChain](/oss/langchain/overview) components throughout the documentation to integrate models and tools, but you don't need to use LangChain to use LangGraph. If you are just getting start with agents or want a higher level abstraction, we recommend you use LangChain's [agents](/oss/langchain/agents) that provide pre-built architectures for common LLM and tool calling loops. |
There was a problem hiding this comment.
Corrected spelling of 'start' to 'started'.
Suggested change
| We will commonly use [LangChain](/oss/langchain/overview) components throughout the documentation to integrate models and tools, but you don't need to use LangChain to use LangGraph. If you are just getting start with agents or want a higher level abstraction, we recommend you use LangChain's [agents](/oss/langchain/agents) that provide pre-built architectures for common LLM and tool calling loops. | |
| We will commonly use [LangChain](/oss/langchain/overview) components throughout the documentation to integrate models and tools, but you don't need to use LangChain to use LangGraph. If you are just getting started with agents or want a higher level abstraction, we recommend you use LangChain's [agents](/oss/langchain/agents) that provide pre-built architectures for common LLM and tool calling loops. |
Copilot uses AI. Check for mistakes.
|
Preview ID generated: preview-landin-1760041280-2aecdd4 |
|
Preview ID generated: preview-landin-1760041707-85a2448 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Adds a general Home page
Type of change
Type: Fix
Checklist
docs devsrc/docs.jsonif neededAdditional notes