The stuff we use on Drill can be found here:
https://github.com/apache/drill/tree/gh-pages
It is simple and works pretty well. I like markdown's simplicity.
I feel like Todd had some substantial thoughts on this earlier (and chose
something over markdown for Kudu).
On Sun, May 8, 2016 at 5:07 P
For the central documentation I'm more in favor of asciidoc for its
seemingly stronger support of interconnected documents (for example,
O'Reilly has moved most of its authoring work to asciidoc from Docbook
XML). But there may be resources for Markdown that I'm not familiar
with. There are multipl
Sounds good. Javadoc is the tool for Java. :)
On Sat, May 7, 2016 at 9:44 AM, Uwe Korn wrote:
> Hello,
>
> as Arrow grows and we want to improve usage/adoption, we definitely need
> to start documenting it a bit. I would volunteer to work on writing some
> sections, but first we need to agree on
Hello,
as Arrow grows and we want to improve usage/adoption, we definitely need
to start documenting it a bit. I would volunteer to work on writing some
sections, but first we need to agree on the used tools. I would suggest
the following setup:
* central Arrow documentation (i.e. the layou
