-
Notifications
You must be signed in to change notification settings - Fork 165
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
Comments
??
…On Thu, Feb 28, 2019, 2:26 PM Sam Azgor ***@***.***> wrote:
how to integrate Disqus or other comment systems?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#33>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARITS4f9EX_qErh9wUJA3SMEGox38e8Cks5vSEmHgaJpZM4bXxS8>
.
|
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 |
my blog added Disqus |
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. 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. |
how to integrate Disqus or other comment systems?
The text was updated successfully, but these errors were encountered: