Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
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
2 participants
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
Consolidates namespace topology guidance into the namespace best-practices page and removes duplicate best-practices content from the Temporal Cloud namespace reference page.
Why
Customers currently have to reconcile overlapping and partially inconsistent guidance across namespace docs. This change makes
/best-practices/managing-namespacethe canonical decision page while keeping/cloud/namespacesfocused on Cloud mechanics.Changes
/cloud/namespaces#best-practicesinto a redirect-style sectionValidation
yarn build┆Attachments: EDU-6116 Consolidate namespace best practices guidance