Xavier Coulon

@DavidGamba first, sorry for the late response! I intentionally used the `strings.ToLower` func in order to mimic what Asciidoctor does when rendering the content (ie, generate `href` value with lowercase....

Hello @DavidGamba Oh, I see what you mean now. I think I missed the point where you mentioned your custom backend! 🤦‍♂️ I'm not sure if it's going to break...

I need to see if such a linter already exist (as a GitHub Action would be ideal)

cool, thanks for the links @moorereason! I'll give it a try soon

yes, I generate the changelog that appears on https://github.com/bytesparadise/libasciidoc/releases using https://github.com/conventional-changelog/conventional-changelog and it parses the commit message to determine the type commit it was, and the scope.

> By the look of it, there's an uniformized rendering function for headers ([source](https://github.com/bytesparadise/libasciidoc/blob/master/pkg/parser/asciidoc-grammar.peg#L69-L75)). The grammar rules for parsing the headers (a.k.a "sections") is defined in https://github.com/bytesparadise/libasciidoc/blob/master/pkg/parser/asciidoc-grammar.peg#L376-L544. What you've linked...

ok, I see now. So we would need some kind of custom, configurable post-processor to enrich/modify the output of some elements, as you've shown in your example. It's not possible...

thanks for your feedback and your suggestion, @edl7878! > I think it is better to realize export to Docbook firstly? because they are twins in different formats. > Docbook is...

hello @edl7878, thanks for your feedback and your suggestion. I agree that having a common interface for all types of element would make sense and would be helpful to traverse...

@edl7878 out of curiousity, may I ask why you closed this issue? I found this discussion interesting, especially since you provided some requirements.