# Plugin: Monthly automated community report

**URL:** https://meta.discourse.org/t/plugin-monthly-automated-community-report/60742
**Category:** Feature
**Tags:** feedback
**Created:** [Avril 10, 2017, 9:02 UTC](https://meta.discourse.org/t/plugin-monthly-automated-community-report/60742 "2017-04-10T21:02:14Z")
**Posts on this page:** 7
**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: [Avril 10, 2017, 9:02 UTC](https://meta.discourse.org/t/plugin-monthly-automated-community-report/60742/1 "2017-04-10T21:02:15Z")

</div>

What if every month, we could all be reminded of what we did as a community over the last 30 days. ❣

This type of content has historically been curated manually by community managers:

- [Monthly update on Flarum](https://discuss.flarum.org/d/5132-community-update-march-2017)
- [Yearly update for Discourse](https://blog.discourse.org/2016/01/a-year-in-discourse-recap-of-2015/)
- [A curated weekly newsletter for your community](https://meta.discourse.org/t/a-curated-weekly-newsletter-for-your-community/76668)

 ![](https://global.discourse-cdn.com/meta/original/3X/c/8/c8e39b3134eb40a1f7aae6c29792fbc226f9596b.jpg)  
 ![](https://global.discourse-cdn.com/meta/original/3X/3/b/3b914dcbe4a29bffa0e0296616beeb41eaf7ba8a.jpeg)

I wanted to do one of these for the year 2016, but other tasks kept climbing higher up on the priority ladder. Besides, it’s pretty tedious, unrewarding work, since \>90% of it can be automated. So today I had a wee think about what such an automated report might look like:

### Basic stats

- How many topics & posts were created?
- How many different people participated in conversations?
- How many new users signed up?
- Were categories created/destroyed/changed?

🗒 I don’t think a comparison to last month would be necessary. The fact that we posted 10 more/fewer topics this month doesn’t really mean anything, but users might inclined to add meaning to it regardless, and we wouldn’t want that.

### Content highlights

- New articles added to #howto this month
- Most liked replies in #Support

### Top snapshot

🗒 Maybe it could be fun to treat this almost like a time capsule. No need to feature individual topics. Just do this:

As of today, {date}, these are the Top 10 topics you’ll find in `/top/monthly`:

- Displaying sub-categories in boxes
- Telegram Notifications Plugin
- Weekly or monthly “best new user” badge
- (…)

### Badge highlights

- “Helpdesk” was awarded to: Tom, Julia, Hannah (…)
- [“Best new user”](https://meta.discourse.org/t/weekly-or-monthly-best-new-user-badge/60065) was awarded to (…)
- “Contributor” was awarded to (…)

🗒 This section was my primary motivation for finally suggesting such a automated report. When we’ve awarded something like [Helpdesk](https://meta.discourse.org/badges/125/helpdesk), [Bug Reporter](https://meta.discourse.org/badges/114/bug-reporter) or [Contributor](https://meta.discourse.org/badges/107/contributor) to one of our members, I want to know about it. And those members deserve some extra recognition for it. This report could act as that extra bit of applause for those members who’ve gained a badge that requires a considerable bit of time and effort.

* * *

Clearly there’s some overlap here with the [admin stats report](https://meta.discourse.org/t/admin-statistics-report/50943), but quite a few things need to change when we post stats publicly. The key difference is that we don’t want to do a lot of “rankings” in a public stats report. Again, this is because we don’t want to risk having users misunderstand the stats as a leaderboard. It’s not about that.

---

<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: [Avril 10, 2017, 9:32 UTC](https://meta.discourse.org/t/plugin-monthly-automated-community-report/60742/2 "2017-04-10T21:32:29Z")

</div>

Sure! I would love to see this morph into a selling tool for our communities as in

> LOOK how awesome your Discourse community is and all the COOL stuff it produced!

With the implied

> … doesn’t that make you super glad you pay us $100 or $200 a month to host it?!

That we could use it on our _own_ hosted communities is merely a bonus 😉

---

<div class="post-metadata">

### Author: ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [Avril 11, 2017, 8:02 UTC](https://meta.discourse.org/t/plugin-monthly-automated-community-report/60742/3 "2017-04-11T08:02:57Z")

</div>

> [@erlend\_sh](#):
>
> nous ne voulons pas risquer que les utilisateurs interprètent mal les statistiques

Dans cette optique (mais aussi pour d’autres raisons évidentes), il serait idéal de concevoir le plugin de manière à permettre aux administrateurs d’ajouter du texte sous chaque (?) élément du rapport, essentiellement pour faciliter la production de quelque chose comme [bilan annuel pour Discourse](https://blog.discourse.org/2016/01/a-year-in-discourse-recap-of-2015/). Mais il doit bien sûr fonctionner aussi en mode entièrement automatique.

> [@erlend\_sh](#):
>
> Points forts du contenu

Sans oublier : le sujet le plus aimé dans #Community Building > Praise 😉

---

<div class="post-metadata">

### Author: ![alefattorini](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alefattorini/32/119928_2.png) [@alefattorini](https://meta.discourse.org/u/alefattorini)
#### Post date: [Avril 11, 2017, 9:16 UTC](https://meta.discourse.org/t/plugin-monthly-automated-community-report/60742/4 "2017-04-11T09:16:57Z")

</div>

Love that, it would be super useful. Let us customize it with extra text and it’s ok for me.

---

<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: [Décembre 29, 2018, 3:36 UTC](https://meta.discourse.org/t/plugin-monthly-automated-community-report/60742/5 "2018-12-29T03:36:28Z")

</div>

Note that @simon has been cooking up something along these lines as a “year in review” fun stats report, and will have more to show soon. 🥳

---

<div class="post-metadata">

### Author: ![Andy02](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andy02/32/119498_2.png) [@Andy02](https://meta.discourse.org/u/Andy02)
#### Post date: [Mars 25, 2019, 11:43 UTC](https://meta.discourse.org/t/plugin-monthly-automated-community-report/60742/6 "2019-03-25T23:43:58Z")

</div>

posting so i can keep an eye on that new feature coming out 🙂

---

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [Mars 26, 2019, 12:00 UTC](https://meta.discourse.org/t/plugin-monthly-automated-community-report/60742/7 "2019-03-26T00:00:54Z")

</div>

We have a [Discourse Yearly Review](https://meta.discourse.org/t/discourse-yearly-review-plugin/105713) that could be used as the basis of a new plugin for creating a monthly report.
