Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dead Links #77

Open
Minimal-C opened this issue Dec 17, 2021 · 1 comment
Open

Dead Links #77

Minimal-C opened this issue Dec 17, 2021 · 1 comment

Comments

@Minimal-C
Copy link
Contributor

Hi, I noticed some dead links in some of the build instruction pages. So I did some digging and compiled a list of all dead links using this https://github.com/tcort/markdown-link-check tool.

Full disclosure: I work for Andor Technology but am contributing this issue on my own time.

I have attached the output for running this tool on this repository for *.md files:
output.txt

The output contains mostly false positives for intra-document links but as far as I can see most of the external http failures are valid, so that's what I would draw most focus to.
A general estimate would be that ~966 http/https links are dead.

I understand that there are alot of pages specific to manufacturer websites and user pages so it might be difficult to cleanup all the links.

@marktsuchida
Copy link
Member

Thanks for this. I also generated a list when we switched to the GitHub Pages-based site, and if I remember correctly I eliminated all broken internal links. (At the time I used a different tool that scans the generated HTML rather than the Markdown, but I had to disable checks for external links for it to finish within a reasonable time.)

The false-positive internal links probably result from the fact that we generate redirect pages based on the page header entires; a tool scanning the Markdown will not notice this.

As for the external links, I get 448 after filtering and uniquing.
cat output.txt |grep -o '^ \[✖\] http[^ ]* ' |sort -u |less

I don't think it's going to be easy to act on these other than by manually reviewing each, except for the one or two cases where there are a large number of similar links -- but it was useful to confirm this.

Categories that may be actionable:

  • some of the http URLs might work if changed to https (and others should be updated to https even if they work with http)
  • links to micro-manager.org, valelab.ucsf.edu, and valelab4.ucsf.edu (although some are obsolete and/or lost)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants