The developer community stack
Where should a developer community live, and what keeps it alive?
Choosing a chat platform is the smallest of these decisions and the only one most teams make deliberately. Six more: where answers go to be found again, how you hear the conversations happening off your turf, and how you tell whether anyone is actually showing up.
By Fabian HugUpdated
7 decisions · 16 tools
01 · Decision
Pick the room
Real-time chat is where a community feels alive and where knowledge goes to die - messages scroll away and search is an afterthought. Pick on where your developers already are rather than on features: Discord if they came from open source or gaming-adjacent tooling, Slack if they are at work and their employer already pays for it, Zulip if threading matters more than vibe and you want to host it yourself.
02 · Decision
Give answers a permanent home
The step teams skip, then spend two years regretting. A forum is where a good answer stays findable a year later, by someone who never joins your chat. If your project already lives on GitHub, Discussions is the version of this decision with no new account and no new moderation surface - which is often the version that actually survives.
03 · Decision
Make what you already answered findable
If the room is Discord and the answers are staying there, this indexes support threads so they show up in search results instead of being re-answered every week. It is a direct patch for the failure mode in step one, and it is worth installing before the archive gets big rather than after.
04 · Decision
Hear the conversations you were not invited to
Most of what gets said about a developer tool is said somewhere you do not control: a Reddit thread, a Hacker News comment, someone's issue tracker. Alerting on your own name is the cheapest signal in this entire list, and the one that most often surfaces a problem while it is still small.
05 · Decision
Know who is actually showing up
Member counts measure signups, not community. These stitch together the same person across chat, GitHub, and events so you can see who keeps returning and who answered someone else's question. Worth it once you have more activity than one person can hold in their head, and overhead before that.
06 · Decision
Run the recurring moment
A community with nothing on the calendar is a support channel. Something regular and small - office hours, a monthly call - does more than an annual conference, and the tooling only needs to handle a page, a date, and a reminder.
07 · Decision
Borrow from people doing this full time
Community work is unusually lonely inside a company, because nobody else in the building does your job. These are where the practitioners compare notes on the parts nobody writes down: moderation calls, burnout, what to do when the room goes quiet.
How to read this
These are shortlists, not rankings. Every tool named here has its own directory entry with the facts it publishes and the date they were checked, and the order within a step is the order it was written in, not a verdict about which is better. We do not run these tools in production and we take no money for inclusion. Where a step has two options that genuinely suit different situations, it says which is which instead of picking one.
Hiring for this work
11 open roles match the community roles filter on the board right now.
Upcoming events on these topics