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

Checking and fixing broken links on GAP website #15

Open
olexandr-konovalov opened this issue Feb 27, 2016 · 4 comments
Open

Checking and fixing broken links on GAP website #15

olexandr-konovalov opened this issue Feb 27, 2016 · 4 comments
Labels
gapdays2020-spring Issues and PRs that could be worked on or discussed during GAPDays 2020.

Comments

@olexandr-konovalov
Copy link
Member

This is a snippet of the command to check html links on GAP website with linklint:

linklint -limit 100000 -doc gaphtml -http -host www.gap-system.org -skip /ForumArchive/@ /@

We should run it periodically. In fact, I already have a Jenkins job that does that, but because it reports a number of issues, it is not practical to fail it automatically yet.

@olexandr-konovalov olexandr-konovalov changed the title Checking html links on GAP website Checking and fixing broken links on GAP website Mar 3, 2016
@olexandr-konovalov
Copy link
Member Author

olexandr-konovalov commented Mar 3, 2016

We should certainly try to fix them if the solution is in this repository (IIRC last big cleanup of broken links was a while ago), and report to package authors otherwise. One of the common problems in packages is misssing .css and .js files that are produced by GAPDoc but not included in the archive.

@fingolfin
Copy link
Member

Perhaps we can setup a travis job to run this link checker?

@fingolfin
Copy link
Member

Another interesting link checker: https://github.com/gjtorikian/html-proofer

It also can check external links, but one can also configure it to turn that off. With external link checks, it takes quite some time to run, but no problem for a daily cron job.

I'd love to run these things in Travis, but one thing that makes this problematic is that for example links to package manuals would be broken there. But perhaps we can find a way around that, e.g. by installing the missing manuals in the Travis job?

@ruthhoffmann ruthhoffmann added the gapdays2020-spring Issues and PRs that could be worked on or discussed during GAPDays 2020. label Nov 7, 2019
@fingolfin
Copy link
Member

@schnellecom run a link check for the website relaunch in PR #339 and fixed many broken links.

Perhaps we could use a GitHub action like https://github.com/marketplace/actions/check-links-with-linkcheck or https://github.com/marketplace/actions/link-check-action to check for broken links more systematically?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gapdays2020-spring Issues and PRs that could be worked on or discussed during GAPDays 2020.
Projects
None yet
Development

No branches or pull requests

3 participants