Suggestions before release

[2color]

TODO

• Replace the CTA, with a permalink to the "Pick the tool that fits the job."
• Add Georg Greve's picture
• Make the quotes links to the case study or video
• Replace "Anywhere data needs to be verifiable, CIDs tend to show up." with "Anywhere data needs to be verifiable, CIDs are helpful.
• Remove numbers for categories in "Running in science labs, game studios, art vaults, and low earth orbit."

Pick the tool that fits the job

• Add the UnixFS DAG-CBOR libraries from Add links to libraries for working with CIDs in different languages #4
• Add radicle-artifact
• Add debugging tools
  • https://check.ipfs.network/
  • https://dag.ipfs.tech/
  • https://ipfs.github.io/public-gateway-checker/
  • https://ipns.ipfs.network/

Hash around, and find out

• Add link to CID inspector

General

• Fix the favicon and logo
• Test og tags
• Ensure font sizing is consistently applied
• Add plausible metrics including events for specific interactive elements

[vmx]

The "running in production at" section:

• The logos have a hover effect, hence I expected them to be links.

The "Not a platform to migrate to. A property you add." section:

• For some reason, at first I didn't notice that the "Transport agnostic" was something I could click.
• Please make the "CIDs for addressing" and "Transport agnostic" text selectable. I dislike it when websites tell me which things I'm supposed to select or not (it would've been useful if I could've copy and pasted the headlines here instead of typing them).

In the "Public, private, and everything in between" section:

• The four cases look so clickable. I thought I could click them to find out more about those. This is probably out of scope, I just wanted to mention it.
• I would expect more of the keywords to be links. Namely: Amino DHT, IPNI, swarm key, Gateways

[2color]

Thanks @vmx. I've addressed all the points you raised.