FTR:Website: define and agree goals

[barnabee]

Proposed goals of website project and approach for next steps (to be ticketed).

Goals

• Open source website
• License content and assets under something like Creative Commons
• Improve first impressions explanation of Vega
• Increase prominence of Testnet, including access to Console without account
• Task based / “choose your own adventure” reorg: handle the top reasons people come to the site better (often this will just be a jumping off point)
• Ensure content style is project, technology, community first and reflects our thinking about how we talk about Vega
• Make the structure and code accessible to community contributors
• Add design finesse and illustrations/graphics where helpful
• Add content for key specific user segments (trading, liquidity provision, validators)
• Add content for roadmap
• Build landing page / micro site for Testnet (does this live in other project)

Approach (to be ticketed next)

1. [x] Run workshop(s) to review current site and collect feedback
2. [x] Propose and present a solution approach, agree sequencing, cost/scope
3. [x] Ticket tasks

[barnabee]

Extra points discussed in stand-up:

• Open source once we feel we have/can explain the project
• [ ] Create new repo to be public (nuke history)
• [ ] Ticket to check legals around font, graphics, site
• [ ] Prepare an announcement of "website 3.0 community edition" / whatevs (not necessarily before opening)

[edd]

Note for clarity: The thoughts below related entirely to the Fairground microsite Hey, @goslingo asked me a couple of questions and not having been involved much in the micro site project I’m putting them back here with my thoughts:

• Open Source: Sure. Let’s do it in a separate repo specific to the fairground site
• Hugo vs Plain HTML. I don’t have a strong opinion here really. Looking quickly over the designs, the ‘Active Incentives’ and news sections are what would need to be updated. As @goslingo they could probably be populated in JS, so lends itself to being a static site. However! If it turned out that there was a requirement for different languages, that might change the game. @rebeccajsimmonds is this only being done in English?

I can set up Netlify builds when appropriate

[campbellssource]

related https://github.com/vegaprotocol/community/issues/47