In this article
A project that has grown into a channel, a discussion group, a support room and two bots occupies five lines of everybody's chat list. A community gathers them under one entry that opens into a directory — one thing to find, one link to share.
It is an organising layer rather than a new kind of room, and knowing that is what stops people expecting the wrong things from it.
What you will be able to do
- check_circle Gather related chats under one entry.
- check_circle Tell it apart from topics and from folders.
- check_circle Decide which rooms a newcomer should see.
- check_circle Avoid building more rooms than you can fill.
One entry that expands — the rooms inside are the same rooms they always were.
account_tree A directory, not a container
The most useful thing to understand is what does not change. Each chat inside keeps its own members, its own permissions, its own history and its own notification settings. Joining the community is not joining everything in it, and being an administrator of one room is not being an administrator of the others.
What changes is discovery and tidiness. A newcomer arriving at one link can see what exists and choose what to join, instead of being handed four separate invitations by somebody who has to remember all of them. And a member who has joined five of your rooms gets one line in their chat list rather than five.
Both of those matter more than they sound. The usual way a multi-room community loses people is not disagreement — it is a person who joined the main channel, never learned the discussion group existed, and concluded the project was quiet.
Four ways to organise a growing community
They look interchangeable and they solve different problems.
| What it is for | Who it helps | What it does not do | |
|---|---|---|---|
| Topics in one group | Splitting conversation inside a single room so people can ignore parts of it. | Members, who get to follow one thread and mute the others. | It is still one group: one set of members, one set of permissions, one moderation problem. |
| A channel plus a discussion group | Separating announcements from conversation — the standard shape for anything with an audience. | Everybody. Readers can take the channel alone and skip the talking. | It does not scale past two rooms, and the discussion group is a full community to run on its own. |
| A community | Several genuinely separate rooms that belong to one project, presented as one place. | Newcomers, who can see what exists, and members, who get one chat list entry. | It changes nothing about the rooms themselves — same permissions, same moderation, same work. |
| A shared folder | Handing somebody a set of chats to join in one action, without a shared identity. | Anybody assembling a bundle, including across projects they do not run. | It is a list rather than a place, with no front page and nothing for a stranger to arrive at. |
Use topics until the conversations need different members. A community is for when the rooms are genuinely separate.
group_add The failure is always empty rooms
Given a structure for several chats, people build several chats. A new community with a general room, a support room, an off-topic room, a regional room and an announcements channel has five places for the twelve people currently talking, and all five look abandoned.
Conversation does not divide well. Split a room that was busy and you get two quiet ones, and quiet rooms are self-reinforcing — nobody posts into silence. The rule that holds up is to add a room when an existing one is actively being disrupted by a conversation that does not belong in it, and not before.
Which makes the honest starting shape small: a channel, one discussion room, and nothing else. The directory is worth having at that size anyway, because it is the thing you grow into rather than something you have to migrate to later.
near_me Make the front page answer one question
Somebody opening the directory for the first time wants to know where to go. That is the only job the listing has, and it is done by the order and the naming rather than by completeness.
Put the room a newcomer should read first at the top, name each one for what happens in it rather than for what it is called internally, and keep the descriptions to a line. A directory listing nine rooms with clever names is a menu nobody can order from.
And revisit it. Communities accumulate rooms from projects that finished, and a listing full of places where the last message was in spring tells a visitor more about the state of the project than anything in the description does.
settings Setting one up
- Start with the rooms you already have Not the ones you imagine.
- Hide what newcomers should not see Listing is a choice.
- Order it for a first-time visitor Most important first.
- Name rooms for what happens in them One line each.
- Add a room only when one is being disrupted Splitting makes two quiet rooms.
- Share one link everywhere And retire the list of invitations.
This page gives a project a front page. The curriculum step is the simpler mechanism behind the same idea: handing somebody several chats in one action, and what that link keeps doing after they have used it.
At a glance
- 1Communities
Gather related groups and channels under one entry.
- 2A directory
Each room keeps its own members and rules.
- 3Avoid empty rooms
Add a room only when one is really needed.
Updated
