Generated documentation from code

[bertfrees]

API documentation

• [doing] javadoc
• [doing] xprocdoc
• xsl-doc
  • we should move to XSLT 3.0 first
• CSS
• liblouis tables

generated script documentation

• to do: group script option (similar to Group options on job creation page into content panes pipeline-webui#53)

htmlized sources

i.e. grepcode-like documentation of source code

• done for XProc, XSLT, CSS, catalog.xml
• to do: for Java (possibly with maven-jxr-plugin)
• to do: braille CSS support for Coderay

[bertfrees]

@josteinaj I have added the clientlib-java javadocs to the website: http://daisy.github.io/pipeline/Contribute.

Is this how it is supposed to look? Is there some specific entrypoint we should point to? org.daisy.pipeline.client.http.WS maybe? Are there some packages/classes we should hide from the user? (If we have a single entry point, all classes that can not be reached from that entrypoint should ideally be hidden.)

Note that I haven't linked up the two modules (clientlib-java and clientlib-java-httpclient) yet so you can't go e.g. from WS to Job.

[josteinaj]

Looks good! WS could be emphasized, yes. I can't think of anything in specific that needs to be hidden.

Linking up the two JavaDocs would be useful.

[bertfrees]

Done.