Fix | Continuous Integration to Check for Broken Links in Documentation

[exequielrafaela]

Describe the Feature:

Implement a GitHub Action that automatically checks for broken links (404) in the documentation at each pull request (PR). This will help ensure all documentation remains accessible and reliable. Additionally, conduct a comprehensive review and repair of existing broken links across the entire documentation site.

Expected Behavior:

1. A GitHub Action runs with each PR, scanning for broken links in the documentation changes.
2. Any detected broken links are reported back to the contributor, preventing merge until they are fixed.
3. An initial sweep through the current documentation identifies and fixes any existing broken links.

Use Case:

This feature ensures the documentation remains a trusted resource with functional navigation, providing a better user experience and reducing maintenance overhead. It is particularly important for maintaining the quality and reliability of documentation as the project scales.

Describe Ideal Solution:

• Implement a GitHub Action using a tool like lychee or markdown-link-check to automatically check for broken links in all markdown files within the repository whenever a new PR is created.
• Fix all currently identified broken links as part of the initial implementation phase.
• Integrate this check into the CI pipeline to maintain ongoing quality control without manual oversight.

Alternatives Considered:

• Periodic manual checks for broken links—less efficient and scalable.
• External services for link checking—could introduce dependencies and costs.