# 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:** [08.Июль.2016 21:19:08 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:** 1
**Showing post:** 3

<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: [11.Июль.2016 16:42:18 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:

---

_[View the full topic](https://meta.discourse.org/t/how-would-you-design-a-statistics-index-page-for-the-backend/47016)._