Skip to content

update-hyperlinks: fix broken links in Intro key benefits section#695

Open
santoshkal wants to merge 2 commits into
kserve:mainfrom
santoshkal:update-hyperlink
Open

update-hyperlinks: fix broken links in Intro key benefits section#695
santoshkal wants to merge 2 commits into
kserve:mainfrom
santoshkal:update-hyperlink

Conversation

@santoshkal

Copy link
Copy Markdown

"Fixes #issue-number" or "Add description of the problem this PR solves"

Proposed Changes

This PR fixes three broken hyperlinks in the KServe documentation website that were routing users to non-existent pages and resulting in "Page not found" (404) errors.

Fixed Documentation Pages in Key Benefits section of the Intro page:

  • kvcache-offloading
  • multi-node inference
  • metric-based autoscaling

@netlify

netlify Bot commented Jun 12, 2026

Copy link
Copy Markdown

Deploy Preview for elastic-nobel-0aef7a ready!

Name Link
🔨 Latest commit 07f7a9f
🔍 Latest deploy log https://app.netlify.com/projects/elastic-nobel-0aef7a/deploys/6a3182cf77c6a0000874c507
😎 Deploy Preview https://deploy-preview-695--elastic-nobel-0aef7a.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Signed-off-by: santoshkal <ksantosh@intelops.dev>
Signed-off-by: santoshkal <ksantosh@intelops.dev>

@spolti spolti left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, can you also fix it in the docs so the fix persists for new doc releases?

@santoshkal

santoshkal commented Jun 18, 2026

Copy link
Copy Markdown
Author

Hi, can you also fix it in the docs so the fix persists for new doc releases?

Hi,
I've updated the links in ./docs as well in this commit. My understanding is that future versioned documentation would be generated from these files in ./docs, so this fix should persist in subsequent releases.

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.

2 participants