Skip to content

Docs & courses

What is a good comment system for an online course or a product documentation site?

Lesson pages and docs pages have the same job for comments: let the people reading them ask a question right where they got stuck, and let your team answer it once for everyone who comes after. Here is what to look for, how the common options compare, and when EchoThread is the wrong pick.

Short answer

A good comment system for an online course or a product documentation site gives every lesson or docs page its own thread, lets readers comment without creating yet another account — ideally signed in with the account they already have on your course or docs platform — screens spam before it is published, and gives your instructors or support team a shared moderation queue. EchoThread does all four, with single sign-on on the Pro plan. If your docs are for developers who all have GitHub accounts and will paste code, Giscus is a strong free alternative.

Who EchoThread fits, and who should choose something else

A good fit

  • Online course creators who want questions under each lesson instead of in a separate forum.
  • Product and SaaS documentation where readers are customers, not developers with GitHub accounts.
  • Teams that want instructors or support staff to share one moderation queue.
  • Sites that cannot show ads or third-party trackers next to paid content.

Choose an alternative

  • Developer docs where every reader has a GitHub account and comments are mostly code: use Giscus.
  • Teams that must self-host and own the database outright: use Commento.
  • Courses that need graded assignments, quizzes or a full community forum: use your LMS or a forum tool.
  • Readers who need code blocks in comments: EchoThread supports bold, italic, strikethrough and spoilers only.

What to look for in a course or docs comment system

  1. 1

    One thread per lesson or docs page

    Questions belong next to the content they are about, and they must survive URL changes when you reorganise a course or ship a new docs version.

    In EchoThread: each page gets its own thread, keyed to a data-identifier you choose. See the docs.

  2. 2

    No second account for your readers

    Students already logged into your course and customers already logged into your app will not register again just to ask a question.

    In EchoThread: guest commenting or seven social logins on every plan, and single sign-on with your own accounts on Pro. See the docs.

  3. 3

    Spam screened before it is published

    Public docs pages rank in search, and that attracts link spam. A login wall stops spam but also stops most legitimate readers.

    In EchoThread: every guest comment is scored by a machine-learning classifier first, and uncertain ones wait in your queue. See the docs.

  4. 4

    A queue your whole team can work

    Instructors, teaching assistants and support engineers need to see new questions and answer them without sharing one login.

    In EchoThread: five team seats on every plan, a Moderator role on Pro, and approve-from-email plus Slack and Discord alerts from Starter. See the docs.

  5. 5

    Light enough for content pages

    Docs and lessons are read on slow connections and phones. The comment widget should not outweigh the page.

    In EchoThread: the widget is under 65 KB gzipped and loads no ads or trackers. See the docs.

EchoThread vs Disqus, Giscus, Commento and Hyvor Talk for docs and courses

Rows are the decisions that matter most for lesson and docs pages. How each cell was checked is under Methodology.

Comment systems compared for online courses and documentation sites
 EchoThreadDisqusGiscusCommentoHyvor Talk
Who can commentGuests, or Google, GitHub, X, Facebook, Discord, Bluesky, MastodonDisqus account; guests only if the owner enables itGitHub account onlyOAuth login (per its README)Optional sign-in
Sign in with your own course or docs accounts (SSO)Yes, on Pro ($19/mo)Business add-on, through salesNoListed in its READMEYes (Stateless SSO or OpenID Connect)
Where comments are storedHosted; export JSON or CSV any timeHosted; XML exportGitHub Discussions in your repoYour own server (self-hosted)Hosted; export available
Spam filterML classifier + your word listAkismetGitHub login wallManual / AkismetAkismet / add-on
Star ratings (e.g. rate a lesson)Yes, from Starter ($5/mo)On ProReactions onlyNot in its feature listPage ratings
Ads / trackingNeverYes, on the free tierNoNoNo
Widget sizeunder 65 KBHeavyweight~30 KB~11 KBHeavier, lazy-loaded
Free optionFree forever, 10K views/moFree, ad-supportedFree, open sourceFree to self-host14-day trial, then paid

Narrower head-to-heads: vs Disqus, vs Commento, vs Hyvor Talk, and the full alternatives lineup.

Proof

One queue for every lesson and docs page.

The EchoThread moderation queue, with tabs for pending, approved, rejected and spam comments and a threaded reply under an approved comment
The moderation queue: comments from every page on a site land here, sorted into pending, approved, rejected and spam. Click through the live demo.

Methodology

EchoThread's column comes from our pricing page and documentation, which describe the shipped product. The widget size is a ceiling, not an estimate: every build is checked against a under 65 KB gzipped budget, and a build that exceeds it fails.

Competitor cells come from each vendor's own public documentation, linked under Sources below and checked on October 11, 2026. Where a vendor's docs do not mention a capability, we say so rather than guess. Products change, so every cell is re-checked whenever this page is updated.

We do not yet publish customer case studies for course or documentation sites. Every claim here is something you can verify yourself in the docs or on the free plan, without talking to anyone.

Implementation notes

  1. Paste one snippet into your lesson or docs page template. Docusaurus, MkDocs, VitePress, Hugo, Astro and any other static generator work, because the widget is a single script tag with no framework dependency. See the quick start and the platform guides.
  2. Set a stable data-identifier per lesson or page. Docs and course URLs change when you rename a section or publish a new version. Key each thread to an ID that survives the move, such as a lesson ID or a docs path without the version, so the questions stay on the right page. See the snippet attributes.
  3. Decide who can comment. For a public docs site, guest commenting removes the login wall and the spam filter does the gatekeeping. For a paid course, connect single sign-on on Pro so only your enrolled students can post, already signed in as themselves.
  4. Give instructors or support staff a seat. Invite them from the dashboard, restrict them to the Moderator role on Pro, and turn on approve-from-email or Slack and Discord alerts (from Starter) so new questions reach them where they work. See comment moderation.

Questions

What is a good comment system for an online course?
One that puts a thread under every lesson, lets enrolled students post without creating a new account, and gives instructors a shared moderation queue. EchoThread does this with single sign-on on the Pro plan, so students comment as the identity they already use in your course. Star ratings (from Starter) let students rate a lesson, and spoiler tags let them discuss quiz answers without giving them away.
What is a good comment system for a product documentation site?
For docs read by customers, pick a hosted widget that allows guest or social sign-in, screens spam before publishing, and routes new questions to your support team. EchoThread fits that. For open-source developer docs where every reader has a GitHub account and comments contain code, Giscus is a good free choice because comments live in GitHub Discussions.
Can students or customers comment without creating an account?
Yes. Turn on guest commenting and readers post with only a display name; every guest comment is screened by the spam filter first. Or connect single sign-on on Pro so they are signed in automatically with the account they already have on your platform.
Does EchoThread work with Docusaurus, MkDocs or my LMS?
It works on any page where you can add a script tag, which covers Docusaurus, MkDocs, VitePress, Hugo, Astro and most hosted course platforms that allow custom HTML. Set a stable data-identifier per lesson or page so threads survive URL changes. Platforms that only let you embed inside a sandboxed iframe can show comments but may block sign-in.
How much does it cost for a course or docs site?
The Hobby plan is free forever for one site and 10,000 page views a month. Starter is $5 a month for 3 sites, 100,000 page views, star ratings and email and chat alerts. Pro is $19 a month and adds single sign-on and the Moderator role.

More on courses: comment systems for online courses and LMS engagement.