Originally published at: Discourse for Private Communities
There are many reasons why a community might be private: Paid memberships; a company intranet; a sensitive subject matter; beta testers; a grassroots movement building momentum before going public. Whatever the reason, we want Discourse to function well in private contexts. We reached out to 23 private Discourse communities to learn more about their use…
AI-generated summary
The Discourse team reached out to 23 private Discourse communities to learn about their use cases, with 10 responding with valuable insights. Private communities use Discourse for various purposes, including sharing knowledge, solving problems, and discussing sensitive topics. Respondents praised Discourse for its ability to facilitate discussions across geographical and organizational boundaries.
Some notable use cases include:
- Avi Flax from Park Assist uses Discourse to move discussions away from email and chat, improving knowledge sharing and problem-solving.
- Jake Shadle from Frostbite prefers Discourse over mailing lists for certain types of communication.
- David García from GoodRebels uses Discourse as a space for coworkers to discuss methodology, philosophy, and strategy.
The top favorite things about Discourse among respondents include:
- Access to data on successful communities and case studies.
- Customizable profile fields and social media links.
Mcwumbly suggests that integrating Discourse with other private systems, such as Slack and Google Docs, would be beneficial for private communities. This includes the ability to Onebox links to private Slack instances and access private Google Docs.
17개의 좋아요
An opportunity I see for making Discourse continue to improve for private communities (particularly company intranet sites), is to have more integrations with other private systems
The slackdoor plugin gives Slack some ability to unfurl links to private discourse instances, but going the other way would be cool too (i.e., having the ability to Onebox links to private Slack instances).
Same goes for things like Google Docs. The current solution is better than it used to be, but it’d be great if Discourse could be configured to have the necessary authorization to actually fetch and onebox private docs.
These are just a couple examples that come to mind - I imagine each private instance would have their own thoughts on what integrations like this would be valuable.
6개의 좋아요