Landing pages for gateways at ipfs.io, dweb.link, trustles-gateway.link

[lidel]

This is followu-up for verbal discussed in one of recent meetings between Shipyard and IPFS Foundation.
cc @cewood @mishmosh @2color for visibility and feedback.

Need

We want to reduce confusion by having meaningful landing pages at public utilities such as https://ipfs.io, https://dweb.link, and https://trustless-gateway.link

https://ipfs.io is the biggest problem, it redirects to project website, creating an impression the IPFS Project and Shipyard-run gateways are the same thing.

Below is my first stab at describing current state + what I would do to "fix" the confusion.

Proposed information

https://ipfs.io

• Right now redirects to https://ipfs.tech
• We want to stop redirecting, and return HTML page that
  • Explains what IPFS and IPFS Gateways are in one sentence + links to docs, specs, tests.
  • Asks user what they are looking for:
    • Information about this IPFS gateway (ToS, SLA, DMCA, contact) → https://about.ipfs.io (backed by https://github.com/ipfs-shipyard/ipfsio-about)
    • Information about IPFS Project → link to https://ipfs.tech (and/or https://docs.ipfs.tech, https://discuss.ipfs.tech, https://specs.ipfs.tech)

https://dweb.link

• Right now redirects to https://docs.ipfs.tech/how-to/address-ipfs-on-web/#subdomain-gateway
• We want to stop redirecting and return similar interstitial page as proposed for ipfs.io above
  • We want to explain how subdomain gateway at dweb.link is different than one at ipfs.io (one sentence + link to docs and specs?)

https://trustless-gateway.link

• Right now redirects to https://docs.ipfs.tech/how-to/address-ipfs-on-web/#subdomain-gateway
• We want to stop redirecting and return similar interstitial page as proposed for ipfs.io above
  • We want to explain how subdomain gateway at trustless-gateway.link is different than one at ipfs.io (one sentence + link to docs and specs)

Logistics

TBD. We could have separate repos, but I'd like to keep this contained and easy to review/maintain.

MVP does not have to be involved. We have about.ipfs.io at https://github.com/ipfs-shipyard/ipfsio-about.

We could reuse ipfsio-about repo and setup, and have landing pages at:

• https://about.ipfs.io/landing/ipfs.io
• https://about.ipfs.io/landing/dweb.link
• https://about.ipfs.io/landing/trustless-gateway.link

And then set up Nginx for non-/ip[nf]s on these domains as reverse-proxies for these URLs.

I think this makes things easier to land, @mishmosh can review above URLs before we deploy Nginx configs and publish them at roots of these domains. And we can apply changes across all of them via a single PR to a single repository.

Thoughts?