docs: rename infrastructure options to single-tenant / multi-tenant#10789
Merged
docs: rename infrastructure options to single-tenant / multi-tenant#10789
Conversation
Renames the customer-facing display text for the infrastructure options to use industry-standard single-tenant / multi-tenant terminology and removes the naming collision with the Shared / Dedicated deployment types. - "Shared infrastructure" -> "Multi-tenant infrastructure" - "Dedicated infrastructure" -> "Single-tenant infrastructure" - "Dedicated infrastructure with CSPS" -> "Single-tenant infrastructure with CSPS" URL anchors (#shared-infrastructure, #dedicated-infrastructure, #dedicated-infrastructure-with-csps), reference link IDs, and product region identifier slugs (aws-us-east-1-shared, etc.) are intentionally left unchanged so external inbound links and product identifiers keep working. Mintlify explicit anchor syntax is used to preserve them under the renamed headings. Also documents the new terminology in .cursor/rules/namings-rule.mdc. Made-with: Cursor
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
|
Claude finished @keydunov's task in 2m 12s —— View job Review: docs rename infrastructure options to single-tenant / multi-tenant
Overall this is a clean, well-scoped terminology rename. The anchor preservation strategy using Mintlify's Missed Renaming — 6 Instances of Old TerminologyI found 6 remaining occurrences of "Dedicated Infrastructure" in customer-facing prose that were not updated. These are across 4 VPC-related files:
The link text inside these bullet points was correctly updated to "single-tenant infrastructure", but the surrounding prose and bold labels were missed. I've left inline suggestions on the 4 lines that are part of the diff. The two intro paragraphs (line 8 of each private-link file) are on unchanged lines — those should also be updated to say "Cube Cloud single-tenant infrastructure". What Looks Good
No Other Issues Found
|
Made-with: Cursor
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| @@ -36,8 +36,8 @@ To request establishing a PrivateLink connection, please share the following inf | |||
| - **Ports**: a list of ports that will be accessed through this connection | |||
| - **DNS Name** (optional): an internal DNS name of the upstream service in case SSL needs to be supported | |||
| - **Dedicated Infrastructure Region:** VPC Peering requires Cube to be hosted in | |||
Contributor
There was a problem hiding this comment.
The bold label still says "Dedicated Infrastructure Region" while the link text inside was updated. Should be consistent:
Suggested change
| - **Dedicated Infrastructure Region:** VPC Peering requires Cube to be hosted in | |
| - **Single-tenant Infrastructure Region:** VPC Peering requires Cube to be hosted in |
| @@ -23,8 +23,8 @@ information is required: | |||
| - **AWS VPC CIDR:** The [CIDR block][wiki-cidr-block] of the VPC that Cube Cloud | |||
| will connect to, for example, `10.0.0.0/16` | |||
| - **Dedicated Infrastructure Region:** VPC Peering requires Cube to be hosted in | |||
Contributor
There was a problem hiding this comment.
Same issue — the bold label still uses the old name:
Suggested change
| - **Dedicated Infrastructure Region:** VPC Peering requires Cube to be hosted in | |
| - **Single-tenant Infrastructure Region:** VPC Peering requires Cube to be hosted in |
| @@ -41,8 +41,8 @@ To request establishing a Private Link connection, please share the following in | |||
| - **Ports**: a list of ports that will be accessed through this connection | |||
| - **DNS Name** (optional): an internal DNS name of the upstream service in case SSL needs to be supported | |||
| - **Dedicated Infrastructure Region:** Private Link requires Cube to be hosted in | |||
Contributor
There was a problem hiding this comment.
Bold label still uses old name:
Suggested change
| - **Dedicated Infrastructure Region:** Private Link requires Cube to be hosted in | |
| - **Single-tenant Infrastructure Region:** Private Link requires Cube to be hosted in |
| @@ -86,8 +86,8 @@ information: | |||
| → **Properties** → **Tenant ID** section of | |||
| [Azure Portal][azure-console]. | |||
| - **Dedicated Infrastructure Region:** VPC Peering requires Cube to be hosted | |||
Contributor
There was a problem hiding this comment.
Bold label still uses old name:
Suggested change
| - **Dedicated Infrastructure Region:** VPC Peering requires Cube to be hosted | |
| - **Single-tenant Infrastructure Region:** VPC Peering requires Cube to be hosted |
Matches the wording already used for Single-tenant infrastructure. Made-with: Cursor
Enterprise is the top tier — there is nothing above it, so the phrase "Enterprise and above plans" is meaningless. Replaces all 32 occurrences across docs-mintlify with "Enterprise plan" (singular), and rewords the single "Enterprise and above product tiers" reference in pricing.mdx. Adds a new "Plan Tier Naming" section to .cursor/rules/namings-rule.mdc to codify the convention so future docs avoid this pattern. Made-with: Cursor
CSPS sits on top of single-tenant infrastructure, so it requires both the Enterprise plan and the Single-tenant infrastructure add-on. Made-with: Cursor
Plan availability is a hard gate, not a "by the way" aside. Switching the callout from <Info> (blue, used heavily for general notes) to <Note> (gray) makes plan-gating info visually distinct and scannable. Converts all 47 plan-availability blocks across 42 files. The script at /tmp/convert_info_to_note.py only swaps <Info> blocks whose inner content starts with "Available", leaving non-plan Info blocks untouched. Also adds a "Plan availability callouts" section to namings-rule.mdc to codify the convention. Made-with: Cursor
Use the user-facing terms directly. The URL examples below already show the literal slugs (shared, byoc, etc.) in context. Made-with: Cursor
… nav Promotes the page to sit right after Deployment types so the deployment- level concepts (types, environments) are grouped together before infrastructure and operational topics. Updates both title and sidebarTitle to "Deployment environments" so the term is unambiguous when referenced out of context. Made-with: Cursor
Groups the infrastructure-related pages together (Infrastructure options followed by VPC and BYOC sub-groups), separating them from the deployment-level operational topics that come before. Made-with: Cursor
- Card hrefs were bare relative paths ("vpc/aws") that Mintlify resolved
to /admin/deployment/vpc/vpc/aws — fixed to absolute paths.
- Combined the two-line plan-availability Info into a single Note
matching the new convention (Enterprise plan + Single-tenant add-on).
- Removed an orphaned heading-without-hash line.
- Updated the legacy /docs/deployment/cloud/... reference link target
to the current /admin/deployment/infrastructure path.
Made-with: Cursor
- Parent VPC index: card description and intro now distinguish AWS/GCP VPCs from Azure VNets. - Azure VNet Peering page: sidebarTitle "VPC Peering" → "VNet Peering", and the inline "VPC Peering" reference in the support-info checklist. - Azure Private Link: replaces a stale "Cube Cloud Dedicated Infrastructure" mention with the new "single-tenant infrastructure" term, matching the rest of the rename. - Renames the support-info bullet "Dedicated Infrastructure Region" to "Single-tenant Infrastructure Region" on both Azure pages. - Fixes AWS sidebarTitle typo "VCP Peering" → "VPC Peering". - Updates 5 stale legacy reference links pointing to /docs/deployment/cloud/infrastructure → /admin/deployment/infrastructure. Made-with: Cursor
Card components in index pages used bare relative paths that included
the parent directory name (e.g., on /admin/sso, href="sso/okta") which
Mintlify resolves relative to the current page, producing broken URLs
like /admin/sso/sso/okta. Switches all 51 affected hrefs to absolute
paths so they resolve correctly.
Files affected:
- admin/connect-to-data/visualization-tools/index.mdx (29 cards)
- admin/monitoring/monitoring-integrations/index.mdx (5)
- admin/deployment/{vpc,byoc,providers}/index.mdx (8)
- admin/sso/{index,microsoft-entra-id/index}.mdx (5)
- docs/integrations/semantic-layer-sync/index.mdx (3)
- reference/orchestration-api/index.mdx (3)
- docs/getting-started/index.mdx (1, plus retargeted to a real page)
Made-with: Cursor
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.
Renames the customer-facing display text for the infrastructure options to use industry-standard single-tenant / multi-tenant terminology and removes the naming collision with the Shared / Dedicated deployment types.
URL anchors (#shared-infrastructure, #dedicated-infrastructure, #dedicated-infrastructure-with-csps), reference link IDs, and product region identifier slugs (aws-us-east-1-shared, etc.) are intentionally left unchanged so external inbound links and product identifiers keep working. Mintlify explicit anchor syntax is used to preserve them under the renamed headings.
Also documents the new terminology in .cursor/rules/namings-rule.mdc.
Made-with: Cursor
Check List