Pelican Comment System
As previously posted I have added commenting to my site. I used the methodically named Pelican Comment System by Bernhard Scheirle. Bernard seems to have abandoned the project but luckily for me it is still working. There was a couple of glitches I ran into…
The first one was listed as an issue, a simple fix, amending get_writer to _get_writer on line 89 of ../site-packages/pelican_comment_system/init.py
The next glitch was actually just my own brain not getting it. If a comment is not a direct reply to a previous comment then replyto is not a required value. Seems obvious now. A comment is basically the same as the rest of the posts, just a file. This is the bare minumum that’s needed:
date: 2021-1-21 15:00
author: Norman
Content of the comment.
Other values that can be used are as follows:
| tag | description |
|---|---|
| the commentators email address | |
| replyto | the id of the comment one is replying to |
| website | any website address given will be used to wrap the commenters name in a link |
| slug | the persistent uri of the comment, if not used it gets computed from the filename |
| χ | Where the arbritary string χ is parsed to be available in the theme as {{comment.χ}} |
To do
- Modify the Identicons. Limit the colours used to fit my site style.
I also quite like these space invaderesque ones). - Custom Identicons for select authors
- Comments are few and far between on tregeagle.com, for a busier site it would be worthwhile to build upon Bernhard’s IMAP_Importer
- Use an inline form instead of relying on my visitors to send an email.
One of the barriers to this implementation of the Pelican Comment System is switching from the page you are browsing to your email window. We humans have the attention spans of gnats and most of us probably decide it’s not worth an email.
Comments
Add a comment?There are no comments yet.