Merged
Conversation
Member
|
I love this! Do you think it's possible to maybe add a check in the pipeline which inspects the markdown files and automatically check if all links are valid? That would be a huge improvement and we won't ever be able to ship broken links! |
…04 links between pages
Collaborator
Author
Great idea! Fixed the state of things to be clean now in this PR and will open a separate issue for that to keep things clean going forward. |
timbastin
approved these changes
Feb 4, 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
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.
Due to relative paths from the old structure, wrong naming of new folders or linking to pages in new articles that don't exist yet, there are a bunch of links in the documentation that lead to 404s which also impacts SEO.
In this PR, paths are being fixed so there are no more dead links inside the documentation, as well as new pages being added where they are needed due articles already linking there.
The creation of all missing pages according to the new structure will be done in a separate PR, as the existence of a lot of empty pages first has to be checked for SEO impact severity. Sooner or later this has to be done though, so the pages that still need to be newly written enter our review-cycle-bot-recommendations.
Also, a standard if everyone uses relative or absolute paths should be discussed going forward.
I would plead for absolute paths for better readability and easier search/replace, as well as target pages probably being less prone to be moved as we settle into the new documentation structure.