Prune bot: Prune: help-center

[mintlify]

Rotation

• ISO week: 38 (date +%V = 38)
• Alphabetically-sorted top-level directories containing English MDX (excluding es/, fr/, zh/, snippets/, and empty dirs): agent, ai, analytics, api-playground, api, assistant, automations, cli, components, create, customize, dashboard, deploy, editor, guides, help-center, integrations, migration-services, migration, optimize, organize, reference, search-index (count 23)
• Index: 38 mod 23 = 15 → help-center/ (0-indexed).

Summary

Change	Type	Pages affected	Confidence	Rationale (1 line)
Group help-center entries by topic in docs.json	Reorder (nav only)	docs.json (help-center group order)	High	Pages were listed in creation order; grouping into audience clusters makes the (hidden, search-only) tab easier to maintain.

No pages were deleted, merged, moved, or renamed. No redirects were needed. No prose was modified.

Full rationale

After reading all 19 pages in help-center/ and cross-checking against their upstream canonical pages (deploy/*, migration/*, api-playground/*, ai/*, organize/*, dashboard/*, analytics/*), I did not find a candidate that meets the "confident, information-preserving" bar for a diff this week.

Help-center is a hidden: true, searchable: true tab (see docs.json L471-473). By design, its pages are search catchers — narrowly-scoped landing pages for exact error strings and specific "how do I…" phrases that a reader would type into search. Most are 1-3 KB and delegate to a canonical page in another directory. That is the shape they are supposed to have, not sprawl. A canonical page has no reason to embed the exact error string ("Failed to fetch OpenAPI file for anchor or tab", "Domain is already claimed by another organization", etc.); the help-center page exists to catch that string.

The single change is a reorder of the pages list inside the Help center group in docs.json so that pages sit next to their siblings: deployment/org identity → git/deployment source → auth → build errors → editor → search/AI/MCP → analytics → migration. The tab is hidden from readers, so the reorder is a maintainer-facing cleanup only, but it is fully within the automation's REORDER scope and low-risk.

Also worth reviewing (not touched)

Ranked by how confident I was that a prune would preserve information. Left as suggestions because in each case a merge would either lose search-catcher value or require adding new content to the merge target (against automation rules).

1. help-center/migrate-from-confluence.mdx — Very thin (1.7 KB). Four numbered steps duplicate migration/manual.mdx. Unique content: link to Atlassian's export docs (external, easy to search for) and a short pointer to the Mintlify agent's Confluence integration (arguably scope creep on a migration page). Candidate for deletion + redirect to /migration/manual, but the page was just added in Fill gaps from assistant conversations: ZIP and Confluence migration #7254 (2026-09-11) explicitly as a search catcher for "confluence to mintlify"; pruning a week-old intentional addition looks like automation churn, so I left it. If a human agrees the search-catcher value is low, deletion is safe with a redirect.
2. help-center/migrate-docs-from-a-zip-export.mdx — Also from Fill gaps from assistant conversations: ZIP and Confluence migration #7254. More defensible than the Confluence one because it disambiguates Document360 vs. ReadMe vs. "other" ZIPs and mentions the reverse direction (mint export). Real disambiguation value; probably keep.
3. help-center/preview-deployment-not-created-for-fork-branch.mdx — 1.4 KB, the smallest page. Content is fully covered by deploy/preview-deployments#fork-pull-requests and api/preview/trigger.mdx (which already notes fork branches aren't supported). Unique framing: bundles the automatic-PR-preview and API-trigger cases into one FAQ. If merged, redirect to /deploy/preview-deployments#fork-pull-requests.
4. help-center/agent-blocked-by-git-provider-ip-allow-list.mdx (Update from code changes: agent IP allow list error fix #7276) vs. help-center/ip-addresses-for-git-provider-allowlists.mdx (Update from support feedback: clarify Git integration network requirements #7172) — Both added inside this audit window and cross-link cleanly (the IP-addresses page has an "Agent and automation runs" section that points at the agent-blocked page). They overlap on the "agent traffic uses dynamic IPs; email support to route it through 54.242.90.151" fact. Kept separate because each targets a distinct search intent (specific error message vs. "what IP does Mintlify use"). If deemed too close, merging the agent-blocked page into an "Agent and automation runs" subsection of the IP-addresses page is straightforward with a redirect.

Unrelated issues noticed (not fixed)

Per the automation rules, I did not fix these — flagging for a follow-up pass:

• help-center/migrate-from-confluence.mdx frontmatter is missing a keywords array while every other page in the directory has one. Ironic for a page whose only reason to exist is search discovery.

Sanity checks

• mint validate passes.
• mint broken-links passes.
• No page slugs changed, so redirects.json and the es.json / fr.json / zh.json mirrors did not need updates.

---

Note

Low Risk
Navigation-only reorder in docs config files; no content, redirects, or runtime behavior changes.

Overview
Reorders the Help center pages list in docs.json so entries are grouped by topic (deployment/org identity, git and deployments, auth, build errors, editor, search/AI/MCP, analytics, migration) instead of creation order. The same order is applied to the mirrored lists in es.json, fr.json, and zh.json.

No help-center pages were added, removed, or renamed; only navigation config changed. The tab stays hidden and searchable, so this is maintainer-facing ordering with no reader-facing URL or content impact.

^{Reviewed by Cursor Bugbot for commit b6dab01. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

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

Project	Status	Preview	Updated
mintlify	🟢 Ready	View Preview	Sep 17, 2026, 2:17 PM