-
Notifications
You must be signed in to change notification settings - Fork 5
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
Comments
@irenegia will have to provide the content for the homepage, we’ll start discussing and producing soon (missing issue) |
step 2 – Alpha UX and home page Research phase (week 23-24)
— KEY VISUALS / STEP 1 NEEDS TO BE IN AN ADVANCED STAGE HERE — Design phase (week 25)
Approval phase (week 26)
|
briefing here is also about #copy |
@irenegia here’s a checklist of what the homepage will be about
Do we have other references? |
@irene how do you expect the team section? Exact questions are:
|
Yep! numb of persons = us, the team |
The team is ? |
UPDATE FROM WEEKLY CHECK-IN for @claudiofabbro
we expect this to be one bottom line/sentence with a sequence of names, right below team members
we expect this to be slack (+ eventually twitter) logo on the footer bottom right below "news/teams" section |
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 |
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 |
No problem, I'll fix it |
@irenegia I'm sorry to say that having a "contributors section" (on the website right?) doesn't mean much. |
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 )
The text was updated successfully, but these errors were encountered: