Add pandoc source and renderer

[nichtich]

What are the results of this discussion?

I'd like to propose to primarily use the Pandoc document model for source and rendering. Pandoc is a universal document converter covering Markdown, Office, TeX and many more. It is being developed and used heavily since years so it also covers most edge cases and pitfalls of these formats. Pandoc internally converts document formats to its document model which can be read and written as JSON, e.g.:

echo '# Hello _World_' | pandoc -t json

For reference of the model see this Haskell package. Maybe this mapping to Perl I've written a few years ago, is also of use. So the workflow for converting documents to and from atjson would be:

• Document => Pandoc JSON => atsjon
• atjson => Pandoc JSON => Document

When atjson specification will be finished, support of atjson could also be added to the Pandoc source code.

What do you think about use of Pandoc for conversion from and to atjson?

[tim-evans]

This would be cool to have as an addition. I don't think we have the bandwidth for this, but it'd definitely be something that's inline with what we have here.

[codegod100]

I've been writing a PEG parser for my friend's markup language that outputs pandoc ast, this would be cool to have