# How Discourse Uses Discourse

**URL:** https://meta.discourse.org/t/how-discourse-uses-discourse/387597
**Category:** Blog
**Created:** [November 4, 2025, 7:03pm UTC](https://meta.discourse.org/t/how-discourse-uses-discourse/387597 "2025-11-04T19:03:34Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [December 4, 2025, 6:19pm UTC](https://meta.discourse.org/t/how-discourse-uses-discourse/387597/5 "2025-12-04T18:19:48Z")

</div>

Thank you @blake for this very welcome update on Discourse’s internal use!

Like for @HAWK’s post seven years ago, I translated it so French readers can also learn from your experience:

> **[Comment l'équipe de Discourse utilise-t-elle Discourse (sept ans après)](https://ps.zoethical.org/pub/comment-lequipe-de-discourse-utilise-t-elle-discourse-sept-ans-apres)**
>
> Sept ans après « Comment l'équipe de Discourse utilise-t-elle Discourse? », Blake Erickson a publié le 4 novembre 2025 une mise à jour dont voici la traduction… L’un des meilleurs aspects du travail chez Discourse est que nous pratiquons ce que...

There are some similarities with how we use Discourse at _petites singularités_ but you seem to use [@staff](https://meta.discourse.org/groups/staff) a lot more. In our case, we have few people with access to #staff but more categories with group moderation.

I was surprised to read about the incident response: does that mean you actually open at least three topics for the same incident? It seems to follow the Product/Todo split though.

A follow-up question maybe. Since you’re hosting quite a lot of free software project forums, do you ever share _runbooks_ with them, or get inspired by some of them?

---

_[View the full topic](https://meta.discourse.org/t/how-discourse-uses-discourse/387597)._