commentator VS staticman

i'm the author of Commentator, a commenting system where comments are stored on any s3 compatible store (easier to manage than a DB or local storage): https://github.com/mcorbin/commentator

It's still WIP but it supports comments approval, has a rate limiter, a challenge system to avoid spammers... I already use it for my personal blog.

Staticman - Staticman is a Node.js application that receives user-generated content and uploads it as data files to a GitHub and/or GitLab repository, using Pull Requests.

Staticman

Another possible solution to add dynamic content to a GitHub website is to use staticman. On the opposite of the previous solutions using external databases, staticman creates files in your repository, updating your website statically. It is free and open-source but not as straightforward to implement as disqus. The nice thing is that it will store all your comments in your git repository, so there is no risk of losing them.

This article is part of a series showing you how to quickly and freely build and host your own Jekyll blog on GitHub Pages. This series will also cover more advanced topics like adding a comment system directly in our code using Staticman and adding privacy-friendly but still free analytics using Umami.

We will also cover more advanced topics like adding a comment system directly in our code using Staticman and integrating free privacy-friendly analytics using Umami.

I'm late to the game, but I'm surprised that no one has mentioned StaticMan yet:

https://github.com/eduardoboucas/staticman

Just uses Git(Hub) to triage and approve comments for your static sites, like Jekyll.

Alternatives from my notes (never used them IRL):

* https://github.com/eduardoboucas/staticman

* https://github.com/schn4ck/schnack