Skip to content

Handbook: Add Administration docs for Discourse forum platform

Michael Friedrich requested to merge community-relations-forum-admin-docs into master

Why is this change being made?

The Discourse instance on forum.gitlab.com was not documented in detail, leading to questions from team members and customers. In tech_stack.yml, we link to https://about.gitlab.com/handbook/marketing/community-relations/community-operations/workflows/forum/#administration

This MR adds a new section Discourse platform to the handbook documentation, detailing all technical details like SaaS hosting, and also provides an overview of all Discourse settings, plugins, users, groups, etc.

Helps address

Customer is interested in setting up their own internal community hub. They find discourse as a community engagement tool quite interesting and would have a few questions. For now they are mainly administrative, i.e. what server do we have this running on, how much traffic are we seeing.

@greg Please review in-depth, I think I got everything addressed from the past 2+ years. @sugaroverflow Please review high level to get familiar with the different aspects of Discourse.

cc @johncoghlan @mbruemmer

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this change to the correct DRI(s)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports