v2.0.0 Release 🚢 Shipping the Revamp 🚀

[olizilla]

What needs to happen to get the revamp branch released

• All UI text to be localisable (decide on react-intl / i18next / https://github.com/lingui/js-lingui)
• Handle IPFS connection errors gracefully Handle IPFS connection errors gracefully #773 - See feat: add ipfs connection indicator and notifications #802
• Status page with node identity info and node bandwidth chart feat: node stats page #766
• Integrate file share app. v1.0.0 Release 🚀 ipfs-shipyard/ipfs-share-files#11
• Export and reuse ipld-explorer chore: reuse ipld-explorer as git submodule #771
• Polish files page. File browser polishing #748
• Improve perf of peer bandwidth stats (or disable it until a better api is available)
• Finish API address config page PR feat: guide the user when no api found #715
• Disable the CRA service worker, until we have the update mechanism in place. refactor: disable service worker #757
• Publish to webui.ipfs.io Publish to webui.ipfs.io #775
• Move the revamp branch to master, bump package.json version to 2.0.0, and tag it.
  • Switch transifex/ipfs/ipfs-webui to fetch new strings from master
    (see Meta: Translation Project for IPFS GUIs ipfs-gui#50 (comment))
• Publish to ipfs and release it. https://github.com/ipfs-shipyard/ipfs-webui#release-a-new-version-of-the-webui

Work that will wait until v2.1

Start tackling these after the revamp becomes the new master branch and is tagged for a release.

• Define a better deployment and update mechanism. IPLD Explorer announces when a new version is available. We could publish Web UI under a DNSLINK address, and have the app check a release version to see if there is a newer version (feat: prompt user to reload when updates available ipld/explore.ipld.io#21 (comment))
• File availability indicator. [wip] feat: add file status #718 asking for providers every file from every webui user will be slow, resource intensive and could spam the network, so this needs some more thought.