(From the user feedback interview.)
User should be able to see actual data than just the numbers.
Basically add a div in each table cell and populate it on demand (see this for example). We can perhaps show a loading animation if it turns out to be slow. Note:
- The entire row will be clickable and we add the collapse/expand markers on the left to let people know the rows are expandable.
- Multiple rows can be expanded at the same time.
- Show a sane number of rows (say 10 for starters) and make the div scrollable.
- Totals row is expandable as well.
- User names and page titles are links (all left aligned in the div).
We don't touch the Event page tables and add another button for letting users see a more granular view of data which takes them to this page. All except one wiki are collapsed by default and we run the queries when user clicks a section open. This still needs us to run all five queries for a wiki at the same time, like in above mock, so we still need to do the performance testing .
This gives us the advantage of not having to complicate an existing UI that works well. The sections shown in the mock are all placeholders and can/will change depending on what data is deemed important. The other advantage is that we can show a lot more data - more freedom of playing with UI elements.
I think it makes sense (with this UI in mind) to go with Leon's idea in T182885#3949875 to show participants, new editors and retention on per-wiki basis. This also came up in a one of the user interviews where a program organizer would like to keep track of which participants are working on which wikis.
I would however split that into a separate task if we decide to go with it.