Spike: IPFS deploy and its impact on the user experience

vegaprotocol / ux-and-visual-design

A place to track work items for the ux and visual design team working across all frontend apps, sites and tools

0 stars 1 forks source link

Spike: IPFS deploy and its impact on the user experience #81

Closed ckpringle closed 1 year ago

ckpringle commented 1 year ago

There have been a number of mentions of IPFS deploy for console, and the potential need for a change to the user experience.

Tasks

[ ] Speak to Matt, Dex and Edd about what the current plan is
[ ] Identify what that means to what we need to do in console, on the website linking to console
[ ] And understand what this might mean for the other front ends - is governance / token going on to IPFS for example? What else?
[ ] Share with Barney publicly to sanity check

PeteWilliams commented 1 year ago

Spoke to Edd, this one is still blocked as per https://github.com/vegaprotocol/vega.xyz/issues/246. Put a placeholder in Figma here: https://www.figma.com/file/K49Nx7XfocShhHcwwQzQkm/Console-V2?node-id=4034%3A38792 Contacted Dave Mac to find out if this is 'legal' content that he should be involved with, or just advisory.

PeteWilliams commented 1 year ago

One for @campbellssource to chase Dave Mac on.

ckpringle commented 1 year ago

Bunch of IPFS notes on "Close out IPFS / console interstitial page questions" here https://app.asana.com/0/search?q=ipfs&child=1203411638270688

campbellssource commented 1 year ago

The job of routing to a correct version of console will not happen on the website, instead it'll link to https://console-fairground-wtf.ipns.dweb.link/ and it'll handle the rest. Once the IPFS hosted option is working we are going to demo what we have in place and review the requirements

mattrussell36 commented 1 year ago

This has been superseded by other work around ipfs