I have been accumulating a few documentation inconsistencies over the past
several months and I wanted to finally fix them and contribute them back.
Last time I made any changes was in the old markdown repository. I am
referring to the documentation under the main project ( https://github.com/elasticsearch/elasticsearch/tree/master/docs) not the
new documentation repo (https://github.com/elasticsearch/docs).
How is the site asciidoc built? Since Github uses asciidoctor, I have tried
using it, but I cannot come up with a way to create the same directory
structure using the default stylesheets/templates, so there is obviously
more to building the documents that what is included in git. Or am I
missing something? My sole command line flag is ''-d book".
It seems I have misunderstood the intent of the new documentation repo and
it is indeed what I am looking for. I assumed it was the WIP elasticsearch
book. Asciidoc is fairly simple, not sure why this level of complexity is
needed.
Cheers,
Ivan
On Sat, Jan 11, 2014 at 12:01 PM, Ivan Brusic ivan@brusic.com wrote:
I have been accumulating a few documentation inconsistencies over the past
several months and I wanted to finally fix them and contribute them back.
Last time I made any changes was in the old markdown repository. I am
referring to the documentation under the main project ( https://github.com/elasticsearch/elasticsearch/tree/master/docs) not the
new documentation repo (https://github.com/elasticsearch/docs).
How is the site asciidoc built? Since Github uses asciidoctor, I have
tried using it, but I cannot come up with a way to create the same
directory structure using the default stylesheets/templates, so there is
obviously more to building the documents that what is included in git. Or
am I missing something? My sole command line flag is ''-d book".
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.