docs: convert in-site absolute links to root-relative#860
Merged
Conversation
Convert internal doc links from https://docs.sparkpost.com/docs/... to /docs/... (root-relative) across 65 files. This enables client-side routing via next/link, keeps links correct on preview/staging deploys, and matches the relative-link convention already used elsewhere in the content. External sparkpost.com links (developers/app/www) are left absolute.
✅ Deploy Preview for support-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
/docs/product.url is a merge-field placeholder inside a fenced code example, not a real navigational link. Keep it as-is to scope this PR to genuine in-site links.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 511eca8. Configure here.
viniciusgiles
approved these changes
Jul 14, 2026
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.

Summary
Follow-up to #858. That PR migrated in-site documentation links to the
docs.sparkpost.comhost but kept them as absolute URLs. These links point right back at this same site, so this PR converts them to root-relative paths:https://docs.sparkpost.com/docs/...→/docs/...Why relative is better for in-site links:
components/markdown/link.tsx) wraps links innext/link. Root-relative paths get fast client-side navigation; absolutehttps://URLs force a full page reload.signals/,user-guide/).Scope
content/docs/.https://docs.sparkpost.com/docs/...links were rewritten. External SparkPost links are left absolute:developers.sparkpost.com/api/...(separate API reference site)app.sparkpost.com/...(the app)www.sparkpost.com/...(marketing/blog/pricing)[here](/docs/...)markdown link so it stays clickable.Test plan
sparkpost.comlinks are unchangedNote
Low Risk
Documentation-only link target changes with no application or API logic affected; risk is limited to broken internal links if any path was mistyped.
Overview
Follow-up to the docs host migration: this PR rewrites in-site markdown links from
https://docs.sparkpost.com/docs/...to/docs/...across 65 files undercontent/docs/.External SparkPost URLs (
developers.sparkpost.com,app.sparkpost.com,www.sparkpost.com) are unchanged. One bare suppression-list URL was turned into a proper[here](/docs/...)link.The goal is client-side navigation via
next/link, correct behavior on preview/staging hosts, and alignment with existing root-relative link style in the content.Reviewed by Cursor Bugbot for commit 511eca8. Bugbot is set up for automated code reviews on this repo. Configure here.