# How would you design a "Statistics" index page for the backend?

**URL:** https://meta.discourse.org/t/how-would-you-design-a-statistics-index-page-for-the-backend/47016
**Category:** UX
**Created:** [Juillet 8, 2016, 9:19 UTC](https://meta.discourse.org/t/how-would-you-design-a-statistics-index-page-for-the-backend/47016 "2016-07-08T21:19:08Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [Juillet 8, 2016, 9:19 UTC](https://meta.discourse.org/t/how-would-you-design-a-statistics-index-page-for-the-backend/47016/1 "2016-07-08T21:19:08Z")

</div>

This is not a sure thing yet, but I sure would love it if Discourse had a dedicated /admin/statistics page on the backend, rich with interesting community insights, visualised for my viewing pleasure.

Maybe this will come more naturally once we’ve nailed down [the stats we’ll be focusing on for the RGSoC 2016](https://meta.discourse.org/t/rgsoc-2016-visual-forum-analytics-community-discussion/46905), but if someone has some ideas for this already I’d love to hear’em.

**Here are some statistics pages from other web apps for inspiration:**

 ![](https://global.discourse-cdn.com/meta/original/3X/b/a/ba2fedf8082fd4c81a49d0a3ddb19b144f94ccfb.jpg)

* * *

 ![](https://global.discourse-cdn.com/meta/original/3X/a/e/aea1732b2e85544300e9a7bbc4f48806d2ad9a0d.jpg)

* * *

 ![](https://global.discourse-cdn.com/meta/original/3X/f/6/f6dadc83794ffdff94b84cb780354b705001d483.jpg)

* * *

 ![](https://global.discourse-cdn.com/meta/original/3X/1/3/13460d548b4e29ca76ea1cc85e22f1a90fffccd5.jpg)

* * *

 ![](https://global.discourse-cdn.com/meta/original/3X/7/4/74dbd8001881496d4dd27fd34507f74fac8a6b1e.jpg)

* * *

 ![](https://global.discourse-cdn.com/meta/original/3X/6/0/60ed4a4574f9291486b6f5f83968d9cba7ff550c.jpg)

* * *

 ![](https://global.discourse-cdn.com/meta/original/3X/5/1/5113651f18fa59cd7fe520140a7f18e0f40825b7.png)

* * *

 ![](https://global.discourse-cdn.com/meta/original/3X/5/c/5ce0135e46dafdece7f74af9587cca9b906d0c7d.jpg)

📯 @awesomerobot, @rewphus, @commonpawn, @DiscourseMetrics.com, @HAWK

---

<div class="post-metadata">

### Author: ![commonpawn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/commonpawn/32/50792_2.png) [@commonpawn](https://meta.discourse.org/u/commonpawn)
#### Post date: [Juillet 11, 2016, 4:11 UTC](https://meta.discourse.org/t/how-would-you-design-a-statistics-index-page-for-the-backend/47016/2 "2016-07-11T16:11:14Z")

</div>

Like you’re saying, it really comes down to what data has to be displayed and what you’re trying to achieve with this dashboard. I think that would be a great place to start

In terms of dashboards in general, there is also room for improvement. A lot of the critique of dashboards as we know them, is based on the fact that they simply display data - not insights. Eg. Fitbit tells you how much you move but does not really tell you how to improve your fitness - you will have to figure that out yourself from reading the data.

What if discourse could have a smarter, dynamic dashboard that not only displays a lot of useful data, but serves you relevant insights on how to improve your community

---

<div class="post-metadata">

### Author: ![mcwumbly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcwumbly/32/103861_2.png) [@mcwumbly](https://meta.discourse.org/u/mcwumbly)
#### Post date: [Juillet 11, 2016, 4:42 UTC](https://meta.discourse.org/t/how-would-you-design-a-statistics-index-page-for-the-backend/47016/3 "2016-07-11T16:42:18Z")

</div>

Agreed. I was trying to make a similar point here:

> [@RGSoC 2016: Visual Forum Analytics Community Discussion](https://meta.discourse.org/t/rgsoc-2016-visual-forum-analytics-community-discussion/46905/9):
>
> When deciding which things to add first, I think it’d be healthy to frame the question in these terms: Along those lines, one feature to consider adding is a tooltip or explanation that attempts to give some guidance about what a given metric might mean under what scenarios it might be expected to be misleading. There may be some hints about what kind of data is “missing” in this topic too:

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [Mai 19, 2018, 5:56 UTC](https://meta.discourse.org/t/how-would-you-design-a-statistics-index-page-for-the-backend/47016/4 "2018-05-19T05:56:35Z")

</div>

> [@Help us build the new 2.0 Dashboard](https://meta.discourse.org/t/help-us-build-the-new-dashboard/86468):
>
> We have redesigned our admin dashboard at /admin In the next days I will be finishing this and moving towards a v1 which will be in the next Discourse release. Please refrain yourself to write a long bug report for a few more days, I will post it when I think “it’s done”, but do try it and please give us an early feedback on what you can try and this mockup. I’m very excited to finish this and give you this new dashboard. One of my personal goals with this revamped dashboa…
