v1.0.0 Release 🚀

[fsdiogo]

Release checklist:

• Add page
• Download page
• Update share.ipfs.io and dev.share.ipfs.io
• Don't rely on the public gateway (Use a js-ipfs instance instead of using the public gateways  #43)
• Update copy and assets (App copy and assets #41)
• Add project to Transifex (i18n: add to Transifex #33)
• Fix https://github.com/ipfs/js-ipfs-api/issues/797 (Strange behaviour without IPFS Companion #22)
• Post a link in this thread

[lidel]

Let's add translations to the end of the list – I can help with that :)

For "WebUI" integration take a look at what @olizilla did with IPLD Explorer:

• https://github.com/ipfs-shipyard/ipld-explorer
  standalone app that depends on ipld-explorer-components
• https://github.com/ipfs-shipyard/ipld-explorer-components
  a dependency used by both ipld-explorer and ipfs-webui

@olizilla Please confirm if creating ipfs-share-files-components and following Explorer's conventions is the right way to do this?

[hacdias]

Hmm, I thought we were just giving links for share.ipfs.io/#/add/hash/hash2 and not really embedding this into WebUI.

[olizilla]

The dream is to have a bunch of separate apps that link out to each other. We're going to try it out with the share app to see what the UX is like.

For context, I'm not super happy with ipld-explorer-components but it's the least worst solution for now, to get webui to a state we can release it. Once WebUI is out there, then we'll be focusing on building out the reusable component library that @hacdias has always dreamed of.

Composite components (things more complex than "Button", like IPLD Explorer) are tricky, as, while there are a many ways to share css styles from reusable components, the path for publishing components with i18n locales is much less clear, but we'll find a way.

[olizilla]

We need a fix for https://github.com/ipfs/js-ipfs-api/issues/797 before we can release this

[jessicaschilling]

Closing - stale, and superseded by this week's hackathon activity.