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

comment system #33

Open
samazgor opened this issue Feb 28, 2019 · 4 comments
Open

comment system #33

samazgor opened this issue Feb 28, 2019 · 4 comments

Comments

@samazgor
Copy link

how to integrate Disqus or other comment systems?

@Taboo69
Copy link

Taboo69 commented Mar 30, 2019 via email

@ageitgey
Copy link
Owner

ageitgey commented Apr 3, 2019

You would just paste in the Disqus code on the page template under the content here: https://github.com/ageitgey/amplify/blob/master/_layouts/post.html#L12

@aicochow
Copy link

my blog added Disqus
https://gfw-blog.netlify.com/2018/05/11/cse-amp.html

@VincentTam
Copy link

VincentTam commented Jun 25, 2019

Hi, this is the maintainer of @staticmanlab, a public GitLab instance of Staicman. Here's some shortcomings of the commenting systems mentioned above.

  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.
  4. Disqus is difficult to access for non programmers in the PRC, as reported in 期望增加来必力、畅言评论的公共代码 Huxpro/huxpro.github.io#258 (comment).

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.


To have a taste of Staticman in minutes, you might try Beautiful Hugo. Otherwise, you may consider cloning any one of my demo sites on Framagit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants