Asciidoctor Community

The Asciidoctor community of projects (aka Asciidoctor Project) is an perpetual effort to develop an accessible, comprehensive, and open source toolchain and workbench for writing and publishing AsciiDoc content across various platforms and runtimes.

In addition to AsciiDoc processors for Ruby, the JVM platform, and JavaScript, the community develops plugins/add-ons for automation tools, browsers, and IDEs, as well as extended converters for producing additional output formats, adapters for expanding integrations, and extensions for augmenting AsciiDoc documents with rich media such as diagrams and charts.

The Asciidoctor community also pushes the AsciiDoc language to evolve by introducing new ideas and innovations and promotes AsciiDoc through documentation and advocacy.


The Asciidoctor Project is a loosely knit collection of projects. All Asciidoctor projects are open source (either MIT or Apache 2.0). The source repositories and issue trackers for these projects are hosted on GitHub. Each project has its own project lead(s) and maintainers (aka project team), who determine how the project is run. All contributors volunteer their time to work on a project. Asciidoctor is the primary project and, as such, provides the overall direction and vision for the community. Projects generally follow semantic versioning, though it’s not (yet) true of all projects.


All the documentation on this site is written in AsciiDoc and published by Antora.

The source of the documentation is not stored in a single location. Rather, the documentation is stored with the project it documents. For example, the documentation for the core Asciidoctor processor can be found under the docs folder in the repository at Antora aggregates the documentation from multiple repositories and publishes it together to make this site.

The repository that contains the build manifest that pulls all the documentation together is located at We refer to this as the playbook repository. The documentation content sources are defined in the Antora playbook file, antora-playbook.yml. The location of the UI (i.e., the bundle of page templates, CSS, images, and scripts) of the site is also defined in the playbook file. The UI is stored in yet another repository at, which also hosts the released UI bundles. The build amounts to passing that playbook file to the antora command.

$ antora antora-playbook.yml

The site gets built and published nightly and on each commit to the playbook repository. If you submit a PR to the playbook repository, you will be provided with a deploy preview that includes any additional content sources you’ve added to the playbook repository. See the playbook repository for more information about how the site is built and how to build and preview it on your own machine.

Relationship to AsciiDoc

Asciidoctor serves as the reference parser/interpreter for the AsciiDoc syntax as we know it today. In other words, Asciidoctor is the official reference for how to parse and convert modern AsciiDoc.

Given this standing, Asciidoctor is inherently compliant with the AsciiDoc syntax. And Asciidoctor has evolved the AsciiDoc syntax since it took over this role from Yet, to continue evolving the syntax while encouraging more implementations without introducing divergence, we know we need a more formal definition for what AsciiDoc is. In other words, we need an AsciiDoc standard that’s independent from Asciidoctor.

The Asciidoctor project has been a driving force behind the initiative to establish a working group for AsciiDoc at the Eclipse Foundation. The main goal of the AsciiDoc Working Group is to oversee the creation of a formal specification for the AsciiDoc language. While Asciidoctor plans to become a compliant implementation, the specification and associated compliance program also invites other implementations to emerge.

The future

We expect the Asciidoctor Project to play a leading role in the AsciiDoc community for many years to come.