DOC: Update outdated getting_started links in whatsnew files #63253
+12
−12
Conversation
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
1 participant
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.
This PR updates several outdated hyperlinks in the documentation that still referenced the old getting_started/install.html page. The Pandas documentation has since reorganized the Getting Started section, and the correct page is now located at getting_started/installation.html.
Summary of changes
Updated all occurrences of getting_started/install.html in the whatsnew/ documentation files to point to getting_started/installation.html.
Corrected the corresponding redirect entry in doc/redirects.csv so that older references route to the correct modern page.
Verified that the remaining occurrences of “getting_started” in other files (CSS references, image paths, and section anchors) were not hyperlinks and therefore did not require modification.
Why this change is needed
Several parts of the documentation contained hard-coded links to pages that no longer exist due to restructuring of the Getting Started section. These outdated URLs:
caused broken links on the live documentation website,
produced unnecessary Sphinx warnings during builds,
made navigation more difficult for new users.
Updating these links ensures users are directed to the correct installation guide and maintains the integrity of the documentation.
Validation
All affected files were updated manually and verified through a filesystem search. Only actual hyperlinks were modified; non-link references such as CSS files, images, and internal anchors were left unchanged.