Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Right. And this would be so easy to fix too.

  a) crawl your own documentation and find dead links.
  b) monitor 404 errors and track down the source (via referer headers, etc.).
  c) ask the user on the 404 page what they were hoping for or provide a search menu, record it, and have someone manually review.
  d) add a redirect management engine, so you can redirect links that you can't/won't ever fix.


I'll write a crawler and get this done for CGA docs (Compute, Graphics and AI).

Thanks for the tip.


Sarcastic? I can't tell.

I didn't mean to imply it was trivial, but the concept of crawling your own documentation is quite sound and should just be part of good document maintenance.

There are some plenty good crawlers already. I'm guessing one of them has a 404 report that could hopefully be used to find dead links.


not sarcastic, and yes I'll probably use a crawler library :)


Cheers! Good luck to you.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: