[jira] [Commented] (OAK-936) Incorporate Oak documentation into the Oak website

["Jukka Zitting (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726360#comment-13726360 ] 

Jukka Zitting commented on OAK-936:
-----------------------------------

I'm not too excited about the CI build approach, given how the ASF web infrastructure works. I've tried setting up and maintaining such site builds on a few projects, but it always ends up being a more trouble than it's worth given the various security constraints (site must be in svn, but one shouldn't store svn credentials on a CI server, etc.).

Instead I'd rather just use static files, possibly with something like [strapdown.js|http://strapdownjs.com/] for rendering. That way a documentation update can be deployed simply by committing the changes.
                
> 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