Closed bedeho closed 1 year ago
Hierarchy: There is an overall lack of a strong hierarchy on the page, which makes it really easy to loose track of what is being said, and how things fit together. There are two things which currently communicate this, the changing of background colours, and the size of section and content titles. This needs to be cleaned up. Below I make a similar remark about the size of the hero header text.
I kind of feel like the landing page is really missing a table of contents navigation system on the side, by most standards it is a very long webpage for a landing page.
Here is some additional POVs from a marketing audit: https://docs.google.com/document/d/1RiVtqAWy4vvN8oiDXF_IqqwXYGoaK8FxfbVAGPbSiUA/edit
@bedeho I cant open the marketing audit from the link above as there are viewing restrictions on the link π«£
I haven't finished the work on the landing page tweaks yet but I wanted to share with you this update - I talk about the necessity of different file organisation for the website & the top navigation component which also encapsulates the solution for #618 β Please let me know what you think.
π₯ Video update: https://www.loom.com/share/68a1cf20d3ed46d2b69c1b0208fad520?sid=ffb8eced-cee5-425a-a1af-0946e08700e7
π Top navigation: https://www.figma.com/file/3uoobZkRhFF4yibFjCWa2D/Components-library?type=design&node-id=9441-14630&mode=design&t=TKsoKc20EiyRe94D-4
βΆοΈ Mobile top nav prototype: https://www.figma.com/proto/3uoobZkRhFF4yibFjCWa2D/Components-library?page-id=9441%3A2036&type=design&node-id=9441-18456&viewport=3194%2C1869%2C0.3&t=pOI9pRyZFifZNLNu-1&scaling=min-zoom&starting-point-node-id=9441%3A18456&show-proto-sidebar=1&mode=design
βΆοΈ Desktop top nav prototype: https://www.figma.com/proto/3uoobZkRhFF4yibFjCWa2D/Components-library?page-id=9441%3A2036&type=design&node-id=9441-137937&viewport=3194%2C1869%2C0.3&t=pOI9pRyZFifZNLNu-1&scaling=min-zoom&starting-point-node-id=9441%3A137937&show-proto-sidebar=1&mode=design
Wonderful work! Thank you for cleaning this up. I think we should not go overboard here, so try to restrain your appetite for creating order and beauty, as overall value of it is not as high as for Atlas product.
@bedeho I finished the work on design tweaks and those are ready to be reviewed β The video is quite long 42min - as it was a lot to address but I tried to discuss only the most important stuff here π«£
π₯ Video update (42min/x1.2) : https://www.loom.com/share/ecf71aa843c8427293e7665f46a669cf?sid=a56d1593-c80d-4650-9b34-8a946c4659a5
π Figma landing page tweaks file: https://www.figma.com/file/dmmYGgpFwRyHJ9cueKiTUx/Homepage?type=design&node-id=9588-235979&mode=design&t=V7peMQZAHRy3hGN9-4
βΆοΈ Landing page prototype: https://www.figma.com/proto/dmmYGgpFwRyHJ9cueKiTUx/Homepage?page-id=9533%3A139718&type=design&node-id=9588-235979&viewport=1672%2C878%2C0.07&t=8nz34GGxWVFzicEl-1&scaling=min-zoom&starting-point-node-id=9588%3A235979&mode=design
Thank you for this herculean effort!
Lets try to keep a separate iteration for this, because it became just too complex to give good feedback on both in parallel, and you are also not doing mobile variations of everything in parallel as I understand it. However, what I would ask is that unlike before, please allow me to sign off on mobile, because I think in the past it has been a bit deprioritised in terms of time and care it deserves.
I like these ideas, but perhaps its best to just pause the finalization of this before the dashboard is done then. So we just launch a frist version of the landing page which does not have this section, as dashbaord may take a lot of time to get done.
Looks brilliant! But lets
@bedeho thank you for the feedback! I dont have any comments on most of the points and while I already started iterating on few of those points - few questions came to my mind that I need to ask:
You mentioned cookies as too large and overlaping main image and specify mobile as the week spot here. I do agree that the main visual is important and if we wouldnt want to collect cookies then removing the small banner altogether seems like the best solution to achieve what you seek here as currently the banner which we use is preety small and even on the smallest mobile screen takes almost the minimum amount of space if we consider the amount of text we have there But if we want to have the cookies and collect it - then even on the polygon site which you mentioned - on mobile, the ussual approach is to make the banner prominent so the user takes the action first and then scroll the page (and it appears even if im not scrolling the page)
From my POV maybe its even better for us to ask user for consent upfront, they are already used to sites asking for it, rather than try to percieve the cookies banner as a part of UI that user has on top of their screen and they browse the page with it being open. Thats my POV, wdyt?
Im a bit confused by the hero feedback to the video hero and to know if you want us to stick with this concept or not as at first you wrote that we can have a first key visual + video below in a separate section ( and Im ok with that - workin on that iteration rn - but still I believe the video here is going to bring much more value than UI screenshots), but then below in CTA feedback you add that hero video should be the main action - is that refering to scenario in which we would keep the video as hero. In case if we would add additional section for video would you consider leaving the cta button at the top?
I have a feeling that CTA button in hero section paints a clear picture about what action we want the user to take next.
In terms of player - Im sure we can at the very least do some styling to a container it is inside even if we want to use an embeded player - though I would reconsider that as the common practice would be to use a "custom" video player - and by custom I mean it can be from some kind of library but one that does not link in any way to external platforms like YT, or Vimeo - using a custom player can give more professional feeling to the site + we dont link to any competitor platforms from it. So from my POV I would advice against using any kind of embeds - just simple player + video file - dont know what FE lang is used in Joystream but example library from react: https://video-react.js.org/
I wonder if price data/mcap data either should be removed entirely, or put somewhere else on the page, because it sort of does not feel like it fits in with the other data points. Price really is not traction, but is is useful context. Perhaps we can find some totally separate, but very available place to show price/mcap/supply data?
Sure! I what is the importance of the price/mcap/supply data then? Should it be higher than the traction?
I'm not sold on the first, its too generic and takes a ton of space, but not sure about the other one either, did not see a live demo.
Is there anything in particular that you would like to emphasise in the Builder section? I will make more explorations for this but Im curious if you have a particular vision for the key visual here.
Thats my POV, wdyt?
I'm not sure, but what if we at least
Hero
No here I'm very convinced that people will not be sufficiently invested to start playing a video, which can and will buffer (and people know as the evaluate whether to even bother) with audio (which they may not even be able to listen to) which will last at leastl 10-15s before you have any clue at all about what is going to happen. It requires too much investment. We have to hook them sooner and convey more in less time, the title of the page helps, but its not enough.
Video player
I honestly did not understand your remark here, sorry :(
Builders
Its really just there to capture early leads, and also to communciate that we are serious about having third party developers building. So it does not need to be very ambitious, its just some small optionality.
@bedeho here is the hero & video section iteration - I present here some new ideas and concepts which are ready to be reviewed β
π₯ Loom video (16min, x1.2): https://www.loom.com/share/b6efc88b68df48e8b5b333befcc26962?sid=804cd82c-5065-4e16-858b-6a9f820d3e69
π Landing page tweaks exploration file: https://www.figma.com/file/dmmYGgpFwRyHJ9cueKiTUx/Homepage?type=design&node-id=9711-29985&mode=design&t=NgEvaCTPBOUtXprx-4
@bedeho here are the designs for all other sections covering the rest of the feedback you left for me here - this is all ready to be reviewed β This time I have a video update and two prototypes for you (everything is explained in the video) π
π₯ Video update (18 min, x1.2): https://www.loom.com/share/93661f9fdd37459d8b3f934beb480b24?sid=9ae4e7d7-e42d-41cd-a108-e82994b99ebc
π Landing page tweaks exploration file: https://www.figma.com/file/dmmYGgpFwRyHJ9cueKiTUx/Homepage?type=design&node-id=9782-131802&mode=design&t=NgEvaCTPBOUtXprx-4
βΆοΈ Ist Prototype (header hierarchy) : https://www.figma.com/proto/dmmYGgpFwRyHJ9cueKiTUx/Homepage?page-id=9708%3A169936&type=design&node-id=9777-114585&viewport=3963%2C2868%2C0.27&t=dfVbYdSRq7lALU0u-1&scaling=min-zoom&starting-point-node-id=9777%3A114585&mode=design
βΆοΈ 2nd Prototype: (all bolded) : https://www.figma.com/proto/dmmYGgpFwRyHJ9cueKiTUx/Homepage?page-id=9708%3A169936&type=design&node-id=9782-125990&viewport=3963%2C2868%2C0.27&t=dfVbYdSRq7lALU0u-1&scaling=min-zoom&starting-point-node-id=9782%3A125990&mode=design
Overall, looks fantastic!
@bedeho all of the requested changes to the Landing page are added, the designs are finalized, refreshed the whole UI of the homepage and aligned it with our other landing pages + prepared RWD for the dev so we start using proper grids in here as well β Its ready to be reviewed!
π₯ Video update: https://www.loom.com/share/0942033fb72542ed80a6122ef131f809?sid=cabd7fbd-f78e-4be6-8bfa-cce68d424c99
π Homepage changelog: https://www.figma.com/file/dmmYGgpFwRyHJ9cueKiTUx/Homepage?type=design&node-id=9962-134795&mode=design&t=FHVZ9hkvqZSjzEvk-4
Fantastic work, looks great!
Background
The Joystream landing page (http://www.joystream.org) has been live a while now, and it requires some readjustments to align it better with current priorities.
Proposal
Addendum
Can we also tackle this one in the same go?
https://github.com/Joystream/joystream-org/issues/618