Open cseas opened 5 years ago
I have used Staticman before. It basically needs a hosted service of static man, that listens for webhooks from our frontend.
For each comment, it actually creates a commit to the repository with the comment/data. Thats how they provide Static sites with superpowers
.
They do have a public hosted service of staticman, but it is too overused. We would not be able to use it.
While working on Flutter Arsenal I did host and set up a self-hosted version of statesman.
The endpoint, if anyone wants to set it up
https://staticman.flutterarsenal.com/staticman/{GITHUB USERNAME}/{GITHUB REPOSITORY}/{BRANCH}/{PROPERTY (optional)}
Here is that thread https://github.com/flutterarsenal/FlutterArsenal/issues/46 to have implementation guide/help.
I vote for not having comments for these reasons
Practically this means
I feel a similar way as @asdofindia, the blog posts on the blog till now have been more along the lines of information updates or announcements. I don't think these types of blog posts increase the involvement of the readers. The talk/workshop events usually already do post their dedicated channels of communication.
I think this is something we should look into if the authors plan to write reader engaging posts such as Q/A, Discuss, Share your X(Setup, IDE Settings, etc) and such.
+1 for not having comments for now. I also really like the idea to redirect discussion etc to GitHub and Telegram channels.
And we can setup comments anytime community feels a need later
Should we enable a comments system on the blog? And if yes, then which comments system?
Since it's a static blog, we probably won't be able to come up with our own implementation of a comments system, unless we shift to a dynamic framework.
That leaves us with using third-party plugins like Disqus and Facebook for comments. While they might raise privacy issues, they do have a good spam filtering and comment moderation. Would love to discuss any alternates available too if we want to enable comments.
Related to PR #16