Design investigation: Explore how to make EventDetails more discoverable
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	ifried
	Mar 1 2024, 3:06 PM

Description

User story:

As an organizer or participant in an event, I want to more easily discover the EventDetails page because it has additional information that may be of interest to me (such as the contributions tab, grant ID, P&E Dashboard link, etc) that can help me more fully understand the details and impact of the event.

Background:

EventDetails gives the most complete picture of an event. It has all of the information about the event itself (such as date/time/wikis, etc), a full list of participants, statistics and message tab for organizers, and soon we will add a contributions tab for all users. However, it is not very discoverable. Right now, the main ways to access it are to a) right-click on the "more details" link in the event registration header, b) find an event has many organizers or participants, so it has a link to more in EventDetails, c) go to Special:MyEvents as an organizer, d) already know the event ID of an event and then manually add in Special:EventDetails and the ID into the URL, or e) somehow already know the URL already.

We want to change this so that all people can easily access it and share details of an event with others. Now that we are planning a project to show collaborative contribution data in a new tab in EventDetails, this work has been elevated to higher priority than it was in the past.

Other resources to check out:

T375702 - This is from when we were exploring ways to improve discoverability of the Collaboration List (which as previously known as the Event List). Some of the stuff may not apply to this exploration, but some other stuff may inspire you.

Acceptance Criteria:

Explore how we can make EventDetails more discoverable to all users who may want to learn more about the event, including:
- On the event page itself
- In the confirmation email after registering for the event
- Other surfaces/places where you think it would be useful
Explore if we should have the "more details" modal at all - or do we get rid of it and then just direct people to EventDetails to learn more? Note that, if we do this, we would want to modify Event Details to have a link to Register for the event and we may want to make it more prominent to promote the collaboration list (it is currently a small link at the bottom)

Related Objects

Mentioned In: T392123: Convert event details dialog to codex
T402240: Herald rule to add Connection team tag to maintained projects
T391908: Design exploration: Basic POC for tracking collaborative contributions
T388699: Figure out what to do with events in namespaces where registration is no longer allowed
Mentioned Here: T403118: Replace event modal with direct link to EventDetails
T378002: Promote Collaboration List on Special:EventDetails
T378205: Design: Navigation redesign of Special:EventDetails
T375702: Design exploration: Improve discoverability of the Event List

Event Timeline

ifried created this task.Mar 1 2024, 3:06 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 1 2024, 3:06 PM

ifried triaged this task as Low priority.Mar 1 2024, 3:06 PM

ifried updated the task description. (Show Details)

Daimona merged a task: T312946: Add link to eventdetails from inside dialog box.Mar 7 2024, 2:34 PM

Daimona edited projects, added Connection-Team (Connection-Current-Sprint); removed Connection-Team.

Just to add another reason why we might want this, here's an example of an Event that does have a Dashboard link but was added incorrectly in the wikitext.

As shared by @Sadads "The dashboard URLs sometimes are clumsy for folks" and he has "noticed this happening before", in this case "they forgot the organization breadcrumb in the url"

Moving to backlog, since we may work on it later but it is not currently on our roadmap

ifried edited projects, added Connection-Team; removed Connection-Team (Connection-Current-Sprint).Jun 5 2024, 7:18 PM

Daimona mentioned this in T388699: Figure out what to do with events in namespaces where registration is no longer allowed.Mar 14 2025, 12:17 AM

ifried mentioned this in T391908: Design exploration: Basic POC for tracking collaborative contributions.Apr 16 2025, 9:09 PM

ifried assigned this task to JFernandez-WMF.Jul 23 2025, 6:40 PM

ifried merged a task: T400197: [Placeholder] Improve discoverability of EventDetails (esp Contrib tab).

ifried edited projects, added Connection-Team (Connection-Current-Sprint); removed Connection-Team.

ifried moved this task from Upcoming / refining 💡 to Needs design on the Connection-Team (Connection-Current-Sprint) board.

ifried updated the task description. (Show Details)

ifried updated the task description. (Show Details)Jul 23 2025, 6:45 PM

ifried updated the task description. (Show Details)Jul 23 2025, 6:48 PM

ifried updated the task description. (Show Details)

ifried updated the task description. (Show Details)Jul 23 2025, 8:42 PM

ifried updated the task description. (Show Details)

ifried moved this task from Needs design to Design in progress ✏️ on the Connection-Team (Connection-Current-Sprint) board.Jul 30 2025, 6:46 PM

design proposal:

some changes to the event registration header + eventdetails

current	proposal	notes
		change copy in Event Registration header from "`More details`" to "`See full event details`". clicking on this link will take the user directly to EventDetails, meaning we'll remove the interim More details modal.
		add primary button next to the 'Event details' header for event registration ("`Register for event`"). change the "`View event page`" button at the bottom to a neutral, normal styling and add a neutral, quiet "`Find more events`" button next to it. remove the "`Visit the collaboration list...`" text below.

changes to e-mail confirmation

current	proposal	notes
		add a progressive "`View full event details`" button at the end of the email. change the styling of the "`View event page`" button to neutral normal.

Restricted Application edited projects, added Connection-Team; removed Connection-Team (Connection-Current-Sprint). · View Herald TranscriptAug 19 2025, 3:45 PM

I seem to recall we tried to implement something like F65789252 and it wasn't feasible in the component.

Daimona mentioned this in T402240: Herald rule to add Connection team tag to maintained projects.Aug 19 2025, 4:21 PM

Daimona edited projects, added Connection-Team (Connection-Current-Sprint); removed Connection-Team.

In T358872#11099150, @MHorsey-WMF wrote:

I seem to recall we tried to implement something like F65789252 and it wasn't feasible in the component.

@MHorsey-WMF, thank you! do you remember which part exactly of that mock up couldn't be implemented? maybe the 'Register to event' button next to the header?

In T358872#11099077, @JFernandez-WMF wrote:

change copy in Event Registration header from "More details" to "See full event details". clicking on this link will take the user directly to EventDetails, meaning we'll remove the interim More details modal.

This sounds reasonable. I'll admit I have a bit of sunk cost feelings here (also having become used to the modal), so I may be unable to objectively evaluate this option. Still, I have proposed it myself a long time ago, and it totally has advantages, such as dropping one of three interfaces that do basically the same thing. But I suppose we could maybe expand/rework the registration header a bit if there's something we'd like to keep on the page.

add primary button next to the 'Event details' header for event registration ("Register for event"). change the "View event page" button at the bottom to a neutral, normal styling and add a neutral, quiet "Find more events" button next to it. remove the "Visit the collaboration list..." text below.

Sounds good. The removal of the footer text would also partially address T378205 for the part that came out of T378002. One thing that I'm not fully convinced about is the styling of the "Find more events button": as it has no frame and it uses black, could there be a risk that it wouldn't be seen as an interactive element? Also a question: what would clicking the "Register for event" button do? Open a modal or take you to Special:RegisterForEvent? (Also double-check it in the context of cross-wiki events)

add a progressive "View full event details" button at the end of the email. change the styling of the "View event page" button to neutral normal.

I don't think we can change the styling because that is what Echo provides and we are (ab?)using.

In T358872#11099411, @JFernandez-WMF wrote:

In T358872#11099150, @MHorsey-WMF wrote:

I seem to recall we tried to implement something like F65789252 and it wasn't feasible in the component.

@MHorsey-WMF, thank you! do you remember which part exactly of that mock up couldn't be implemented? maybe the 'Register to event' button next to the header?

I can't think of anything off the top of my head, but I don't think it can be that button, because it would be the same as the "Edit" button currently shown to organizers.

(Also: resetting task priority given updated task description)

Daimona mentioned this in T392123: Convert event details dialog to codex.Aug 20 2025, 5:46 PM

Thanks for the feedback provided on this ticket so far, @MHorsey-WMF & @Daimona! As for some of the questions/concerns raised:

@MHorsey-WMF: Do you happen to remember which part we could not do?
"Find more events" button: Good callout that it may not be perceived as interactive. We can think about this a bit more, but perhaps it would be more clearly interactive if it was blue and maybe also bold. What do you think, @JFernandez-WMF?
I think that, if a user clicks on "Register for Event" on Special:EventDetails, we can bring them to Special:RegisterForEvent.
And, finally, on the topic of sunk cost: Yes, I think we may have waffled for a bit on this, since we already did some work on the modal and it seemed like perhaps there were benefits to keeping it. But, as we move from being primarily a registration solution to also being an impact reporting solution, the costs of keeping the modal now outweigh the benefits, I think. People will really find it frustrating to find basic data on the event, including the metrics. So, I think now is the time :)

As next steps, I have created a placeholder ticket (T403118) for us to work on this, ideally soon. We can hash out some of the open questions in this ticket or in the new ticket.

Also, one comment from team chat: I think we should make sure that the header is sufficiently informative. For example, it's currently displaying truncated address but not country.

All primary work on the design is done, and now smaller improvements will be worked on in the scope of T403118.

	F65789282: Screenshot 2025-08-19 at 12.17.56 PM 2.png
	Aug 19 2025, 3:45 PM

Design investigation: Explore how to make EventDetails more discoverableClosed, ResolvedPublicActions

Description

User story:

Background:

Acceptance Criteria:

Related Objects

Event Timeline

Design investigation: Explore how to make EventDetails more discoverable
Closed, ResolvedPublic
Actions