Issue #7132 new

Render AsciiDoc files (BB-1913)

Dobrosław Żybort
created an issue


would be nice if you could render AsciiDoc files (after all it's written in Python).

File extensions to catch:

.ad, .adoc and .asciidoc

(and probably .ad.txt, .adoc.txt and .asciidoc.txt: )

Repo with samples:

Comments (47)

  1. laher

    +1, this feature gets my vote. Asciidoc is more appropriate (than e.g. Markdown) for authoring books and longer texts. Thanks

  2. jochenhinrichsen

    +1 While i like Markdown, Asciidoc outputs Docbook out of the box which opens up the whole nine yard of the publishing pipeline.

    As an implementation, i'd rather choose the newer Ruby based Asciidoctor instead of the older Python based Asciidoc.

  3. Dan Allen


    There's a Java API for Asciidoctor called AsciidoctorJ that encapsulates the use of JRuby. Bintray uses AsciidoctorJ to render AsciiDoc files. Asciidoctor runs fastest on JRuby anyway.

    Asciidoctor is also very secure for serve-rside usage. By default it runs in secure mode, which disables all file system access. You are free to enable the functionality from there that works best for you.

    AsciiDoc is gaining a lot of traction with big name authors lately, largely do to the innovation & advocacy coming out of the Asciidoctor project & community.

    GitHub uses Asciidoctor to render AsciiDoc, but it hasn't been upgraded past version 0.1.0 released in January. BitBucket could grab the reigns here by deploying 0.1.4 or 1.5.0.preview.1.

  4. TheSteve0

    +1 - we are storing the initial drafts of our book for O'Reilly here and it would be really nice as a paying customer if we could render the files

  5. zgamero

    I've tried reST, Markdown and AsciiDoc, finding the last one the more confortable and it's growing in popularity, IMHO.

    +1 for adding AsciiDoc

  6. Daniel Grigg

    +1 so colleagues will stop complaining about me writing bitbucket-un-renderable readme's

    Honestly asciidoc is just more feature-complete with less hacks required for writing technical docs.

  7. Arto Astala

    +1 Makes you wonder what use is issue tracker when a feature has issue filed, +1:d a lot, requested for readmes, is easy to implement and safe but sees no action or even comment from staff. Didn't even bother to change status from new in more than two years.

  8. Sean Gilligan

    Github and Gitlab (for free private repos) both support AsciiDoc. I've given up on Bitbucket because of this issue. Unwatching this issue and moving on....

  9. Log in to comment