Using Discourse as a internal Knowledge Base / Intranet

We would love to!!
I don’t know if it’s possible due to having a self-hosted instance (non customers), but our story with Discourse is so interesting that we publish it in a book about our culture and management (we can send to the :discourse: team a free printed copy if you want but it’s written in spanish - it was published in january’15):

Translation:

[…] After a full year of time invested in a own development to make a Drupal adaptation to run as our internal social network, DavidGNavas insisted on proving that we should evolve to a recent-creation GPL software called Discourse. Hours of research led him to understand…

/nextpage/

…the advantages, features and how fast was the related community growing, so, after a test on a dedicated server, he showed that he was right. We decided to cut off the budget invested on Drupal and, overall, the emotional link with a project that we had been working for a year. […]

:book:

  • Mentioned here on meta: better support for making groups of wiki authors. Nowadays you can set permissions for a category but it you make a post wiki-style, you get permissions based on trust-level. A good idea would be a mix: group of allowed authors that can edit a wiki post.

  • Perhaps an avatar list of who have contributed to the wiki topic.

Various ideas from @sam in potencial plugins topic:

  • An integration with a to-do app or an own to-do list.
  • The reactions plugin. We have several topics about “who comes to a lunch with foo…?”

pd. we don’t have trouble with javascript/Android because our organization provide us an iPhone while we work here :smile:

13 Likes