Hello, would it be possible if there is a timezone change to have a warning "⚠️ Be aware a timezone change is expected during event." or something like that?

Here is the website I use to figure out timezones. It shows the place, and the timezone abbreviation (EAT, GMT, GMT +1, etc) above. Inspiration for the designers @gonyeahialam
https://www.worldtimebuddy.com/

In T308607#8051106, @Daimona wrote:

In T308607#8050124, @ifried wrote:

@Daimona - How can I reach this page for testing within the UI/user flow? Right now, when I click 'Manage Event,' it brings me to the UI to edit the event, so I don't know how I would find the event registration list page.

I don't think there's any entry point in the UI at the moment. You'd have to browse to Special:MyEvents directly.

Hi, just jumping in here, but when the user deletes the registration, they are informed they will not be able to re-activate it?

In T304738#7983810, @ldelench_wmf wrote:

Hey @CKMIE89 , think we're good to close out this epic & its subtasks? I see a number of comments which leads me to believe the "review" phase is complete - let me know if that's not the case. Thank you!

In T309337#8000023, @ifried wrote:

Thank you so much, @gonyeahialam! This new version has a description of the user ("You are an organizer") and of the action ("Event page: Enable on-page registration so participants can register for your event directly on the page"). Is there any reason that the new version has this additional text, but the old version only had the "Enable Registration" link? Is it so that there isn't arbitrary white space with the addition of the "Enable Registration" button below the title? Also, one quick language note: It seems a bit redundant to say "on-page registration" and "directly on the page." If we decide to keep the additional language, maybe we can just use "directly on the page" since it seems more clear?

Pinging @CKMIE89 since she requested an example in a previous comment -- any thoughts?

And @Daimona -- any thoughts on the example provided by Gregory?

Final thoughts: @ifried I am ok with option 2, with maybe a light drop shadow of the row (not a blue hover state that would be confusing for users)

In T310206#8000799, @Daimona wrote:

In T310206#7999048, @gonyeahialam wrote:

@Daimona @ifried The row in the table is a single unit so having the whole row clickable is the most intuitive option.

As I said, this is entirely possible, as long as we're comfortable with the drawbacks that come with it (I personally find it annoying when I can't right- or middle-click a link, but this may not be the same for everyone).

I think the inline would be great. 👍

In T308611#7989956, @Daimona wrote:

1. If the whole tile cannot be clickable than that is a viable option (having the title in blue) though it does change the design quite a lot.

I would prefer if the whole tile could have a different shade of the mouse hovers over it; is that possible?

2. The point of this page is that you can access your events and see their details, so it makes sense that the man function of each tile would be to access the details. It's quite standard that there is one main option to open a tile and sub-actions in the menu. (think of your inbox for example) :)

In the prototypes "view event page" would take you to the Event page. You access the event details by clicking on the whole event "tile" itself; which should be clickable.

Coud we have an example of what that would look like? If it is more reliable (ie, less subject to changes in the future° and works for all skins, Im sure we can make a design that works in that configuration:

In T308611#7979505, @Daimona wrote:

In T308611#7971265, @CKMIE89 wrote:

Great! Is there a link for us to test on patchdemo?

Sorry, I've just seen this comment... You can test it here (user:Alice, pass:patchdemo1), but note that it's not final (e.g., the buttons should be changed).

Great! Is there a link for us to test on patchdemo?

Having a "search" and a 'filter" option is quite common. I quite like your suggestion @Daimona

This is a good case where ideally we would need to have a good idea of the design options to design prototypes that reflects our questions.
At this point I think an educated guess by senior designers could help, if we have a version we can test. If we do, happy to put 2 YUX designers on it, and they can discuss with Gregory on the pros and cons of each.

In T304745#7810349, @Daimona wrote:

In T304745#7810326, @CKMIE89 wrote:

Hi @Daimona we are trying to gather feedback beyond V0 here, sorry if that was unclear. Feedback from the organizers will help to build that long term vision & roadmap.

Sure, that makes sense :) My point is that I'm not sure how we'll be implementing communication (because it's not v0), so I feel that I don't have enough context to properly answer some questions here. Mostly, it all boils down to whether we'll be implementing our own messaging system, which is something I've never heard about.

Hi @Daimona we are trying to gather feedback beyond V0 here, sorry if that was unclear. Feedback from the organizers will help to build that long term vision & roadmap.

Ok, so I'm not sure what scenarios might justify a hard delete (security?) But maybe this can be left as an option for the organizer?

Reading this I'm wondering if some kind of "waiting list" or "expression of interest" is possible, if an event is full but a "seat" opens up.... (bullet point 1 & 2 from @fnartey comments.)
You could then be automatically registered, or receive some kind of message informing you that registration is possible again?

@ifried Just for clarity, this would be different from making registration active/inactive?

let me answer here:

@all, if you want to recommend the key pages we should detail, please list them. Of course we will be doing the landing page, but what other ones are key to you, are you have the most questions about?

In T304113#7788587, @vyuen wrote:

Thank you for this @CKMIE89. A few clarifying questions:

1. When we say sitemap, are we talking about the conceptual planning of where each page go within the Event Center, or the human-visible sitemap that you can sometimes see at the bottom of a webpage? I assume it's the former but wanted to confirm. Site map we are talking about the ones on Figma you are commenting on
2. What feedback are you looking for? Is the intent to choose between option 1 and 2? not yet, but getting your informed opinion is important to us. Is anything major missing? Is there anything you don't think should be in the event center?
3. From looking at the sitemaps, I am not sure I understand which page/content is the "landing page" i.e. first thing user sees when they hit the Event Center? we havent designed it yet, at this point it's the "event center dashboard" block
4. I see there are distinction between logged-in and logged-out users; but if we were to go with splitting participants and organizer profiles, how will we know which to show if a user isn't logged in? if you are not logged in you cannot access the organizer side at all, and only those elements on the participant view where log in is not needed. Good question

In T304113#7788467, @Daimona wrote:

In T304113#7788425, @CKMIE89 wrote:

Great! Any specific information you are missing?

Mainly, I don't know anything about many of the subpage names shown there. However, it's pretty easy to get an idea of what those pages are for, and the map makes sense AFAICS.

Great! Any specific information you are missing?