I’d like to give a quick update about the comments on this blog. I already mentioned in a previous post that I wanted to experiment with fully static comments for my blog. By fully static I mean that comments are directly integrated in the HTML of each page, at generation time. It requires to generate pages with new comments regularly but I think it’s a good trade-off.
I’d like to give an overview of how it works, and how it looks in practice.
How does it Work?
- Comments will be posted and hosted on Github Issues.
Markdowndocument has an optional
issueattribute in its metadata; when it is specified, the static blog generator will fetch the comments of the specified issue every time we build the site.
- Issues are directly integrated in the HTML of the page (at the bottom) and are collapsed by default.
I see several advantages with this system:
- It’s fast because it’s part of the page’s HTML.
- The look and feel of the page is consistent.
- It leverages Github, which is already used to host the blog anyway, so why not use the
Obviously it’s not perfect because:
- People need a Github account to post comments: but I expect a lot of people do, and if they don’t, there are a lot of ways to discuss blog posts on the Internet: Reddit, HackerNews, Twitter; and they all have their sharing button at the bottom of the page!
- It takes a bit of time to refresh the comments (currently
Traviswill deploy the posts at least once a day + every time I do a commit), but they can always be seen in real time on the
- It might not scale very well with a lot of comments, but I will be happy to figure out a solution for this problem when it happens with this blog!
How it Looks
This post is already equipped with the static comments. I created a few of them to demonstrate the look and feel. You can expend the comments by clicking the first link on the left
N comments, or post a new one by clicking on
Leave a comment on Github (you will be redirected on the correct
Feel free to add more! I’d love to get some feedback on this.