Thanks, @jaevanryssel. This definitely helps a bit. We use Slack too and so there has been some discussion on when Slack is appropriate vs Discourse.
funny that this thread is being reawakened now. I am working on this right now - we use discourse as a community forum and for internal staff discussions. I’d like to reconfigure things so it’s optimal for both, but it’s been a bit of a challenge. For example internal discussions swamp the frontpage for staff so sometimes it’s hard for them to see and deal with community discussions. For today I am trying out the “hide category from frontpage” setting and adding a link to that category on the top menu, visible only to staff.
I also am looking to create a wiki category with sub-categories, to contain operating procedures and how-to docs for staff. This is working well, especially with the “boxes with topics” category view - like the howto category here - see screenshot. I like! I think it will be a big improvement over the google docs we were using previously for this purpose. Especially when considering that it can respect permissions and show people only the sub-category of procedures that they need to see according to their role.
Up next, I think, is to figure out a way to present the wiki topics in a structured interface externally, so it can be used without the distraction of discourse discussion features, safely also when discourse is down, and also perhaps even offline saved as structured PDFs.
The learndiscourse experiment might be a help for this - and if anyone has done it recently with success and has a recipe for it I’d love to see it! Sadly, learndiscourse.org is not working right now.
https://github.com/erlend-sh/learndiscourse/blob/gh-pages/about.md
7 个赞
This is great! I’m also thinking about using discourse as a KB. Only issue I’m seeing so far is localization, seems like that would be a bit more painful than the solution we have now.
There isn’t really a way to have a single topic localized is there?
1 个赞
The same topic translated into multiple languages? Not really, no. Once you get to that kind of upscale requirement I think it’s time to transition to a specialized docs platform. Using something like https://www.gatsbyjs.org you could continue using Discourse as the data source for your English content, whilst translating the rest in Transifex.
3 个赞
Wiki vs. Bulletin: I am not completely sold on idea to have bulletin system for Knowledge Management. Generally speaking, if everyone is familiar common location in a hierarchy, it is easy to reference something. Searching, you may not recall the exact word or key word needed, but you’ll know the location. I look toward analogy of having an index vs. sleuthing through lot of information to extract the exact information you need.
Confluence wiki vs. Other Wiki: I am open to using an alternative code-friendly wiki, maybe something that can be integrate changes that occur with code, so that it is refreshed, e.g. https://www.mkdocs.org/.
我偶然发现了这个帖子，因为我也在为公司寻找一个好的知识库/维基解决方案。
我注意到 Discourse 有这样的设置，我很喜欢。
这是否开箱即用即可轻松配置？我喜欢这种简洁的外观以及通过分类和标签进行的组织方式。
编辑：我还在想是否还有以下几项其他功能可用：
- 带回滚的版本控制
- 针对特定项目的审批/拉取请求式工作流
2 个赞
你好，Jordan！是的，可以通过官方插件启用该功能：https://meta.discourse.org/t/knowledge-explorer-plugin/130172。
主题就是普通的 Discourse 主题，提供版本控制。关于拉取请求类型的流水线，我不太确定——你能详细说明一下吗？
3 个赞
@tobiaseigen 完美！非常感谢。我会进一步研究。
关于审批/拉取请求类型的场景，我尝试在下面更清晰地阐述一下想法：
我举拉取请求为例，因为我认为它非常适合软件开发，并且也可以（正如我想象在某些类似 Gollum 的 Wiki 软件中那样）作为控制某些知识库文章更新的一种方式。需要说明的是，这实际上可以是任何类型的审批工作流，我只是用拉取请求作为一个熟悉的例子。
例如：某人拥有该文章，对该文章的任何更新都需要作为拉取请求（或类似方式）提交以供审查和批准。
这样解释清楚吗？
这已内置于 Discourse 核心版本的编辑历史中。
您可以设置让特定分类下的新主题需要版主审批。核心版本中暂无此功能，但已有相关的功能请求。
不过，这并非针对主题创建者，只有工作人员才能审批帖子。
2 个赞
您好，
我供职于一家大型全球保险公司，目前负责设计一个内部知识库，用于汇总围绕各类主题积累的知识。我想咨询一下，Discourse 平台是否能够与 Microsoft Office 产品进行同步？例如，在我们公司，我们使用 Microsoft Office（Outlook 用于邮件，SharePoint 用于文件存储等）。Discourse 论坛能否以某种方式与 Microsoft Office 集成，以便组织内的用户能够访问它？
如果上述问题的答案是肯定的，那么是否有具备为组织（通过内网系统）开发 Discourse 平台经验的开发者可供聘请？
提前感谢。
您的意思是将 Discourse 配置为将登录委托给 Microsoft 365 吗？
我们企业版托管计划提供此类集成服务。请访问 Discourse Enterprise | Discourse - Civilized Discussion 了解详情，并联系我们提供具体信息。
3 个赞
感谢您的回复。我已通过电子邮件私下联系您的团队，提出了我的请求：slight_smile
这是一个很好的讨论。也许这里有人能帮我。我正尝试在公司内部使用 Discourse，既用于用户生成内容（论坛），也作为内部知识库。
我喜欢 @tobiaseigen 在 2018 年 1 月分享的界面，这正是我想要的。但是，我能否进行编辑控制？例如，我希望指定文章的顺序以呈现特定的叙事逻辑。另外，我不确定该视图是否仅支持显示前 3 篇文章，还是能支持更多内容。有人能帮忙吗？
我也面临用户询问如何在 Discourse 中共享文档的问题。
我没有找到任何官方插件允许这样做。
但这个插件似乎启动了一些有趣的东西：Discourse OneDrive Picker
如果能将文件共享解决方案集成到 Discourse 中就好了 