[
https://issues.apache.org/jira/browse/OAK-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726398#comment-13726398
]
Michael Dürig commented on OAK-936:
-----------------------------------
bq. I'm not too excited about the CI build approach
Scrap that the CI idea.
The approach I'm trying out uses the site plugin to build html files from the
markdown files in {{oak-doc}} and then commit them to our web site. Every
committer should be able to use that without additional fiddling with the
credentials. I'll follow up on OAK-301.
> 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
