Update empty state content

[ckpringle]

The Chore

Update copy for empty states across block explorer so that you're never left with nothing on the screen and nowhere to go / reason why.

Tasks

• [x] Define empty state content for:
  • [x] - Governance proposals
  • [x] - Markets
  • [x] - Oracles
  • [x] - Transactions
  • [x] - Parties
  • [x] - Blocks
  • [x] - Assets
• [x] Review with stakeholders (Edd)
• [ ] Design template for empty state messages
• [ ] Review with team
• [ ] Implement

Additional details / background info

• There will never be 0 instances of, validators, genesis parameters, or network parameters

[edd]

Recapping a chat thread:

We’re thinking about empty states for various pages Which of these could be legitimately empty, and which should always have some content? For example, I assume there will never be 0 blocks in the chain. I’ve done a quick sort based on my assumptions:

There could be 0 instances of:

• Governance proposals
• Markets
• Oracles

It’s very unlikely there will be 0 instances of:

• Transactions
• Parties
• Blocks
• Assets

There should never be 0 instances of:

• Validators
• Genesis parameters
• Network parameters

Chit chat

@edd: I’d be careful with the nevers, it’s more like SHOULD never :slightly_smiling_face: But there should never be 0 validators - without them, no blocks will be made, the whole excercise is pointless, > everyone go home (edited)There should never be 0 assets - all existing networks have at least 1 asset in the genesis file (i.e. at block 0)

@neildawson: Re: never: yeah, I suppose another way to look at it is empty states vs. error messages @Edd think the others hold true though (anyone could start a vega network that would prove almost any of them@edd

@neildawson It sounds like we should still have some kind of state to cater for the should nevers, just in case. Do you agree? (edited)

@edd Never ever empty: validators, genesis, network parameters. Almost certainly never ever but probably never fingers crossed: blocks @neildawson For the almost-certainly-never-evers, I know you could go propose an asset to get something in that list. Is there any action you can take to populate the transactions, parties, or blocks lists? e.g. go make a trade on console

@edd Transactions: yeah. An order would be a TX. Or a proposal. Parties: yeah, in THEORY every party already exists. In practice they’re only listed when they have ‘done a tx’. So as above. Blocks: No, they should be produced continually or the network is broken. They will be empty if nobody does anything. This is fine.

[neildawson]

Ran proposed empty state messages past @edd on Slack. Agreed not to have CTAs for unlikely empty states, simply saying "Check back later":

Next step is to explore how we present the empty states in design, e.g.:

Miro board

[joellecharlotte]

See attached the chosen direction: a generic skeleton placeholder under each page title and some empty state text. Each of the pages has been mapped out in the Figma file here. I've used Transactions as the template to demonstrate how it would behave on the XSM breakpoint.