Repository navigation
docs: remove orphan pages and redirect them (DOC-93) - #731
Merged
Merged
Conversation
… DOC-101, DOC-106, DOC-108, DOC-110, DOC-119, DOC-135, DOC-152) These pages aren't in the navigation and are largely invented or outdated. Each deleted path redirects to the closest current page; inbound links updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
hlenke
marked this pull request as ready for review
October 27, 2026 21:36
hlenke
enabled auto-merge
October 27, 2026 21:36
This branch was successfully deployed
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
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.
Removes 15 pages that aren't in the docs navigation and are mostly invented or out of date, and redirects each one to the closest current page.
Linear: DOC-93, DOC-99, DOC-100, DOC-101, DOC-106, DOC-108, DOC-110, DOC-119, DOC-135, DOC-152
Why
The audit found these pages unreachable from the nav, full of generic or wrong content, or both. One example: the alert best practices page suggests a 67% threshold that the API rejects. Patching them would mean rewriting pages nobody can find. Hannes decided to delete them and redirect instead.
Deleted, and where each now redirects
detect/synthetic-monitoring/api-checks/examples(DOC-93)/detect/synthetic-monitoring/api-checks/setup-and-teardowndetect/synthetic-monitoring/browser-checks/best-practices(DOC-99)/detect/synthetic-monitoring/browser-checks/overviewdetect/uptime-monitoring/heartbeat-monitors/iac-configuration(DOC-100)/constructs/heartbeat-monitordetect/uptime-monitoring/heartbeat-monitors/cli-configuration(DOC-100 cluster)/constructs/heartbeat-monitordetect/uptime-monitoring/heartbeat-monitors/cron-configuration(DOC-100 cluster)/detect/uptime-monitoring/heartbeat-monitors/examplesdetect/uptime-monitoring/heartbeat-monitors/ci-cd-configuration(DOC-100 cluster)/detect/uptime-monitoring/heartbeat-monitors/examplesdetect/uptime-monitoring/heartbeat-monitors/other(DOC-100 cluster)/detect/uptime-monitoring/heartbeat-monitors/examplesdetect/synthetic-monitoring/api-checks/best-practices(DOC-101)/detect/synthetic-monitoring/api-checks/overviewdetect/uptime-monitoring/alerting(DOC-106)/communicate/alerts/overviewdetect/uptime-monitoring/locations(DOC-108)/concepts/locationsdetect/uptime-monitoring/scheduling(DOC-110)/concepts/schedulingdetect/uptime-monitoring/cli-configuration(same orphan group as DOC-106/108/110)/detect/uptime-monitoring/overviewdetect/uptime-monitoring/tcp-monitors/use-cases(DOC-119)/detect/uptime-monitoring/tcp-monitors/overviewconcepts/monitors(DOC-135)/detect/uptime-monitoring/overviewcommunicate/alerts/best-practices(DOC-152)/communicate/alerts/overviewInbound links updated
api-checks/setup-and-teardown.mdx: both "setup script examples" links now point to the setup scripts guide.integrations/ci-cd/vercel/deployment-protection.mdx: the absolute link pointed to an anchor that no longer exists on the examples page. It now links to the API check setup and teardown page.Every page was checked against
docs.json: none is in the navigation, and no nav page links to any of them.Overlap with other PRs
heartbeat-monitors/other.mdx, which this PR deletes. If this merges, docs: fix heartbeat-monitors/other (DOC-163) #667 can be closed.communicate/alerts/best-practices.mdxand the uptimealerting,locationsandschedulingpages, so whichever merges second will conflict.vale and
npm run check:linksare clean.🤖 Generated with Claude Code