[ptwobrussell]

Wow, you definitely have some great ideas here, and given the enthusiasm about ipynb, I would not be surprised to see these things happen in the next 6-12 months.

O'Reilly does use docbook internally as part of the toolchain, but asciidoc is coming into style as well. I've done most of my work in docbook with a docbook editor, but did some of my latest boook in asciidoc, which was much easier. Just use a standard text editor of choice (like Vim) and get right to it. Much easier for me, anyway.

One thing I'd really like to see is ipynb supporting asciidoc instead of or in addition to markdown. You can go to/from asciidoc and docbook in a lossless way, IIRC.

[mcburton]

asciidoc support would require an ansciidoc renderer written in javascript, which does seem to exist[1](although I haven't used it). This also highlights some of the problems with markdown because it is an insufficiently rich language for generating semantically meaningful markup for use-cases beyond blogging. There has been some really interesting work on "scholarly markdown"[2][3], but given the social and technical complexities of markdown implementations and the community[4] seems like adding asciidoc is easier than fixing markdown.

[1] http://asciidoctor.org/news/2013/05/21/asciidoctor-js-render...

[2]https://github.com/scholmd/scholmd/wiki

[3]http://blog.martinfenner.org/2013/06/19/citations-in-scholar...

[4]http://www.codinghorror.com/blog/2012/10/the-future-of-markd...