[
https://issues.apache.org/jira/browse/JCR-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486716#comment-14486716
]
Chetan Mehrotra commented on JCR-3865:
--------------------------------------
bq. note that the site only updates the 'jackrabbit/site/live/jcr' directory.
handling the entire site is very slow, since scm-publish checks out the entire
tree.
In Oak I avoid doing the complete checkin by first running the build with
{{-Dscmpublish.skipCheckin=true}} and then just checkin in the changed html
files. But yes it still has the drawback of checking out whole site which might
be slow
> Use markdown to generate Jackrabbit Site
> ----------------------------------------
>
> Key: JCR-3865
> URL: https://issues.apache.org/jira/browse/JCR-3865
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: docs
> Reporter: Tobias Bocanegra
> Assignee: Tobias Bocanegra
> Priority: Minor
>
> The current jackrabbit site is nor well maintained, mainly because we need to
> edit directly the HTML. most of the content is already available as markdown.
> goal is to automate the site generation via maven and svn pubsub.
> 1. phase is to reuse the same template/skin as in oak and to get the content
> right.
> 2. phase is to beautify it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
