Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate from Disqus #118

VincentTam opened this issue Aug 10, 2019 · 1 comment


Copy link

commented Aug 10, 2019

Hi, this is the maintainer of @staticmanlab, a public GitLab instance of Staicman. #107 has added Disqus support. However, please revert it due to some shortcomings of some common third-party commenting systems.

  1. Gitment, Gitalk and Utterance support only GitHub, and they require user login before commenting. This can scare away many non programmers from leaving a comment to your posts. Besides, comments are part of the site's static content, not a software package problem. As a result, using GtiHub issues for comment storage is wrong in principle and bad in terms of SEO.
  2. Commento is not free as in free beer. For a personal blog with small traffic, you might find a monthly fee of $5 too expensive.
  3. Disqus and Isso contain a 3rd-party script to be loaded during page rendering. The code block for loading each of them shows that the static comments are not rendered as static HTML code. This hinders search engines from grabbing the comments, which are part of the site's content. As a result, that leads to suboptimal SEO.

To see more reasons for migrating from Disqus, you may view


You may avoid these problems by switching to Staticman, which makes use of GitHub/GitLab Pull/Merge Requests instead of issues. Under Staticman's model, static comments are YML/JSON files stored in the remote GitHub/GitLab repo (usually under data/comments, configurable through the path parameter in root-level staticman.yml), and through a static blog generator (Jekyll/Hugo/etc), the stored data are rendered as part of the content. This gives a total ownership of a static site's comments.

ℹ️ There're many ways to Rome, say JAM Stack, Jekyll AWS comments, etc.


This comment has been minimized.

Copy link

commented Aug 10, 2019

Thanks for raising your concern. However, I don't like the idea of storing user comments in my repository. At minimum, each post should then have an explicit confirmation box requiring users to agree their data is owned fully by me.

Disqus has a slight performance impact but for example Google Analytics has worse. Seeing how widely used platform Disqus is and being able to inject both the discussion area and comments count as simple React components makes the tradeoff acceptable. The Lighthouse score for SEO is still at 100 so there's no reason to worry about it either.

Repository owner locked as resolved and limited conversation to collaborators Aug 10, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
2 participants
You can’t perform that action at this time.