docs: Fix broken framework links in Cloud documentation - #791
Merged
Conversation
SandPod
reviewed
Sep 8, 2026
SandPod
left a comment
SandPod
left a comment
Contributor
There was a problem hiding this comment.
Great! Can you apply these to all older versions of the documentation where this applies as well?
Contributor
Author
|
The Cloud docs are a single unversioned instance, so these four pages have no older copies to update. I checked all 19 versioned framework snapshots too, and none contains a On older-version readers: an unversioned Cloud page can't know which Serverpod version someone is on, so these links resolve to the current stable framework docs for everyone. That's the same behavior as every other cloud-to-framework link we have. |
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
2 participants
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.
Eight links from four Cloud pages pointed at framework paths that only exist in the 4.0 prerelease. Readers on the released version hit 404s while following the deploy, logging, caching, and web-hosting paths.
They were all written as absolute
https://docs.serverpod.dev/...URLs. Docusaurus treats those as external and skips them, so the broken-link check never saw them. Each one now points at the equivalent page in the served version, written as a root-relative path like the rest of our cloud-to-framework links, so the build checks it from here on.