-
Notifications
You must be signed in to change notification settings - Fork 69
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
Feature ideas for a new NexGen WP Events central site #1009
Comments
Note: I'll start a P2 post in make.wordpress.org/community/ first to discuss different ideas and I'll be back to GitHub when the discussion is closed. |
The public discussion is now closed: https://make.wordpress.org/community/2023/08/23/call-for-ideas-new-features-for-our-nexgen-wp-events-central-page/ I suggest the next steps:
|
Context
All of them are in external domains (not in the main wp.org domain) and are difficult to find for a new-to-WP user. We already have some functionalities running in https://events.wordpress.org/?preview 🙂 Goals This landing page would be the first step of our vision of hosting all WP events in wp.org and having them all under the same domain umbrella. Requirements
Designs
|
Very clear request. Thanks for the detailed comment. After trying different ideas, I landed on this version. It reuses many existing components from the Design Library and I customized some blocks for the landing's cover area and links set with community images at the bottom. I also documented the section's information architecture in the site's IA map in Figjam. Here are the three principal pages on desktop and mobile.
For this first release, I'm drawn to put online a simple design where all events are listed in a table-ish area. In the future, we can try adding more event metadata to ease their finding and browsing. I would like your feedback on the following:
Regardless any comments, I need help revisiting all content and replacing the "lorem ipsum" examples. |
Those look great, thanks! I can take a closer look next week, but so far I noticed these:
To confirm, |
Thank you @fcoveram, this looks great! 😀
|
To @iandunn notes
This was intentional as on small screens is hard to interact with maps. The most common interaction is scrolling with two fingers, yet the visible area crops most of the map. To solve that interaction, I was thinking of relying on the full-size toggle (which I forgot to add to these mockups) to see everything at once, open the event details in a box, and open the event's external link from there.
In that case, radio options keep making sense, right? If users select
Sorry for not conveying Figma's page system correctly. The file now has a I hope that is more clear for its browsing.
Great. Working on it.
Awesome. |
Design (i3)Landing pageHere is a new iteration of the landing page. You can find the remaining pages in this section.
Since the changes applied were minor visual tweaks to blocks, I think we're ready to start developing unless there are blocking comments related to functionalities and behaviors. |
Love it! Thank you @fcoveram! 😍 👏 |
Love it as well! ❤️ Two ideas:
PS: I understand it might be too late to propose something like that, but I decided to mention it anyway as it was something that I realized now while reviewing the proposals. |
👍🏻
Yeah, we could keep the same UI, but just remove the "hybrid" option 👍🏻
Sounds great, thanks! |
Love the layout, typography and the consistency we're building between sites 🙂 I am struggling with the lack of colour in these 'generic' sites though. I have left this feedback on the Learn designs, where I felt like a 'feature' colour for each site, used in minimal ways, could help differentiate between say Learn WordPress, Documentation, Developers, etc. especially when they are open in tabs next to each other. For this particular design I think the problem for me is that the lack of colour doesn't reflect a 'vibrant' community. The images in the homepage really add more personality, richness and 'vibe', and I understand that not every page is meant to be like that, but I feel like we're at the other extreme. My experience at WCEU this year walking through the main spaces was that there was a lot of energy, colour and enthusiasm and I don't get that here. The photos could be one way to inject this, but the black and white treatment on the photos strips it away. |
The design looks great! Thank you, everyone! Just one request from me: can we please add a button to register/create WordPress.org profile to the page? I noticed recently at WordCamp Manila 2023, that many people, especially folks who are new to the community or the project, do not have a WordPress.org profile. Thank you! |
+1 to the colors and to add a call for registering in wp.org |
Thank you all folks for sharing your thoughts. I will reply to some notes to address the points made as next steps. to @foosantos points
It does make sense. I wonder though if in this first release we are surfacing many worldwide events to avoid seeing a "no events nearby" message in most users and not meet the expectation. Since this redesign aims to include all events, I envision an ideal scenario where that suggestion area displays at least 4 events.
I like the small map as it doesn't take the whole screen, yet keeps the idea of geographical location. I agree that hiding parts of the globe feels random or even region-centric, but a button hides that visual effect that is crucial on its desktop view. In terms of interaction, it doesn't seem that the toggle is less practical or brings a11y problems, but I might be wrong and am open to any change needed. to @adamwoodnz points The page style is truly a certain point. I agree with you that community vibrancy can be depicted through colors, but for the scope of this ticket, we're trying to reduce visual tweaks and reuse patterns from the Design Library as much as possible to release a solid first version. For the future, I envision a richer page to browse events in multiple ways and convey the energy of an active community, but the section also needs to weigh the visual consistency of living among other sections that host completely different content. This doesn't diminish your point, but designing a site as diverse as this is definitely challenging. In the same Figma file (page "i1", section "Final site ideas") you can see other ideas I was exploring for the long-term future. To @devinmaeztri and @dorsvenabili Great! I will include that section. With the content change mentioned above, I think this first version is solid enough to meet the core goal of seeing events in the new WordPress site. And for the future, there is definitely room to explore a more colorful style to convey the community energy and provide more tools to explore events. |
I tried a few ideas for this, but I couldn't give proper context to why Events visitors might need to create a WordPress.org account. I checked other site sections that redirect to the account creation, and all of them are within the flow of users trying to achieve something. To name a few: submit a Showcase site, reply to a forum question, and create a pattern. But in this case, you don't need to create an account to browse events. However, you do need an account to organize an event. But that page mainly redirects to Make handbooks/pages that seem a better place to call for the account creation. If you go to Make's landing page, there are no links to create a WordPress or Slack account. Therefore, it is more coherent with user flows to include that link in the handbooks referred from Events, and the landing page of Make. What do you think @devinmaeztri @dorsvenabili? |
Sounds good, @fcoveram! We'll make sure of adding that CTA in our texts! :) |
Design mockups are done and ready for their implementation. |
Copy for the pages is being worked on in this Google doc. cc: @dorsvenabili |
Agreed with @adamwoodnz on the color. A simple tweak would be to leverage blueberry in the bottom section to break out from the list. Similar to the current homepage. For the heading area, it could be interesting to also separate the numbers in an horizontal 3 column where they turn a bit more visible, celebratory; and also the heading becomes a bit more focused. If we color dark the left side of the heading, shall the whole upper side (nav, subnav) be also dark? Also, let's make sure the lines break without widows and orphans (ie. "and"). |
We're planning to add the new CSS text-wrap rules to the parent theme, which will hopefully improve this across all the sites in the network. Issue here. |
@dorsvenabili @thetinyl would it be possible to get the initial version of the copy finalized by tomorrow? Then we can update the Figma file with a more accurate reflection of the new pages. |
I think there's just the FAQ section that's being finessed, so we should be able to hit this timing no problem. 👍 |
Design (i4)Thanks for the comments. Here is a new iteration with the changes suggested.
For the mockup purpose, I kept the text area's width to indicate the number of columns it uses per breakpoint, so the line break will not be reflected until its code version, as pointed out here. Attaching the landing page views as all remaining pages have the same layout with the bottom area in blue. If we all agree with the changes, I will update the "Design" page with these mockups and mark them as ready for dev. And later updating the content once the copy document has folks' approval. |
Copy should be ready for you @fcoveram. 👍 Let me know if you have any questions or need anything adjusted. |
Mockups are now updated with the latest changes and content, and placed in the "Design" page. I'm also attaching the two images used in 2x and compressed with ImageOptim. |
@thetinyl I'm checking the copy of the page for organizers now, and I see that we're not having anymore the list of kind of events we had linking to the corresponding link to apply to become an organizer of that kind of event. The organizers page now is just an intro and a FAQ, the FAQ should be secondary. The main CTA is the list of kind of events we have linked to the forms to apply to organize. Can we recover that part, please? It's the most important part of that page. @fcoveram one note: in the events landing page, the bottom part says that if you can't find an event in your area, you can apply for it, because it has the same color as the footer it's not very visible. Can we change the background of that section? it's a very important CTA of the page, we want people to see it and click to find more to organize events. Thanks! |
That was a misunderstanding. We worked on the text above and below it, assuming that section would stay. I do see a few lines of text are needed to replace the lorem ipsum and I'll work on that today. |
@catederosia @dorsvenabili I've added some suggested copy in Figma based on @fcoveram's feedback for whenever you have a chance to look. |
The copy looks great! IMO, it’s ready to ship it! 🚀 |
Design (i4.2)Mockups are updated with the content's latest changes and with the following tweaks:
Images |
@fcoveram I've made a couple of minor copy edits in the Figma mockups.
I've added this copy in the Events copy document for future reference. (FYI: @dorsvenabili @catederosia) |
All content suggestions were applied. Thanks @thetinyl. Previous mockups in "Design" page were removed. Just from that page, they still exist in the iteration ones. |
With the page launched in its MVP state, should this be closed and new tickets opened when necessary? |
I would say yes. This ticket is about the need and expectations. What was made addresses both and is more clear to tackle improvements in a new issue. |
This ticket is to open a call for ideas for a future website to host all NexGen WordPress events, have a centralized place to find the next WP events, all open calls for speakers, sponsors, volunteers, ticket sales,... and to be able to filter them by continent, country, language, type of event, etc.
I’d like to share The Linux Foundation Events page for reference as it contains many elements that we're missing in the WordCamp Central Schedule page and that it would be very useful for attendees, sponsors, etc.
Highlights:
I'll be adding new ideas to this thread, and I welcome anyone with more ideas to share them here as well, thank you! :)
The text was updated successfully, but these errors were encountered: