Improve page metadata and link unfurls

neildawson commented 1 year ago

We think this would require major re-architecting and take weeks to implement and therefore questioning the value / urgency right now

The Chore

Page metadata seems to be identical for all pages.

In this example, Slack unfurled links to Token, Associate, Redeem, and Disassociate pages like so:

At the very least each of these should use the page's proper title (which also need to be improved, see https://github.com/vegaprotocol/frontend-monorepo/issues/3798). Ideally each should also have a description, and we should consider what other options are available.

Tasks

[ ] Research best practice for metadata and page unfurls
[ ] Consider in particular how proposal unfurls could give some insight into the content (and maybe status) of the proposal
[ ] Write meaningful descriptions for all pages
[ ] Implement metadata according to the above
[ ] Test/QA

Additional details / background info

neildawson commented 1 year ago

https://medium.com/slack-developer-blog/everything-you-ever-wanted-to-know-about-unfurling-but-were-afraid-to-ask-or-how-to-make-your-e64b4bb9254

sam-keen commented 1 year ago

I've started some investigation into how to achieve this (it's not so easy with an SPA - most crawlers and social media bots don't execute JS so we can't control it within the JS of the app, and may need some static file generation). Awaiting a chat with @edd as something similar may be needed for Explorer.

@ckpringle if we opt for descriptions too, who should I go to for content? Thanks

JonRay15 commented 8 months ago

I dont care about this and am unsure we will ever do it .... unassignig myself..

vegaprotocol / frontend-monorepo