You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider you define a set of strings that qualify a top-level heading of the article as the comment section. In my use-case, this would be COMMENTS_LINE_DEFINITIONS = ['Comments', 'Kommentare'].
Whenever there is a heading on the top level of the current article, this section is stored and handled differently, if you want.
For example, you could define the page template such, that the comment section goes to the bottom of the page. Below the "Related articles that link to this one" and even below the Disqus comments.
The text was updated successfully, but these errors were encountered:
What is that comment section then, if not the disqus comments?
Publicvoit is currently using two comment methods: email and disqus.
This is not about disqus, which I want to get rid of anyway: #40
Whenever there is an email comment coming in, I copy the relevant parts of that email to the article. For that, I usually add a heading. Those headings are indistinguishable from all other headings. This feature adds a tag that allows lazyblorg to handle comment-headings differently.
you add that by hand? This could also be automatic, hmm...
I don't see how. I would have to run a service that parses incoming emails, associates them to the known articles and generates an Orgdown version of it in my personal Orgdown file. Furthermore, this would lack any check against spam or value.
This is a feature wish.
Consider you define a set of strings that qualify a top-level heading of the article as the comment section. In my use-case, this would be
COMMENTS_LINE_DEFINITIONS = ['Comments', 'Kommentare']
.Whenever there is a heading on the top level of the current article, this section is stored and handled differently, if you want.
For example, you could define the page template such, that the comment section goes to the bottom of the page. Below the "Related articles that link to this one" and even below the Disqus comments.
The text was updated successfully, but these errors were encountered: