Implement redirects.

[johnnymatthews]

Work with the infrastructure team to implement the redirects planned out in #503.

[cwaring]

What is the latest status on this, is infra ready with the list we compiled the other day?

[johnnymatthews]

Infra's been given this list (taken from the sheet linked in #503:

https://docs.ipfs.io/ -> /
https://docs.ipfs.io/guides/concepts/ipns/ -> /concepts/ipns/
https://docs.ipfs.io/guides/concepts/dnslink/ -> /concepts/dnslink/
https://docs.ipfs.io/reference/api/cli/ -> /reference/cli/
https://docs.ipfs.io/guides/guides/install/ -> /install/
https://docs.ipfs.io/introduction/usage/ -> /how-to/command-line-quick-start/
https://docs.ipfs.io/reference/api/http/ -> /reference/http/api/
https://docs.ipfs.io/community/ -> /community/
https://docs.ipfs.io/introduction/overview/ -> /concepts/what-is-ipfs/
https://docs.ipfs.io/guides/concepts/cid/ -> /concepts/content-addressing/
https://docs.ipfs.io/guides/concepts/pinning/ -> /concepts/persistence/
https://docs.ipfs.io/introduction/how-ipfs-works/ -> /concepts/how-ipfs-works/
https://docs.ipfs.io/guides/concepts/mfs/ -> /concepts/file-systems/
https://docs.ipfs.io/guides/examples/websites/ -> /how-to/host-single-page-site/
https://docs.ipfs.io/guides/concepts/hashes/ -> /concepts/hashing/
https://docs.ipfs.io/guides/concepts/unixfs/ -> /concepts/file-systems/
https://docs.ipfs.io/guides/guides/addressing/ -> /how-to/address-ipfs-on-web/
https://docs.ipfs.io/guides/concepts/merkle-dag/ -> /concepts/merkle-dag/
https://docs.ipfs.io/guides/concepts/ -> /concepts/merkle-dag/
https://docs.ipfs.io/guides/concepts/dht/ -> /concepts/dht/
https://docs.ipfs.io/reference/js/overview/ -> /reference/js/api/
https://docs.ipfs.io/guides/examples/ -> /how-to/
https://docs.ipfs.io/guides/examples/config/ -> /how-to/configure-node/
https://docs.ipfs.io/introduction/ -> /essentials/
https://docs.ipfs.io/guides/examples/bootstrap/ -> /how-to/modify-bootstrap-list/
https://docs.ipfs.io/guides/examples/blocks/ -> /how-to/work-with-blocks/
https://docs.ipfs.io/guides/examples/git/ -> /how-to/host-git-style-repo/
https://docs.ipfs.io/guides/examples/pinning/ -> /how-to/pin-files/
https://docs.ipfs.io/reference/go/overview/ -> /reference/go/api/
https://docs.ipfs.io/community/irc/ -> /community/irc/
https://docs.ipfs.io/introduction/faq/ -> /concepts/faq/
https://docs.ipfs.io/guides/examples/videos/ -> /how-to/store-play-videos/
https://docs.ipfs.io/guides/examples/api/service/readme/ -> /how-to/make-service/
https://docs.ipfs.io/guides/examples/snapshots/ -> /how-to/take-snapshot/
https://docs.ipfs.io/reference/api/ -> /reference/
https://docs.ipfs.io/community/contribute/how-to-help/ -> /project/contribute/

It's ready to go as soon as the move is done.

[hugomrdias]

@mburns any chance we can deploy these redirect rules to the docs-beta domain ?

[cwaring]

@mburns: just for context these are all 301 redirects so that the bots will update their indexes correctly, thanks!

[mburns]

@hugomrdias we should deploy these redirects to docs-beta for testing before going live, definitely.

Would it make more sense to have these redirects handled by Vuepress instead of by nginx, managed in a separate (private) git repo? vuepress-plugin-redirect looks kind of relevant, and I see some Github Issues talking about calling addRoutes() directly (vuejs/vuepress#160). Thoughts?

Implementing these redirects via nginx is straightforward enough, if that is what we decide.

[hugomrdias]

we talked about it but we would get the 301s that we want