search

fi3ework / hexo-theme-archer

🎯 A smart and modern theme for Hexo.
https://fi3ework.github.io/hexo-theme-archer
MIT License
1.51k stars 273 forks source link

Comments system does not work #225

Open mishka86 opened 5 years ago

mishka86 commented 5 years ago

Thank you for creating the theme.

I want to build a comment system using disqus. I have tried many different ways

"We were unable to load Disqus. If you are a moderator please see our troubleshooting guide." The above phrase is exposed.

If you know what the problem is, please suggest a solution.

ddgth commented 5 years ago

Thank you for creating the theme.

I want to build a comment system using disqus. I have tried many different ways

"We were unable to load Disqus. If you are a moderator please see our troubleshooting guide." The above phrase is exposed.

If you know what the problem is, please suggest a solution.

you can try using valine plug. https://valine.js.org/ apply your key then add to the _config.yml of the theme.

mishka86 commented 5 years ago

Thank you for your reply. But what I want to do is to use 'disqus' instead of 'valine'.

VincentTam commented 5 years ago

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, Valine 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.

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.