Asciidoctor is a fast, open source text processor and publishing toolchain for converting AsciiDoc content to HTML5, DocBook, PDF, and other formats. Asciidoctor is written in Ruby and runs on all major operating systems. The Asciidoctor project is hosted on GitHub.
To simplify installation, Asciidoctor is packaged and distributed as a RubyGem (aka gem) to RubyGems.org. It’s also distributed as a package for popular Linux distributions and macOS. In addition to running on Ruby, Asciidoctor can be executed on a JVM using AsciidoctorJ or in any JavaScript environment (including the browser) using Asciidoctor.js.
We want to recognize our sponsors for their commitment to improving the state of technical documentation by supporting this project. Thank you sponsors! Without your generous support, Asciidoctor would not be possible.
Major funding for Asciidoctor is provided by our Change Maker, OpenDevise, our Strategy Sponsors, Khronos Group and Linda Roberts, and our Pull Request Backers, Brian Dominick, Guillaume Grossetie, and Abel Salgado Romero. Additional funding is provided by the supporters listed on our Community Backers page.
You can support this project by becoming a sponsor through OpenCollective.
Asciidoctor reads content written in plain text, as shown in the panel on the left in the image below, and converts it to HTML5, as shown rendered in the right panel. Asciidoctor applies a default stylesheet to the HTML5 document to provide a pleasant out-of-the-box experience.
Asciidoctor reads and parses text written in the AsciiDoc syntax, then feeds the parse tree to a set of built-in converters to produce HTML5, DocBook 5, and man(ual) page output. You have the option of using your own converter or loading Tilt-supported templates to customize the generated output or produce additional formats.
Asciidoctor is a drop-in replacement for its predecessor, AsciiDoc Python (asciidoc.py).
The Asciidoctor test suite has > 2,350 tests to ensure compatibility with the AsciiDoc syntax.
In addition to the classic AsciiDoc syntax, Asciidoctor recognizes additional markup and formatting options, such as font-based icons (e.g., icon:fire[]) and UI elements (e.g., button:[Save]).
Asciidoctor also offers a modern, responsive theme based on Foundation to style the HTML5 output.
You can run Asciidoctor on the JVM using JRuby. To invoke the Asciidoctor API directly from Java and other JVM languages, use AsciidoctorJ. There are plugins available for Apache Maven, Gradle, and Javadoc, which allow you to integrate AsciiDoc processing directly into your build using AsciidoctorJ.
Asciidoctor also runs in JavaScript. Opal is used to transcompile the Ruby source to JavaScript to produce Asciidoctor.js. Asciidoctor.js is a fully-functional version of Asciidoctor that works in any JavaScript environment, such as a web browser or Node.js. It’s used to power the AsciiDoc preview extensions for Chrome, Atom, Brackets and other web-based tooling.
Asciidoctor works on Linux, macOS and Windows and requires one of the following implementations of Ruby:
-
CRuby (aka MRI) 2.3 - 2.6
-
JRuby 9.1 - 9.2
-
TruffleRuby (GraalVM)
-
Opal (JavaScript)
|
🔥
|
If you’re using a non-English Windows environment, you may bump into an chcp 65001 Once you make this change, all your Unicode headaches will be behind you. If you’re using an IDE like Eclipse, make sure you set the encoding to UTF-8 there as well. Asciidoctor works best when you use UTF-8 everywhere. |
Asciidoctor can be installed using (a) package managers for popular Linux distributions, (b) Homebrew for macOS, (c) the gem install command (recommended for Windows users or if you’ll be installing additional gems), (d) the Asciidoctor Docker image, or (e) Bundler.
The benefit of using your operating system’s package manager to install the gem is that it handles installing Ruby and the RubyGems library if those packages are not already installed on your machine.
The version of Asciidoctor installed by the package manager may not match the latest release of Asciidoctor. Consult the package repository for your distribution to find out which version is packaged per distribution release.
If you want to use a version of Asciidoctor that is newer than what is installed by the package manager, see the gem installation instructions.
To install the gem on Alpine Linux, open a terminal and type:
$ sudo apk add asciidoctor
To install the gem on Arch-based distributions, open a terminal and type:
$ sudo pacman -S asciidoctor
On Debian and Debian-based distributions such as Ubuntu, use APT to install Asciidoctor. To install the package, open a terminal and type:
$ sudo apt-get install -y asciidoctor
You can use Homebrew, the macOS package manager, to install Asciidoctor.
If you don’t have Homebrew on your computer, complete the installation instructions at brew.sh first.
Once Homebrew is installed, you’re ready to install the asciidoctor gem.
Open a terminal and type:
$ brew install asciidoctor
Homebrew installs the asciidoctor gem into an exclusive prefix that’s independent of system gems.
To use Asciidoctor with Windows, you have two easy options.
When you already use chocolatey on your machine, you can use:
choco install rubyThen follow gem installation instructions.
Or you use the Rubyinstaller, download the package for your Windows Version and after the installation go ahead with gem installation instructions.
Before installing Asciidoctor using gem install, you should set up RVM to install Ruby in your home directory (i.e., user space).
Then, you can safely use the gem command to install or update the Asciidoctor gem, or any other gem for that matter.
When using RVM, gems are installed in a location isolated from the system.
Once you’ve installed Ruby using RVM, and you have activated it using rvm use 2.6, open a terminal and type:
$ gem install asciidoctor
If you want to install a pre-release version (e.g., a release candidate), use:
$ gem install asciidoctor --pre
-
Create a Gemfile in the root folder of your project (or the current directory)
-
Add the
asciidoctorgem to your Gemfile as follows:source 'https://rubygems.org' gem 'asciidoctor' # or specify the version explicitly # gem 'asciidoctor', '2.0.10'
-
Save the Gemfile
-
Open a terminal and install the gem using:
$ bundle
To upgrade the gem, specify the new version in the Gemfile and run bundle again.
Using bundle update (without specifying a gem) is not recommended as it will also update other gems, which may not be the desired result.
If you installed Asciidoctor using a package manager, your operating system is probably configured to automatically update packages, in which case you don’t need to update the gem manually.
If you previously installed Asciidoctor using the gem command, you’ll need to manually upgrade Asciidoctor when a new version is released.
You can upgrade the gem by typing:
$ gem install asciidoctor
When you install a new version of the gem using gem install, you end up with multiple versions installed.
Use the following command to remove the old versions:
$ gem cleanup asciidoctor
If the Asciidoctor gem installed successfully, the asciidoctor command line interface (CLI) will be available on your PATH.
To verify it’s available, run the following in your terminal:
$ asciidoctor --version
You should see information about the Asciidoctor version and your Ruby environment printed in the terminal.
Asciidoctor 2.0.10 [https://asciidoctor.org] Runtime Environment (ruby 2.6.0p0 [x86_64-linux]) (lc:UTF-8 fs:UTF-8 in:- ex:UTF-8)
Asciidoctor also provides an API. The API is intended for integration with other Ruby software, such as Rails, Sinatra and GitHub, and other languages, such as Java (via AsciidoctorJ) and JavaScript (via Asciidoctor.js).
The asciidoctor command allows you to invoke Asciidoctor from the command line (i.e., a terminal).
The following command converts the file README.adoc to HTML and saves the result to the file README.html in the same directory.
The name of the generated HTML file is derived from the source file by changing its file extension to .html.
$ asciidoctor README.adoc
You can control the Asciidoctor processor by adding various flags and switches, which you can learn about using:
$ asciidoctor --help
For instance, to write the file to a different directory, use:
$ asciidoctor -D output README.adoc
The asciidoctor man page provides a complete reference of the command line interface.
Refer to the following resources to learn more about how to use the asciidoctor command.
To use Asciidoctor in your application, you first need to require the gem:
require 'asciidoctor'You can then convert an AsciiDoc source file to an HTML file using:
Asciidoctor.convert_file 'README.adoc', to_file: true, safe: :safe|
|
When using Asciidoctor via the API, the default safe mode is :secure.
In secure mode, several core features are disabled, including the include directive.
If you want to enable these features, you’ll need to explicitly set the safe mode to :server (recommended) or :safe.
|
You can also convert an AsciiDoc string to embeddable HTML (for inserting in an HTML page) using:
content = '_Zen_ in the art of writing https://asciidoctor.org[AsciiDoc].'
Asciidoctor.convert content, safe: :safeIf you want the full HTML document, enable the header_footer option as follows:
content = '_Zen_ in the art of writing https://asciidoctor.org[AsciiDoc].'
html = Asciidoctor.convert content, header_footer: true, safe: :safeIf you need access to the parsed document, you can split the conversion into discrete steps:
content = '_Zen_ in the art of writing https://asciidoctor.org[AsciiDoc].'
document = Asciidoctor.load content, header_footer: true, safe: :safe
puts document.doctitle
html = document.convertKeep in mind that if you don’t like the output Asciidoctor produces, you can change it! Asciidoctor supports custom converters that can handle converting from the parsed document to the generated output.
One easy way to customize the output piecemeal is by using the template converter. The template converter allows you to supply a Tilt-supported template file to handle converting any node in the document.
However you go about it, you can have 100% control over the output. For more information about how to use the API or to customize the output, refer to the user manual.
New contributors are always welcome! If you discover errors or omissions in the source code, documentation, or website content, please don’t hesitate to submit an issue or open a pull request with a fix.
Here are some ways you can contribute:
-
by using prerelease (alpha, beta or preview) versions
-
by reporting bugs
-
by suggesting new features
-
by writing or editing documentation
-
by writing code with tests — No patch is too small.
-
fix typos
-
add comments
-
clean up inconsistent whitespace
-
write tests!
-
-
by refactoring code
-
by fixing issues
-
by reviewing patches
The Contributing guide provides information on how to create, style, and submit issues, feature requests, code, and documentation to the Asciidoctor Project.
Asciidoctor is developed to help you easily write and publish your content. But we can’t do it without your feedback! We encourage you to ask questions and discuss any aspects of the project on the discussion list, on Twitter or in the chat room.
- Chat (Gitter)
-
- Discussion list (Nabble)
-
#asciidoctor hashtag or @asciidoctor mention
Further information and documentation about Asciidoctor can be found on the project’s website.
The Asciidoctor organization on GitHub hosts the project’s source code, issue tracker, and sub-projects.
- Source repository (git)
- Issue tracker
- Asciidoctor organization on GitHub
Copyright © 2012-2020 Dan Allen, Sarah White, Ryan Waldron, and the individual contributors to Asciidoctor. Use of this software is granted under the terms of the MIT License.
See the LICENSE for the full license text.
Asciidoctor is led by Dan Allen and Sarah White and has received contributions from many individuals in Asciidoctor’s awesome community. The project was initiated in 2012 by Ryan Waldron and based on a prototype written by Nick Hengeveld.
AsciiDoc was started and maintained by Stuart Rackham from 2002 to 2013 and has received contributions from many individuals in the AsciiDoc community.
Refer to the CHANGELOG for a complete list of changes in older releases.