-
Notifications
You must be signed in to change notification settings - Fork 77
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
Giscus comments #251
Comments
Looks like a cool solution. Comments is a bit uncommon for docs-sites though, isn't it? Off-topic: In your example, why does it look like you're talking to yourself? You mention someone else, but only your posts :) |
I agree that it is a bit uncommon but I can imagine it making the hurdle to comment, ask, etc. much lower. The reason you are seeing me talking to myself (online and in real-life now) is... that those comments were imported from Disqus (hover on a username). |
Upvote on this, azdo has comments for wiki and it is very useful when the page becomes outdated and people post tips on how to actually do the thing the page describes. |
Sounds great 👍 Usually I'd say GitHub-only would limit a comment-solution, but as it's already required to make a docs-issue it's fine. |
No issues at all and even though spam is non-existent, annoying responses can always be deleted in Github Discussions. |
Checklist
Summary of the request
We could consider adding Giscus comments (built on Github discussions) for pages:
Additional info:
Try it out here https://www.bravo-kernel.com/blog/2020/01/creating-a-scheduled-broken-links-checker-using-github-actions
Suggested section
None
The text was updated successfully, but these errors were encountered: