[
https://issues.apache.org/jira/browse/OAK-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729362#comment-13729362
]
Thomas Mueller commented on OAK-936:
------------------------------------
The mvn site approach is fine with me. Just a few thought about alternatives:
* strapdown.js: it's an interesting idea, however I'm not quite sure if the
claim they make about "Search-engine friendly" is really true... Does anybody
know the details?
* [TiddlyWiki|http://en.wikipedia.org/wiki/TiddlyWiki] - each document would be
its on wiki.
* Edit the raw html. This is what I usually do. It avoids having to learn
another markup language (assuming you know HTML). There are a few
disadvantages, but in my view they are not major (lack of templating; HTML is a
bit verbose).
> Incorporate Oak documentation into the Oak website
> --------------------------------------------------
>
> Key: OAK-936
> URL: https://issues.apache.org/jira/browse/OAK-936
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: doc
> Reporter: Michael Dürig
>
> We should incorporate the [Oak documentation |
> https://github.com/apache/jackrabbit-oak/tree/trunk/oak-doc] into the [Oak
> web site | http://jackrabbit.apache.org/oak/].
> Optimally we make this part of our CI and release infrastructure. Each CI
> build would deploy the latest snapshot build of oak-doc to
> http://jackrabbit.apache.org/oak/docs/nightly. Each release would deploy a
> build of oak-doc to http://jackrabbit.apache.org/oak/releases/oak-doc-X.Y
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
