Page MenuHomePhabricator

Design: rework Event Summary page to fit in new metrics
Closed, ResolvedPublic

Description

What to do

Create a design for the Event Summary page that accommodates both 1) the complete set of Summary metrics and 2) the Participants and Category filters (design changes to which are covered in T216280)

Why we're doing this

Prateek has created a very attractive new design for the Event Summary page (see below). That page, however, is considerably deeper than the old design, in part because it assumes that the Participants and Category filters have moved to the Settings page. That is no longer going to happen, so we need a design that shows the new metrics AND does not make the filters difficult to discover.

Design parameters

  • Show the page chrome, including logo, breadcrumb navigation, login and language controls, help | page name and slug, Settings/Update/Download buttons and message.
  • Show the Event-setup data: date/time, wikis, Categories if used.
  • Show all Event Summary metrics (see list below). The arrangement into Contributions, Impact and Participation sections is desirable, for comprehension.
  • Link to "View all edits" page
  • Links to glosses of all on-page metrics
  • Include the Participants and Category filters in a way that makes them clearly discoverable. There are likely various approaches to this. A compact design that shows these in the first screenful (at least on an "average" sized monitor) is one.
  • Assumes Category filter is independent of Participants This design will be built in Release 2 and should assume that Categories are independent of Participants. Other than whatever changes to are specified here or in the tickets listed immediately below, no new functionality should be included.
    • Separate tickets exist for filtering UI changes This design should encompass filtering UI changes tracked the following tickets: T209107 will be built in Release 1 and requires mostly small clarifications to functionality; T216280 requires changes to accommodate having Participants work independently from Categories.
  • Per-wiki metrics, which both designs pictured below supply are desirable but may not be required, if there is a need to save vertical space.
Required Event Summary data

Data not previously displayed on this page are labeled [NEW].

Contributions

  • Pages created
  • Pages improved
  • Edits [NEW]
  • Bytes changed [NEW]
  • Files uploaded
  • Wikidata items created
  • Wikidata items improved

Impact

  • Views to pages created [NEW]
  • Avg. daily views to pages improved [NEW]
  • Unique pages with uploaded files [NEW]
  • Uploaded files in use
  • Avg. daily views to files uploaded [NEW]

Participation

  • Participants
  • New editors
  • 7-days retention
Existing Event Summary pageDesign for ultimate page when filters are removed
Screen Shot 2019-02-18 at 11.38.42 AM.png (883×1 px, 118 KB)
event-summary-redesigned.png (1×1 px, 168 KB)

Event Timeline

jmatazzoni renamed this task from Design: rework Event Summary page to fit in new metrics to Design: rework interim Event Summary page to fit in new metrics .Feb 18 2019, 8:14 PM
jmatazzoni updated the task description. (Show Details)
jmatazzoni updated the task description. (Show Details)
jmatazzoni updated the task description. (Show Details)

@Niharika @MusikAnimal, in order to include the new metrics but save vertical space, so as to make the filters discoverable, I put into the design requirements that:

...it's not clear to me that the per-wiki metrics are required. If people want per-wiki metrics, they can get them in the relevant reports.

If there is some reason I don't see why per-wiki metrics are important on this page, now that we have downloadable reports that can give per-wiki results, then please speak up.

@Mooeypoo, I think the intention here is to make a design we can live with (possibly permanently) but which doesn't require a lot of rewiring. Are there any technical requirements you want to add—e.g., about how it will be build or things not to do?

@Niharika @MusikAnimal, in order to include the new metrics but save vertical space, so as to make the filters discoverable, I put into the design requirements that:

...it's not clear to me that the per-wiki metrics are required. If people want per-wiki metrics, they can get them in the relevant reports.

If there is some reason I don't see why per-wiki metrics are important on this page, now that we have downloadable reports that can give per-wiki results, then please speak up.

I think moving the filters to the Event Settings page won't be terrible. I personally really enjoy the per-wiki breakdown, and I don't think I should have to resort to wikitext/CSV to get this information. We would need to bear in mind that including all the columns listed at T205561 may cause the table to be quite wide, but it should look OK if we make it scrollable, such that it won't exceed the viewport.

In T216304#4965364, @MusikAnimal wrote:

...I personally really enjoy the per-wiki breakdown, and I don't think I should have to resort to wikitext/CSV to get this information...

Something has to give here so that the filters are discoverable. I was trying to give @Prtksxna some leeway. However, I did not say the per-wiki metrics are not allowed; I just said that they are not "required." There are 6 new metrics to fit in here (all are listed above). I'm sure Prateek will have lots of ideas for expressing them in a way that is more compact than before.

What the existing page lacks, btw, is precisely what the new one above emphasizes: the total figures. I do continue to believe that those are more valuable as a measure of event activity and impact than the per-wiki figures. Of course, neither of us is an event organizers...

jmatazzoni renamed this task from Design: rework interim Event Summary page to fit in new metrics to Design: rework Event Summary page to fit in new metrics .Feb 28 2019, 12:50 AM