Add support for native Go implementation of AsciiDoc

[anthonyfok]

Starting with v0.14 (released in May 2015), Hugo provides preliminary support for AsciiDoc with the help of an external helper such as asciidoc (Python-base) and asciidoctor (Ruby-based).

Please see Issue #470 "Support for AsciiDoc" (which led to the current experimental "external helper" implementation) for more information. This issue

However, the ultimate goal is for Hugo to support a native Go implementation of AsciiDoc, something that e.g. the https://github.com/VonC/asciidocgo project set out to accomplish. This issue will track the progress on that front.

[bguiz]

Note that the linked AsciiDocGo project is unmaintained, and is likely to remain so - see VonC/asciidocgo#1 (comment) - where the author says it only covers about 10-15% of the surface area covered by AsciiDoctor.

That being said, I would still very much like to see this happen. This begs the question - is Hugo going to attempt to use AsciiDocGo, or write its own implementation?

[anthonyfok]

Yes, @bguiz, I agree with you totally. Consider this issue more a "Call for Action" for volunteers to take up this worthy but challenging task. It won't happen right away, but if the demand is high enough, I am sure someone will take up the task and either continue with the great work that @VonC started, or start a new implementation if that is easier. Perhaps some kind of open-source bounty or crowdfunding could be considered too, a possibility as our community continue to grow. Just some random ideas. :-)

Meanwhile, I am starting to think that whether some kind of a mythical Ruby-to-Go converter would be feasible to help with this task, haha! I can always dream. 😉

[kastork]

I wonder if there might be a way to use https://github.com/robertkrimen/otto to render asciidoc with
https://github.com/asciidoctor/asciidoctor.js

[bep]

That sounds slow.

[kastork]

Could be. If the otto is slow then it is sure to be. But it might be a way to make the asciidoc solution self-contained rather than relying on the external process (which is also slow).

Anyway, just tossing it out there. I was inspired by the mythical ruby-to-go converter comment above. (asciidoc.js is generated by a ruby-to-js converter from what I understand).