Skip to content
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.

Chapter Invitation design changes #2283

Open
Sembauke opened this issue Jan 26, 2023 · 5 comments
Open

Chapter Invitation design changes #2283

Sembauke opened this issue Jan 26, 2023 · 5 comments
Labels
Enhancement New feature or request Help Wanted Extra attention is needed

Comments

@Sembauke
Copy link
Member

Discuss your ideas or share your views:

Make sure to tell how your idea will benefit this project.

It is a rough sketch, but this shows a feature which gives you the ability to view multiple events on the invitation page when joining a new Chapter.

It also redesigns the page so that it makes clear what the page is actually about.

A switch button instead of a regular button has been added to turn notifications on or off. This makes more sense. The button that says RSVPs now says Attend Event or Leave Event and the attendees at the bottom.

Feel free to discuss of course.

image

@Sembauke Sembauke added Enhancement New feature or request Discussion Ideas, feature requests, views on features. Anything which is a discussion. labels Jan 26, 2023
@ojeytonwilliams
Copy link
Contributor

Thanks for putting together this design, it's great to have something so clear that we can discuss.

The part I like the most is having the Chapter's other events visible. Since some users introduction to the app will be this page, I think that should help them understand what the purpose of a chapter is.

One quick thought: so far people have only created one event at a time, so it could be helpful have one list of previous events in addition to upcoming ones. That way there will typically be some indication of what the chapter is, even if all other events are in the past.

cc: @Sboonny

@Sboonny
Copy link
Member

Sboonny commented Jan 26, 2023

We should go for it 👍, maybe we use calendar icon instead of time to indicate, that it's a date. 🤔

list of previous events in addition to upcoming ones.

We can copy the design in "More Events" to display previous events below the attendees section. 💭 the code won't be different from the one used everywhere when I want quick responsive area 🤣.

grid: repeat(fit-content, minmax(20rem, 1fr)

@ojeytonwilliams ojeytonwilliams added Help Wanted Extra attention is needed and removed Discussion Ideas, feature requests, views on features. Anything which is a discussion. labels Jan 26, 2023
@Sboonny
Copy link
Member

Sboonny commented Feb 3, 2023

Is anyone working on this?


The button that says RSVPs now says Attend Event or Leave Event and the attendees at the bottom

What about creating a list of joined events, and only display upcoming events that aren't joined in this format, so we can have a list of joined events with button to know more or leave them.

BTW, what are your thoughts on this issue @allella?

@allella
Copy link
Contributor

allella commented Feb 3, 2023

If the focus of the page is on a specific event, like https://chapter.freecodecamp.org/events/22, then having "More Events" might be fine, but it's not really necessary in my mind.

For meetup groups, people tend to sign up for one event at a time and then they will come back to sign up to attend future events when they know their schedule is open.

The /events page has a list of the upcoming events, so it's only one click away if someone wants to see upcoming events for a chapter.

If I were to list "More Events" on an event page, it might be at the bottom, if at all, because things like attendees, sponsors, and event details are likely more important to an attendee than a list of future events.

@Sboonny
Copy link
Member

Sboonny commented Feb 5, 2023

👍

  • We should implement this in /chapters/{chapterid}
  • It shouldn't be implemented in events/{eventId}
  • Maybe display chapterCard at the button of the eventPage, but let's delay this until this is implemented 🤔

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Enhancement New feature or request Help Wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants