Request for AsciiDoc support

[rphillips]

Looks like a fantastic project. I don't know if the backend is modular to support other filetype backends, but I would like to see AsciiDoc support.

[ericholscher]

It basically just uses Sphinx, so if you want AsciiDoc support, it would need to be supported in Sphinx.

If it's supported in Sphinx, then it should be pretty do-able in RTD.

[ericholscher]

Ah, you're asking for us to be able to build and host AsciiDoc docs. I see, I'll keep this in mind. We're pretty sphinx focused at the moment, but it might be worth it at some point.

[rphillips]

Thanks for the reply. In addition, I've been thinking hosting the epub files generated from Sphinx would be nice on readthedocs.

[ericholscher]

Totally. Does it make sense to display the epub's, or should they just be downloadable?

[rphillips]

Perhaps a button to the right or left of the 'View Docs' button for 'Download'. The button could automatically expand to 'EPUB', 'PDF', 'HTML Compressed', etc to allow a user to download the documentation for offline browsing.

Similarly, when a user has drilled down into a project's document, there is a "Brought to you by Read the Docs". A button there with an option to download pdf/epub/etc would be slick, I think.

[ericholscher]

Do you have a good project that I could test ASCIIDoc building against? I'd like to try and add this as the first non-sphinx builder backend.

[rphillips]

the git project uses a lot of asciidoc. http://git.kernel.org/?p=git/git.git;a=summary

[ericholscher]

As a design decision, we have chosen to invest heavily in Sphinx, and not support other backends. This would complicate a lot of things, and I want to have RTD act as a way to evangelize Sphinx. Having the code base support other backends would be easy, and is lightly documented here: http://read-the-docs.readthedocs.org/en/latest/builds.html#writing-your-own-builder

I would accept code into the code base to allow this, but the readthedocs.org instance of the code base will focus on Sphinx.