Skip to content

Prevent broken links in dstack docs #1603

Closed as not planned
Closed as not planned

Description

@jvstme

dstack docs often contain broken links that hurt the user experience. To prevent broken links, these measures are suggested:

  • Build docs in strict mode (mkdocs build -s) so that pipelines fail if there are broken links
  • Ensure they do actually fail on broken links (didn't fail here)
  • Build docs in pull request pipelines (without publishing or with publishing to a staging environment) to prevent merging changes that break links
  • In doc files, only use local links and avoid using full self-referencing URLs (https://dstack.ai/docs/...)
  • See if building in strict mode fails when there are broken anchor links. If not, come up with a solution
  • See if there are solutions to check external links when building

Activity

  1. added
    docsImprovements or additions to documentation
    on Aug 21, 2024
  2. github-actions commented on Sep 21, 2024

    @github-actions

    This issue is stale because it has been open for 30 days with no activity.

  3. github-actions commented on Oct 5, 2024

    @github-actions

    This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.

  4. reopened this on Oct 15, 2024
  5. github-actions commented on Nov 16, 2024

    @github-actions

    This issue is stale because it has been open for 30 days with no activity.

  6. self-assigned this
    on Dec 24, 2024
  7. added a commit that references this issue on Dec 24, 2024
  8. added a commit that references this issue on Dec 25, 2024
  9. reopened this on Dec 25, 2024
  10. github-actions commented on Feb 3, 2025

    @github-actions

    This issue is stale because it has been open for 30 days with no activity.

  11. added a commit that references this issue on Feb 9, 2025
  12. github-actions commented on Apr 20, 2025

    @github-actions

    This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.

  13. reopened this on Apr 21, 2025
  14. github-actions commented on May 22, 2025

    @github-actions

    This issue is stale because it has been open for 30 days with no activity.

  15. github-actions commented on Jun 5, 2025

    @github-actions

    This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsImprovements or additions to documentationstaleux

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions