Discourse need a fork to be a Q&A software?

סיכום מבוסס בינה מלאכותית

The discussion revolves around whether Discourse needs to be forked to become a proper Q&A platform. krauss argues that Discourse isn’t inherently a Q&A software, citing the absence of Discourse-based sites in Q&A software comparisons and the lack of a robust voting system for topics and answers. They advocate for a feature-rich plugin or module to replicate the functionality of platforms like Stack Overflow or AskBot. awesomerobot counters that Discourse’s core design prioritizes conversation over Q&A, making a fundamental shift unlikely. However, Bas shares a successful example of using Discourse as a Q&A platform for a closed community, highlighting its suitability for niche knowledge sharing. Mittineague suggests that Discourse could host multiple apps, including a Q&A app, similar to integrating with WordPress. Falco points to existing Q&A platforms, while BIBI and Chaboi_3000 engage with Bas’s example and the limitations of current plugins. krauss reiterates the need for a better solution, referencing a specific community’s requirements.

Discourse, in nowadays, is not a Q&A software.
Rationale: there are some well-known Question-and-Answer softwares (Q&A), like AskBot, but Discourse is not figured there. And a lot of black-box interfaces, as Stackoverflow or Quora, that can be classified as Q&A sites, but we not see any Discouse-site figured there… Even a site using Discourse with some plugin or some alternative module.

We (example) need not a topic-blog, but to vote the topics and the answer-posts, and we need a good interface to it, and a good database / back-end to it… Not a “secondary like-vote” or a fake feature… But “near to clone” interface, like AskBot/Stackoverflow.

And there are a big market demand (!)… So, why the resistance to build a good module or plugin for it? There are some legal impediment (Jeff vs Stackoverflow competition)?

2 לייקים

I think you kind of answered your own question… The biggest impediment to making Discourse Q&A software is that Discourse isn’t Q&A software.

If making Discourse a good Q&A platform would mean changing the underlying structure that makes Discourse a good conversation platform… then it’s not likely to happen. It’s just incongruent with what Discourse is meant to do at that point.

I don’t think anyone’s opposed to improving the existing Solved or Voting plugins. Are there specific things you’d need for those to work better for you?

19 לייקים

Please note that I am (quite successfully if I say so myself) using Discourse as a Q&A platform.
I think many others are doing this as well. It isn’t as focused on competing answers as SO, but it’s perfect for niche topics, where an organisation can share its knowledge and have discussions with their customer base.

8 לייקים

I’m wondering why a “site” could not have varied apps running under it. AFAIK, many Discourse forums integrate with WordPress. I see no reason why the same couldn’t happen with a QA (or wiki, or video streaming, or whatever) app. Just because something hasn’t been done yet doesn’t mean it can’t be done.

2 לייקים

There are plenty in this space:

5 לייקים

Hi Bas could you share a link to your Q&A site? thanks!

לייק 1

Afraid it’s a closed community :frowning:

Bas

Don’t suppose you could share a screenshot?

Hi,

Here you go! Though I’m not sure this will actually help :slight_smile:

Here’s our (heavily) modified homepage :slight_smile:

The forum-part of the community is styled, but pretty much out of the box.

Three main categories:
Help - For people asking for help with our software
Trails - For people to ask for help with one of our tutorials
Feedback - If something could be better

All categories have an employees-only subcategory for employees to post sensitive questions.

Search is based on Algolia, this will index forum posts as well as our documentation and tutorials.

14 לייקים

Technically you can use the solved plugin to make it like a Q/A, but discourse isn’t made to be just a Q/A software.

2 לייקים

Hi @Bas , seems very good what you show above, and perhaps it is better and stable in nowadays (2 years after 2019)…

Can you help OpenStreetMap community?
See Migrate help.openstreetmap.org from OSQA to static html archive · Issue #149 · openstreetmap/operations · GitHub

לייק 1