When comparing DokuWiki vs AsciiDoc, the Slant community recommends AsciiDoc for most people. In the question“What are the best markup languages?” AsciiDoc is ranked 4th while DokuWiki is ranked 9th. The most important reason people chose AsciiDoc is:
The formatting of Asciidoc is standardized so there is only one 'flavor' unlike in Markdown. The definitive user guide is [here](http://asciidoctor.org/docs/asciidoc-writers-guide/).
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy to set up and mantain
To install you need a webserver running PHP 5.2 or later where you unpack the downloaded archive and navigate to install.php in your browser, fill out the necessary information required for the one-page installer and you are done.
Pro Local and open source
Local...
Pro Plain-text file storage
Dokuwiki does not require a database, it stores everything in plain-text.
Pro Version control
Dokuwik offers unlimited page revisions.
Pro Access control
DokuWiki has built-in ACL support.
Pro Runs on any PHP server
It requires a webserver running PHP 5.2 or later of any kind.
Pro A dedicated page for recent changes
A dedicated page to quickly note what has changed recently can be set up.
Pro Search functionality
DokuWiki allows searching through pages.
Pro Very last, consuming very few Local
Local....
Pro Good selection of plugins
DokuWiki offers over a thousand plugins to extend its functionality.
Pro Good selection of themes
DokuWiki offers over a hundred templates to change the visual appearance of the site.
Pro Standardized format
The formatting of Asciidoc is standardized so there is only one 'flavor' unlike in Markdown. The definitive user guide is here.
Pro Human-readable
Simple, easy-to-read style similar to Markdown. Designed to be easy for a human to enter with a simple text editor, and easy to read in its raw form.
Pro Technical Documentation
The DocBook format which Asciidoctor can convert to was originally developed with the creation of computer books in mind and thus has a rich array of formatting options which are powerful enough to manage the formatting of lengthy technical books.
Pro Supported by GitHub and GitLab
Both GitHub and GitLab support AsciiDoc syntax in repositories, wikis and Gists/Snippets (powered by the Asciidoctor Ruby gem).
Pro It's structured
Cleanly transforms to DocBook and HTML5.
Pro Supports semantic markup
Pro Native support for colored output
AsciiDoc has offered the ability to define both the color of any text output as well as its background, almost since its inception. It accepts several standard chromatic notations for them, too, including hexadecimal and decimal RGB values, decimal HSL and named CSS.
Pro Embedded metadata
The AsciiDoc standard defines a number of metadata values which can be defined inside a document primarily for contextual purposes that aren't rendered in its standard output such as author, date, license, document title and version, etc. These can be especially useful when searching through a large number of files/documents or documenting the evolution of one as part of a larger codebase.
Pro Shorter, more concise than Markdown
Pro Good tool support
There are plugins to support editing AsciiDoc for many editors/IDEs.
Cons
Con Lots of plugins to manage
DokuWiki is highly modular. Even thing like WYSIWYG editors and categories have to be added separately as plugins. This can quickly lead to managing lots of plugins.
Con Not as popular/widely used as Markdown
The Asciidoc format is not as popular/widely used as Markdown. Notwithstanding the foregoing, Asciidoc is used for some of the following projects:
- O'Reilly and Maker Press
- NFJS, the magazine
- other examples
Con Limited output options
Asciidoctor can only convert directly to HTML or DocBook. However, you can always use another converter such as pandoc to convert from one of the output formats to another format.