- Article (
The default doctype. In DocBook, includes the appendix, abstract, bibliography, glossary, and index sections. Unless you are making a book or a man page, you don’t need to worry about the doctype. The default will suffice.
- Book (
Builds on the article doctype with the additional ability to use a top-level title as part titles, includes the appendix, dedication, preface, bibliography, glossary, index, and colophon. There’s also the concept of a multi-part book, but the distinction from a regular book is determined by the content. A book only has chapters and special sections, whereas a multi-part book is divided by parts that each contain one or more chapters or special sections.
- Man page (
Used for producing a roff or HTML-formatted manual page (man page) for Unix and Unix-like operating systems. This doctype instructs the parser to recognize a special document header and section naming conventions for organizing the AsciiDoc content as a man page. See Generate Manual Pages from AsciiDoc for details on how structure a man page using AsciiDoc and generate it using Asciidoctor.
- Inline (
There may be cases when you only want to apply inline AsciiDoc formatting to input text without wrapping it in a block element. For example, in the Asciidoclet project (AsciiDoc in Javadoc), only the inline formatting is needed for the text in Javadoc tags.
The rules for the inline doctype are as follows:
Only a single paragraph is read from the AsciiDoc source.
Inline formatting is applied.
The output is not wrapped in the normal paragraph tags.
Given the following input:
https://asciidoctor.org[AsciiDoc] is a _lightweight_ markup language...
Processing it with the options
<a href="https://asciidoctor.org">AsciiDoc</a> is a <em>lightweight</em> markup language…
The inline doctype allows the AsciiDoc processor to cover the full range of applications, from unstructured (inline) text to full, standalone documents!