Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FTR:Website: Brief for updates to content, structure and visuals #47

Open
2 tasks
barnabee opened this issue Mar 1, 2021 · 1 comment
Open
2 tasks
Assignees

Comments

@barnabee
Copy link
Member

barnabee commented Mar 1, 2021

Website updates brief

Target state

  • Project/Protocol/Community centred
  • Not sales, not an exchange homepage
  • Open source content, assets, code
  • Anyone (whether new to or familiar with Vega) can find what they need quickly, whether it is on the site or not, including:
    • about Vega
      • headline
      • describe project
      • mission
      • high level design goals (“pro” / “real world” trading)
      • team behind Vega
      • open/values/get involved
      • roadmap/link to post?
      • governance
    • overview of the protocol (summary level - images/bullet points)
      • trading protocol
      • liquidity mining
      • cross-chain/bridge
      • governance/market creation
    • testnet & Console
      • how to use
      • prominent Console link
      • info (nodes, etc.)
      • stats
      • block explorer
    • protocol/technical documentation
      • new protocolised docs
      • API docs (all three)
      • client libraries
      • sample code
      • tutorials/walkthroughs
    • community fora
      • forums
      • discord
      • TG (secondary)
    • published articles/press releases/blog posts/videos
    • social media channels
      • GitHub
      • Twitter
      • YouTube
      • ...
  • Succinct, supported by visuals
  • DO NOT duplicate things covered elsewhere, DO aim to create a very limited amount of additional content and focus on organisation, linking prominently to what exists elsewhere, writing succinctly and clearly with visuals to help

Audience

  • DeFi people (these pretty much all sit in one or more other categories)
  • Core early users (relatively small number of these, they try "everything")
  • Cex futures/perpetual/day traders (SBF fans/FTX users key target, BitMEX, Binance also)
  • Developers (building for fun/bounties)
  • Traditional finance crypto savvy “very early adopters” (secondary)
  • Large protocols/projects that need to hedge risk (secondary)

High level tasks

  • Decide if we are keeping current site generation tools/pipeline
  • Spec any development/devops work needed and do it (Big Fan/Oli?)
  • Open source [new?] website repository
  • Decide license for graphics assets and open source these (separate repo)
  • Define list of new pages to be created
  • Create updated structure/navigation (inc. external links, define whether pages will be split/combined)
  • Write new homepage content/spec any visuals
  • Design updated homepage and overall site structure/nav (Big Fan)
  • Update existing page content including splitting/combine
  • Design work for existing pages (if/where needed)
  • Write content and produce “specs” for diagrams/visuals for other pages
  • Design other pages (Big Fan, illustrator?)
  • Replace existing site with new as early as possible and deploy iteratively
  • Translations

Steps to complete

  • Review and finalise/publish the above
  • Create cards for tasks
@barnabee barnabee changed the title FTR:Website: Update content, structure and visuals of vega.xyz FTR:Website: Brief for updates to content, structure and visuals Mar 1, 2021
@barnabee barnabee self-assigned this Mar 1, 2021
@candida-d
Copy link
Member

Three suggested additions (@barnabee):

  • all the published papers (everything in the current papers section plus market risk, which is only linked to in docs right now)
  • temporarily link to the existing docs until protocolised docs site goes live
  • don't forget Medium in the socials section, and LinkedIn. Maybe worth linking to the linktree so that people can see all the official channels? We might get more imposter channels as things ramp up so I think it's better to link to everything

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants