Repository navigation
Tickets section on the homepage. #1075
Description
Activity
Not sure about this from a functional and design perspective. The tickets are quite expensive, and ideally, you want people to first understand the value they're getting, because if they see the price before reading anything or exploring the content, there's a high chance they'll just close the page.
Of course, some people come specifically to check the price and already know what they're paying for. For those, we already have two CTA buttons on the homepage: one in the hero section and one in the top corner that's visible across all pages. This layout is pretty standard for similar conferences.
Rustweek does it the same way and a few more community conferences.
JS Nation has ticket info on the homepage too, but it’s placed all the way at the bottom, after the program, speakers, full schedule, social events, and bunch of stuff. The idea is the same: show the value first, then the price. I do like the idea of having one longer homepage, rather than having a tree structure, especially since we don't have any breadcrumbs, but I don't think with the current layout we have that it's a good idea to put the prices right in the front.
We could follow that approach as well, but to make it work, our homepage would need to be longer.
Context
We would like to have tickets mentioned on the homepage, so the homepage is longer, and when the user scrolls down, they see a TL;DR of what we offer.
Requirements
- We can reuse the tickets container
- Title: type of ticket
- No price mentioned
- Text field: ~40 words in length
- Under it a "Register now" button in each container
- Under all three containers: volume discount, centered
I was wondering if it's a good idea to add another section on our homepage that shows a bit more details about the tickets.
Not the full breakdown like this one:
But maybe a smaller, more compact version of this?
WDYT?
cc @clytaemnestra @nikoshell @Daksh777