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

Implement "Comments" section is able to be separated from the main text #31

Open
novoid opened this issue Apr 12, 2019 · 4 comments
Open

Comments

@novoid
Copy link
Owner

novoid commented Apr 12, 2019

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.

@xeruf
Copy link
Contributor

xeruf commented Sep 3, 2022

Consider you define a set of strings that qualify a top-level heading of the article as the comment section.

Below the "Related articles that link to this one" and even below the Disqus comments.

What is that comment section then, if not the disqus comments?

@novoid
Copy link
Owner Author

novoid commented Sep 4, 2022

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.

@xeruf
Copy link
Contributor

xeruf commented Sep 4, 2022

you add that by hand? This could also be automatic, hmm...

@novoid
Copy link
Owner Author

novoid commented Sep 5, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants