You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Documents that a multi-repository deployment can now have one source served at a root URL path (/), with no path prefix, and explains how path conflicts between sources are handled.
Changes
deploy/multi-repo.mdx: added guidance on using an empty / root URL path for one source, updated the URL path uniqueness warning, and added a new "Avoid path conflicts across sources" subsection.
Mirrored the same updates in the Spanish, French, and Simplified Chinese translations (es/, fr/, zh/deploy/multi-repo.mdx).
Context
Multi-repository deployments previously required every source to have a non-empty, non-root URL path. One source can now be mounted at the site root while other sources continue to serve under their configured URL paths, which is useful when one repository holds the main docs and others contribute sections like an API reference or SDK guides.
Note
Low Risk
Documentation-only changes with no application code or deployment logic modified.
Overview
Updates multi-repository deployment docs (deploy/multi-repo.mdx and es/, fr/, zh/ mirrors) to describe mounting one source at the site root (/ or empty URL path), with other repos still under their own paths.
The requirements warning now states that only one source may use the root path. The Set the URL path step explains how to configure that. A new subsection Avoid path conflicts across sources covers duplicate final URLs (more specific path wins, deployment conflict warning) and how to avoid overlaps between root-source filenames and other sources’ URL paths.
Reviewed by Cursor Bugbot for commit 55cab7f. Bugbot is set up for automated code reviews on this repo. Configure here.
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
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.
Summary
Documents that a multi-repository deployment can now have one source served at a root URL path (
/), with no path prefix, and explains how path conflicts between sources are handled.Changes
deploy/multi-repo.mdx: added guidance on using an empty / root URL path for one source, updated the URL path uniqueness warning, and added a new "Avoid path conflicts across sources" subsection.es/,fr/,zh/deploy/multi-repo.mdx).Context
Multi-repository deployments previously required every source to have a non-empty, non-root URL path. One source can now be mounted at the site root while other sources continue to serve under their configured URL paths, which is useful when one repository holds the main docs and others contribute sections like an API reference or SDK guides.
Note
Low Risk
Documentation-only changes with no application code or deployment logic modified.
Overview
Updates multi-repository deployment docs (
deploy/multi-repo.mdxandes/,fr/,zh/mirrors) to describe mounting one source at the site root (/or empty URL path), with other repos still under their own paths.The requirements warning now states that only one source may use the root path. The Set the URL path step explains how to configure that. A new subsection Avoid path conflicts across sources covers duplicate final URLs (more specific path wins, deployment conflict warning) and how to avoid overlaps between root-source filenames and other sources’ URL paths.
Reviewed by Cursor Bugbot for commit 55cab7f. Bugbot is set up for automated code reviews on this repo. Configure here.