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

Add links to discuss blog posts (github/telegram/etc) #17

Open
cseas opened this issue Oct 16, 2019 · 4 comments
Open

Add links to discuss blog posts (github/telegram/etc) #17

cseas opened this issue Oct 16, 2019 · 4 comments

Comments

@cseas
Copy link
Contributor

cseas commented Oct 16, 2019

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

@cseas cseas mentioned this issue Oct 16, 2019
4 tasks
@karx
Copy link
Contributor

karx commented Oct 16, 2019

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 flutterarsenal/FlutterArsenal#46 to have implementation guide/help.

@asdofindia
Copy link
Contributor

I vote for not having comments for these reasons

  • we have historically not had many valuable comments
  • people discuss blog posts differently these days, and comments are usually in social media posts

Practically this means

  • 0 overhead
  • let us redirect people to GitHub/Telegram channels if they want to discuss

@Amorpheuz
Copy link
Member

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.

@karx
Copy link
Contributor

karx commented Oct 17, 2019

+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

@asdofindia asdofindia changed the title Comments on the blog Add links to discuss blog posts (github/telegram/etc) Oct 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants