Open yingziwu opened 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.
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.
@VincentTam Thanks for your advice. After reading the document of Staicman, Staicman seems to only support Jekyll. But my blog is based on Nikola, so I can't use Staicman. Thank you any way.
@VincentTam Thanks for your advice. After reading the document of Staicman, Staicman seems to only support Jekyll. But my blog is based on Nikola, so I can't use Staicman. Thank you any way.
In fact, Staticman is just a tool for pushing HTML form data into GitHub/GitLab repo, and it doesn't care whether there's a static blog generator or not. See the author's comment at https://github.com/eduardoboucas/staticman/issues/264#issuecomment-460446511. As long as you own a GitHub/GitLab repo, you can use Staticman. You may see the barebone example https://gitlab.com/ntsim/test-staticman. (require GitLab login)
I had missed my list of Staticman demo pages on Framagit in my last comment. It contains a variety of Hugo and Jekyll themes.
Figure: Math display in static comments on my demo Beautifhul Hugo + Staticman site
https://blog.bgme.me//posts/add-disqus/
向博客添加Disqus评论系统的过程