Installer asciidoctor avec Homebrew, apk, apt, MacPorts, Nix, pacman, dnf

Liens du projet

• Page d'accueil
• Dépôt
• Page du gestionnaire de paquets

Commandes et alias

• asciidoctor
• asciidoctor-pdf

Historique du projet

The official history traces Asciidoctor to GitHub's need to process AsciiDoc in Ruby for the GitHub application and git-scm.com documentation. GitHub was removing AsciiDoc.py-based rendering because of security and subprocess concerns, while a Ruby implementation had started for the Git website.

Nick Hengeveld made the first `asciidoc.rb` prototype commit for git-scm.com on 2012-04-03. Ryan Waldron made the first Asciidoctor commit on 2012-06-01 using that prototype lineage, and the first Asciidoctor gem release followed on 2012-06-14. In January 2013, GitHub re-enabled AsciiDoc rendering using Asciidoctor instead of AsciiDoc.py, and the project moved to the asciidoctor organization.

Dan Allen took project leadership in April 2013. The project quickly grew beyond the Ruby gem: AsciidoctorJ, Maven and Gradle plugins, Asciidoctor.js, Diagram, PDF, EPUB3, browser preview, and other tooling appeared in the official timeline. Asciidoctor 1.5.0 in 2014 introduced a modernized AsciiDoc syntax, and Asciidoctor 2.0.0 was released in March 2019.

Historique d'adoption

Asciidoctor's adoption story is unusually explicit in the official history: it preserved GitHub repository rendering for AsciiDoc in 2013, powered git-scm.com documentation, crossed into JVM and JavaScript environments, and reached one million RubyGems downloads by November 2016 and ten million by December 2020.

The current docs describe distribution through RubyGems, Docker images, numerous Linux distribution packages, Homebrew, and MacPorts. The input package facts confirm packaging in Homebrew, Alpine, Debian, Fedora as rubygem-asciidoctor, MacPorts, Nix, Arch, and Ubuntu.

Modes d'utilisation

The primary CLI is `asciidoctor`; users run `asciidoctor document.adoc` to produce HTML by default, or select converters and options for HTML5, DocBook, man pages, custom stylesheets, safe modes, extensions, and API-driven conversion. The same core can be used from Ruby, via AsciidoctorJ on the JVM, or via Asciidoctor.js in JavaScript and browser tooling.

Pourquoi les passionnés de paquets s'y intéressent

Asciidoctor matters to package nerds because it is both a replacement for a security-sensitive legacy processor and a multi-runtime documentation platform. It touches Ruby gems, Linux distro packages, Homebrew, MacPorts, Docker, Maven, Gradle, browser extensions, and JavaScript packages, while serving as the practical reference for a markup language used to build docs, books, man pages, and websites.

Chronologie

• 2012-04-03: First asciidoc.rb prototype commit for git-scm.com.
• 2012-06-01: First Asciidoctor commit by Ryan Waldron.
• 2012-06-14: First Asciidoctor gem release, 0.0.1.
• 2013-01-17: GitHub re-enables AsciiDoc rendering using Asciidoctor.
• 2013-04-16: Project leadership transfers to Dan Allen.
• 2013-04-25: First Asciidoctor release by Dan Allen, 0.1.2.
• 2014-08-12: Asciidoctor 1.5.0 released with modernized AsciiDoc syntax.
• 2016-11-26: Asciidoctor gem reaches over one million downloads.
• 2019-03-22: Asciidoctor 2.0.0 released.
• 2020-12-13: Asciidoctor gem reaches over ten million downloads.

Related projects

• AsciiDoc.py is the legacy Python processor Asciidoctor succeeded.
• AsciidoctorJ runs Asciidoctor on the JVM and underpins Maven, Gradle, and Java integrations.
• Asciidoctor.js transpiles the Ruby source to JavaScript for browser, Node.js, and editor-preview use.
• Asciidoctor PDF, EPUB3, Diagram, reveal.js, and related extensions expand output formats and authoring workflows.

Sources

• https://docs.asciidoctor.org/about/history/
• https://docs.asciidoctor.org/asciidoctor/latest/
• https://docs.asciidoctor.org/asciidoctor/latest/cli/
• https://github.com/asciidoctor/asciidoctor