Skip to content

Update from code changes: dashboard settings label renames - #7283

Open
mintlify[bot] wants to merge 3 commits into
mainfrom
mintlify/2044c46b
Open

Update from code changes: dashboard settings label renames#7283
mintlify[bot] wants to merge 3 commits into
mainfrom
mintlify/2044c46b

Conversation

@mintlify

@mintlify mintlify Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Summary

The dashboard search and general settings pages were rebuilt with renamed labels ("Maximum search results" → "Results", "Project name" → "Deployment name"), so the docs references to the old names are updated.

Changes

  • Updated /optimize/search to point users to the "Results" section when setting Results per query, and updated image alt text to reference the control.
  • Updated the "Can I rename my deployment or organization?" help center page to say "deployment name" instead of "project name", matching the new Deployment name field label.
  • Mirrored both fixes in the Spanish, French, and Chinese translations.

Context

Both settings pages moved to the new dashboard design system. Save behavior, validation rules, and defaults are unchanged, so no other docs updates are needed. The dashboard screenshots on the search page predate the redesign and may be worth retaking.

Unverified claim left as-is: the new General settings field description says the deployment name is "Shown in the topbar of your docs", while the help center page says it appears in the dashboard topbar (and that the docs site name comes from docs.json). Could not confirm which surface actually renders the deployment name, so the existing docs claim was kept.

https://github.com/mintlify/mint/pull/10814
https://github.com/mintlify/mint/pull/10816

Update history

  • Documented mintlify/mint#10814: updated /optimize/search (en/es/fr/zh) for the renamed "Results" section.
  • Documented mintlify/mint#10816: updated the rename help center page (en/es/fr/zh) to use "deployment name" terminology matching the rebuilt General settings page.

Note

Low Risk
Copy and localization changes only; no application code, auth, or data handling.

Overview
Documentation-only updates across English, Spanish, French, and Chinese so wording matches the current dashboard UI and product terminology.

Search settings: In optimize/search (and locales), instructions now point users to the "Results" section instead of "Maximum search results" when setting Results per query, and screenshot alt text describes the Results per query control rather than the old section label.

Deployment rename help: In help-center/can-i-rename-my-deployment-or-organization (and locales), copy replaces project name with deployment name, retitles the rename section (e.g. Rename your deployment), and updates localized anchor ids from rename-your-deployments-project-name to rename-your-deployment where applicable.

Reviewed by Cursor Bugbot for commit cb2481c. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify

mintlify Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
mintlify 🟢 Ready View Preview Sep 6, 2026, 9:49 AM

@mintlify

mintlify Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
tomee 🟡 Building Sep 6, 2026, 9:48 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

@mintlify mintlify Bot changed the title Update from code changes: rename search settings section reference Update from code changes: dashboard settings label renames Sep 6, 2026
@mintlify

mintlify Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor Author

Update from code changes updated this PR.

Verified best-practices checks; no changes needed

Source PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants