Is anyone working on a Discourse Wiki?

Buy an enterprise hosting contract is the main way to move forward. None of our customers are asking for this. Not opposed to it but we have other priorities based on our paying customers at the moment.

4 个赞

This one has been spec’d out and currently has a “bounty”:

3 个赞

If you want to split the requests, that probably could be done through another feature:

Topic templates commands. So we could issue a command to turn it into wiki. Not sure if this have been considered yet, or why not. If it haven’t, I’m probably posting this in the wrong place… :stuck_out_tongue:

1 个赞

Just to throw in my 2 cents. I love Discourse, and a Wiki option would be AWESOME! I too feel like most wiki software is stuck in 2005 or earlier.

1 个赞

To be clear “Wiki” functionality exists:

Perhaps it’s not an exact replacement for Wikipedia’s MediaWiki - but the base functionality to a large degree exists and works.

6 个赞

It’s a solid foundation that could be much improved with a little bit of work:

In a “wiki category” :

  • All new topics are wikified by default
  • Author attribution is suppressed
  • Always go to first post when viewing a topic
    (option to hide replies on separate page)

And made into a “proper” wiki with some more detailed and involved work:

  • Table of contents generation with [contents] object and headers
  • Create links to other topics by “tagging” them ie. &PageTitle
  • Create new topics by tagging a non-existant page eg. &NewTopic
9 个赞

I happened to be looking at this today in another context. While it’s a little convoluted, it is actually possible to pass non-default parameters (such as wiki) to new posts. It took me a little while to figure this out, so someone else may find it useful. There are four things you need to do:

  1. Set wiki to true when creating the post record in the store.
  2. Add wiki to the serialized composer properties via Composer.serializeOnCreate.
  3. Use PostRevisor.track_topic_field(:wiki) to add wiki as a permitted param in the posts_controller.
  4. Save the wiki opt to the Post using the post_created event.
6 个赞

I’ve been trying to decide which official Wiki to create a plugin with MediaWiki Classic of the new FederatedWiki.

Thank you so much for posting your experience.

Wiki pages on a forum are a great idea, kudos to Discourse. The revisions system works well. The editor is great.

But there’s a massive gap in functionality from my PoV.

If two people edit concurrently, one person’s work is lost

We’ve not had much use of the wiki feature on my forum (1000 visits/day) but we’ve already seen multiple edit clashes.

Suggested solutions in order of preference (preferred first):

  1. Live collaboration (show where the editors’ cursors are, as per google docs).
  2. Lock a post to other editors when it’s being edited
  3. Allow conflicts to be merged by the last editor.
3 个赞

I haven’t tested this locally, but are both revisions available in the edit history modal?

(BTW you posted an incomplete URL to the example of the problem)

2 个赞

I believe both revisions are there in the history, yes. The link is just to the forum. The conflicts were in our private staff area. The issue is easily reproducible.

Yes, both are visible – but the second person to make the edit usually won’t notice that they reverted the previous person’s changes. :frowning:

2 个赞

I’ve not tried this myself, but I think the Pages theme for Grav (a flat file CMS) could serve as a wiki. Additionally, Grav has support for Discourse comments via the JS Comments plugin.

The official Grav docs use the same theme.

1 个赞

这个讨论已经有好几年了,但我在意识到将论坛组织成维基(wiki)形式会非常酷之后,偶然发现了它。@peternlewis 很好地表达了我心中的想法。这不仅仅是允许在单个帖子中使用维基功能,而是让我的 Discourse 网站像一个维基百科那样的维基。正如他所说:

Discourse 能否实现这一点?

1 个赞

是这个吗?https://meta.discourse.org/knowledge-explorer

4 个赞

您可以在任何计划上安装 DiscoTOC - automatic table of contents

您可以使用 Codepen 或 https://repl.it/ 嵌入可运行的代码。

3 个赞

谢谢。

更具体地说,我认为我们使用的是开源套餐之一,很可能是这一款:Free Hosting for Open Source v2

作为管理员,我检查了是否可以安装 DiscoTOC,但它不在可用插件列表中。:slightly_frowning_face:


谢谢,但遗憾的是,我们是 Prolog 程序员,具体来说是 SWI-PrologDiscourse 论坛)。虽然 CodePen 提供了一些运行 Prolog 的能力,但远不如真正的 Prolog 功能强大,而且由于并非专门针对 SWI-Prolog,因此并未被采用。SWI-Prolog 确实有一个在线工具叫 SWISH,但出于安全考虑,它的功能受到限制,无法实现 Prolog 的全部能力;如果您了解 LISP 因 同像性 而能实现的功能,就能明白这一点。我曾尝试将 SWISH 与 Iframe 集成,并尝试了其他一些方案,但都无法按预期工作;虽然最终实现了一个可用的版本,但并不实用,据我所知,问题出在屏幕宽度上。

再次感谢你们的反馈,我们非常感激。

它是一个 主题组件

2 个赞

你当时指的是什么?

DiscoTOC 是一个主题组件,而不是插件。请按照如何安装主题或主题组件?的说明进行安装,它肯定对您可用,不妨试试看。

哦,我明白了。

我认为尝试运行一个可工作的 Prolog repl.it 实例可能是最好的选择,即使它是基于 编译为 WASM 的 SWI-Prolog。可以尝试联系 repl.it 的创始人 @Amjad_Masad

5 个赞