Skip to content

Home

Jump to bottom Edit New page
Sarah White edited this page Mar 30, 2015 · 9 revisions

Documentation IA

Asciidoctor Toolchain

So to get all the docs in some sort of flow that is actually based on a user’s reality (and therefore useful to them), we need to do two things in tangent.

  1. Make a list of all of the parts of the Asciidoctor toolchain.

  2. Make a list of the different types/stages of Asciidoctor users.

Here’s my first attempt at these two list:

Asciidoctor Toolchain

  • Core

    • Syntax

    • Parser

    • AST

  • Viewing Tools

    • Docgist

    • Firefox Plugin

    • Chrome Plugin

    • Guard with Live Reload

  • Editing Tools

    • Brackets

    • Atom

  • Converters

    • HTML

    • PDF

    • EPUB

    • DocBook

    • Latex

    • Reveal

    • DZSlides

    • fopub (archived)

    • Stylesheets

      • Custom styles per converter

  • Diagrams and Equations

    • PlantUML

    • Ditaa

    • Shaape

    • BlockDiag, SeqDiag, ActDiag, NwDiag

    • GraphViz DOT

  • Asciidoclet

  • Plugins

    • Gradle

    • Maven

    • Gulp

    • Grunt

    • Leiningen

    • Ant

    • sbt

    • Intellij

    • Eclipse (in progress)

  • Implementations

    • Ruby (Core)

    • Java

    • JavaScript

    • GroovyDSL

  • Web Publishing

    • Confluence

    • Jekyll

  • Docker Container

    • Asciidoctor

    • AsciidoctorJ

  • Distributions

    • RubyGems

    • Debian

    • Fedora

  • Organization infrastructure

    • Doctest Suite

    • html-pipeline (infrastructure for GitHub)

    • RPM package spec

    • webjars

Add a custom footer
Add a custom sidebar
Clone this wiki locally