Essential header/footer menu items.
Display of new music/playlists/variety.
MUSIC FIRST
Essential points for homepage communication (to be homogenised with player landing page)
Essential header/footer menu items.
Display of new music/playlists/variety.
MUSIC FIRST
Essential points for homepage communication (to be homogenised with player landing page)
@Timothee Now you have access to the Figma, letās develop a list of three (max) critical changes we need to make to the current layout or design that we can include in our first homepage #platform:epics.
@melis_tailored Thoughts on whatās the most tip-top pressing design issues of the website? e.g. is there anything thatās currently just broken (i.e. looks wrong)
To be able to answer to your question @angus, I need to know which version of the website homepage we are talking about: there are several Figma files containing different versions of the homepage:
I donāt understand which one is the latest and who did what.
@Timothee Good question! @melis_tailored @auggod any thoughts on which of the three is the latest / correct version?
Unable to access the second two Figma links, but can say āHugo V1ā has been functioning as the operating document!
@sganesh Yes, Hugo V1 has been the reference point. Nevertheless, I believe we are at a point where all of these designs, Hugo V1 included, are simply proposals. I believe @alexcrane was the primary designer in the past.
These initial proposals havenāt been updated in ~2 years to my knowledge.
@Timothee Letās keep using this topic. As we discussed on the call
develop
branch against https://www.figma.com/file/e6powcUMz6RNuYZwRNW0oOQy/RESONATE_NEW_WEBSITE_HUGO_V1?node-id=312%3A1
Weāll then use that, along with Player landing page text, to set our #platform:epics agenda.
do you have a link for the call?
Hey everyone. Iām interested in this topic in regards to the existing WordPress site and existing content like all sign-up and payment forms, blog posts, the Press section, Team + bios and all Support pages.
I think we lost analytics years ago, so not sure what the direct traffic is to some of these areas, but thought it worthwhile to check in with this team if thereās been an audit of everything to be replaced, or whether we need to maintain WordPress for certain things.
yes, important you are involved peter.
if you look at the new website text - you can see which pages are intended to be kept.
existing content like all sign-up and payment forms, blog, press/Team + bios (this page is being re-done) and all Support pages are intended to be kept from the menu.
if you think thereās something missing, let me know.
it would be an idea if you, angus and timothee meet to discuss this perhaps?
@angus Here is what I did:
develop
branch againt the Figma file: I took a screenshot of each page and paste it along its correspondig frame inside the Laptop 1024 (archive 210702) pageNow, I have some questions that I will share with you during our 2021-07-06T12:00:00Z meeting, specially about Resonate eco-system architecture (Player app vs Hugo website vs WordPress website) and design system (Figma files vs @resonate/tachyons).
See you tomorrow!
Great, yes we can discuss this today after the Player meeting
To follow the yesterday discussion about the Player & Website Epic with @angus @Hakanto and @auggod, here is my proposal for the new design of the shared header and footer. I didnāt work on the mobile version yet, because I would like to discuss and validate some important design decisions first, specially for the header that raises very important questions with huge impact on the whole Resonate user experience.
Website:
Player:
Not logged in:
Logged in (hover on user avatar)
Goal: designing a unified header across the whole of Resonate (website + player) to help people better understand and navigate between the different pages, while having the feeling of staying within the same platform (like Bandcamp or Soundcloud).
Design decisions and questions:
Website:
Player:
Goal: list the most useful links for all type of people (first time visitor, listeners, artists, journalists, developers, etc.) with clear and logical wording and grouping.
Questions:
Thatās all for the moment! I hope it is clear enough, and if you have questions, suggestions and feedbacks, please share it here before 2021-08-07T22:00:00Z so we can have some time to discuss it together and update the design accordingly. Thanks
The history of work on the ānew websiteā is in the project is here in this Basecamp project
And I made some additional notes on the design thinking and the Hugo implementation, with some added note from @Alex himself, in this documentā¦
Might be good to include any material that is still relevant from this in githubā¦ or on here
@peter @auggod tried out https://www.offen.dev/ ā¦but by default it collected too much. Needed proper more specific requirements for setup I think.
In particular, we need to āmeter upā the new signup flow on the website. I.e. define essential logging events of our own and have a data structure that can record them.