The tools that I have been using in projects and $work are:
- Hugo for static site; migrating my own site, Apache Jena is on hugo, and I
helped migrating Apache SIS and some OGC sites. Hugo is really fast comparing
to Jekyll, and Markdown.
- sphinx; using it for Python libraries and tools, usef
The OpenNLP developer documentation looks nice and integrates in the build
nicely, but editing it can be a bit of a chore since it is XML documents.
Does anyone have any suggestions of other documentation tools that can fit
nicely in our build but be a little bit more developer-friendly? I don't
m
unsubscribe
On Tue, Sep 2, 2014 at 10:25 AM, Jörn Kottmann wrote:
> The HOWTO you found explains on how to update our website,
> but the documentation is build using docbook and can be found in
> opennlp-docs.
>
> https://github.com/apache/opennlp/tree/trunk/opennlp-docs
>
> The file for the pa
The HOWTO you found explains on how to update our website,
but the documentation is build using docbook and can be found in
opennlp-docs.
https://github.com/apache/opennlp/tree/trunk/opennlp-docs
The file for the parse can be found here:
https://github.com/apache/opennlp/blob/trunk/opennlp-docs/
Hi,
I have written some documentation to address issues 690 and 219. I had
already change the team list when I started as a committer but now
when I have looked to include such documentation in the opennlp-site
some doubts have risen:
1. I cloned https://svn.apache.org/repos/asf/opennlp/site/trun
