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

Homepage design [product design step 2] #28

Closed
Tracked by #35 ...
0xjona opened this issue May 24, 2022 · 15 comments
Closed
Tracked by #35 ...

Homepage design [product design step 2] #28

0xjona opened this issue May 24, 2022 · 15 comments

Comments

@0xjona
Copy link
Collaborator

0xjona commented May 24, 2022

In step 2 we are designing together with @claudiofabbro the UX of the alpha version of the product and the landing page.

Coming after a few weeks of work from now, when we’ll have defined all the components of the ALPHA and what the landing page is about.

We’ll have to collect all the inputs coming from key references (e.g. https://drand.love )

@0xjona
Copy link
Collaborator Author

0xjona commented May 24, 2022

@irenegia will have to provide the content for the homepage, we’ll start discussing and producing soon (missing issue)

@claudiofabbro
Copy link
Collaborator

step 2 – Alpha UX and home page

Research phase (week 23-24)

  • Collect references on competitors / similar players in the field @claudiofabbro
  • Publish a document for the research phase / results of the analysis (optional) @claudiofabbro @0xjona

— KEY VISUALS / STEP 1 NEEDS TO BE IN AN ADVANCED STAGE HERE —

Design phase (week 25)

Approval phase (week 26)

@0xjona 0xjona changed the title Alpha UX and homepage [product design step 2] Homepage design [product design step 2] May 31, 2022
@0xjona
Copy link
Collaborator Author

0xjona commented Jun 1, 2022

briefing here is also about #copy

@0xjona
Copy link
Collaborator Author

0xjona commented Jun 2, 2022

@0xjona
Copy link
Collaborator Author

0xjona commented Jun 6, 2022

@irenegia here’s a checklist of what the homepage will be about

  • Link to lite paper (update this with relative documentation issue)
  • link GitHub with readme (updated with Install guide)
  • link to news (this could either be https://mirror.xyz or https://medium.com so it’s external for now
  • short about (explaining mainly the “metaphor” used)
  • team section (how many people are involved? So that we start imaging the relative space needed
  • link to launch the MVP/ALPHA (which will open a new tab, with an intro/disclaimer before connecting wallet)

@claudiofabbro @Steve-Rog

Do we have other references?
https://protocol.ai/work

@0xjona 0xjona mentioned this issue Jun 6, 2022
3 tasks
@0xjona 0xjona moved this from Backlog to Implementation in retriev.org Jun 8, 2022
@0xjona
Copy link
Collaborator Author

0xjona commented Jun 8, 2022

@irene how do you expect the team section?

Exact questions are:

  • How many people?
  • name surname, and max 4 word for description is ok?
  • no pictures, right?

@irenegia
Copy link
Collaborator

irenegia commented Jun 9, 2022

name surname, and max 4 word for description is ok?
no pictures, right?

Yep!

numb of persons = us, the team
this! :)

@0xjona
Copy link
Collaborator Author

0xjona commented Jun 10, 2022

@0xjona
Copy link
Collaborator Author

0xjona commented Jun 14, 2022

UPDATE FROM WEEKLY CHECK-IN for @claudiofabbro
We should consider to add

  • contributors to add in the team section

we expect this to be one bottom line/sentence with a sequence of names, right below team members

  • link slack channel to add

we expect this to be slack (+ eventually twitter) logo on the footer bottom right below "news/teams" section

@nicola
Copy link

nicola commented Jun 16, 2022

Let's avoid the team page on the website, the spirit is that this is a very simple lightweight composible protocol, not a company/product. We should keep it as lightweight as possible. It's ok to have team page on discord or on github.

@irenegia
Copy link
Collaborator

Let's avoid the team page on the website, the spirit is that this is a very simple lightweight composible protocol, not a company/product. We should keep it as lightweight as possible. It's ok to have team page on discord or on github.

ok

@0xjona
Copy link
Collaborator Author

0xjona commented Jun 16, 2022

The team section is in the footer so it’s not so visible; we can redesign it to look more like an acknowledgment page (plus some notes about cryptonet as a whole) rather than a corporate team page! @claudiofabbro

@irenegia
Copy link
Collaborator

The team section is in the footer so it’s not so visible; we can redesign it to look more like an acknowledgment page (plus some notes about cryptonet as a whole) rather than a corporate team page! @claudiofabbro

discussed with Nicola, we only need a "contributors" section

@claudiofabbro
Copy link
Collaborator

No problem, I'll fix it

@0xjona
Copy link
Collaborator Author

0xjona commented Jun 17, 2022

@irenegia I'm sorry to say that having a "contributors section" (on the website right?) doesn't mean much.
So as long as this indications are on a high level, I'll take care of turning them into specifications

@0xjona 0xjona moved this from Implementation to Validation in retriev.org Jun 28, 2022
@0xjona 0xjona closed this as completed Jul 5, 2022
@0xjona 0xjona moved this from Validation to Done in retriev.org Jul 5, 2022
This was referenced Jul 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants