Update from support feedback: custom domain lifecycle limitations#6436
Open
mintlify-development[bot] wants to merge 1 commit into
Open
Update from support feedback: custom domain lifecycle limitations#6436mintlify-development[bot] wants to merge 1 commit into
mintlify-development[bot] wants to merge 1 commit into
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Adds a "Limitations and lifecycle" section to the custom domain page covering constraints that support keeps having to explain: the
.mintlify.sitesubdomain is permanent, renaming a project only changes the display name, the default subdomain stays live after a custom domain is added, and Mintlify serves each project from a single primary custom domain (multi-hostname/multi-project routing requires a reverse proxy or multi-repo).Changes
customize/custom-domain.mdx.deploy/deployments.mdx(delete a deployment) as the workaround for changing a.mintlify.sitesubdomain.deploy/reverse-proxy.mdxanddeploy/multi-repo.mdxfor multi-domain and multi-project routing.Support context
Note
Low Risk
Documentation-only changes with no application code, configuration, or security impact.
Overview
Documents recurring support topics on custom domain lifecycle that were missing from the docs.
A new Limitations and lifecycle section on the custom domain page explains that the
<subdomain>.mintlify.siteURL is fixed at creation (renames only change the dashboard display name and can causeDisallowed origin hoston previews until rebuild), that the default subdomain stays reachable alongside a verified custom domain with no built-in redirect (canonical URL for SEO), and that each project has one primary custom domain with pointers to reverse proxy, multi-repo, and/docssubpath for harder routing setups.Delete a deployment now notes that delete-and-recreate is the only way to change the
.mintlify.sitesubdomain, with a link to that section. Reverse proxy and multi-repo pages add short callouts linking back to the same limitations section for multi-hostname and multi-project routing.Reviewed by Cursor Bugbot for commit f728c34. Bugbot is set up for automated code reviews on this repo. Configure here.