broken relative links

[evanwill]

There are quite a few broken internal relative links in the docs, I was thinking of quickly fixing some, but not exactly sure your practice and the redirects going on.

There are a couple different issues, but many of them are incorrect relative paths. For example list of installation instructions the markdown has links [Find archiveweb.page in the Chrome store](installation/chromestore), where they don't need that extra level, should be [Find archiveweb.page in the Chrome store](chromestore) since they are in the same directory. While further below, the link [troubleshooting page](troubleshooting) won't work because that page is in a different directory.
To avoid the confusion of relative paths in Jekyll, I usually use either the Liquid link tag or relative_url. For example, a link to Troubleshooting could be [troubleshooting page]({% link _en/troubleshooting.md %}) or [troubleshooting page]({{ '/en/troubleshooting/' | relative_url }}).

If I create a PR would you like to use plain markdown relative links, or add Liquid?

Thank you for your work on this project!

[amandavisconti]

I think because of the internal link directory reasons above—I just noticed that on your https://archiveweb.page/en/usage/ documentation page under "troubleshooting",

1. the link to "Check out our troubleshooting page" (https://archiveweb.page/en/usage/troubleshooting) goes to a 404,
2. as does the "contact us" (https://archiveweb.page/en/usage/contact) link in the same paragraph

(Am finishing up the zine from yall's great Fall 2024 DIY Web Archiving workshop.) Thanks for developing and documenting this important tool @ikreymer @tw4l !