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

Enable comments on posts #20

Open
sc0ttj opened this issue Feb 19, 2019 · 5 comments
Open

Enable comments on posts #20

sc0ttj opened this issue Feb 19, 2019 · 5 comments
Labels
enhancement New feature or request

Comments

@sc0ttj
Copy link
Owner

sc0ttj commented Feb 19, 2019

Use Disqus (or similar)

@sc0ttj
Copy link
Owner Author

sc0ttj commented Feb 19, 2019

Also:

@sc0ttj
Copy link
Owner Author

sc0ttj commented Feb 19, 2019

Disqus would be best - most popular, biggest community, most likely to get comments ..

Then gitment would be nice.. Looks nice.. Seems lightweight, easy.

@sc0ttj sc0ttj added the enhancement New feature or request label Feb 20, 2019
@sc0ttj
Copy link
Owner Author

sc0ttj commented May 29, 2019

Here are two good alternatives to Disqus, more lightweight, seem nice:

https://commento.io/ - looks great
https://posativ.org/isso/

@VincentTam
Copy link

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. Isso contains a 3rd-party script to be loaded during page rendering. The above code block 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.

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.

@sc0ttj
Copy link
Owner Author

sc0ttj commented Jun 20, 2019

Thanks for the information @VincentTam, I will look into it..

I would definitely prefer something that automated the adding of comments to the page itself, so that they were embedded as HTML, like any other content on the page, so Staticmanlab seems ideal.

I will have a go at implementing it at some point in the future 👍

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

No branches or pull requests

2 participants