[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930224#action_12930224
 ] 

Patrick Hunt commented on ZOOKEEPER-925:
----------------------------------------

We prolly wouldn't generate pdfs for the web site, no one seems to do that 
anymore (although it's possible if someone would want to do it explicitly for 
some reason)

We check in the source, that's a given.

We check in the generated site/docs for a reason as well. In forrest timeframe 
it was mainly due to the fact that using forrest is a pita. ;-) In maven that's 
less of a concern. For whirr we currently don't checkin the generated, but we 
are thinking of doing so to lower the bar for new users. Doesn't really matter 
much to me, we could try "not committing generated" first, then see if it's an 
issue.


> Consider maven site generation to replace our forrest site and documentation 
> generation
> ---------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-925
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-925
>             Project: Zookeeper
>          Issue Type: Wish
>          Components: documentation
>            Reporter: Patrick Hunt
>
> See WHIRR-19 for some background.
> In whirr we looked at a number of site/doc generation facilities. In the end 
> Maven site generation plugin turned out to be by far the best option. You can 
> see our nascent site here (no attempt at styling,etc so far):
> http://incubator.apache.org/whirr/
> In particular take a look at the quick start:
> http://incubator.apache.org/whirr/quick-start-guide.html
> which was generated from
> http://svn.apache.org/repos/asf/incubator/whirr/trunk/src/site/confluence/quick-start-guide.confluence
> notice this was standard wiki markup (confluence wiki markup, same as 
> available from apache)
> You can read more about mvn site plugin here:
> http://maven.apache.org/guides/mini/guide-site.html
> Notice that other formats are available, not just confluence markup, also 
> note that you can use different markup formats if you like in the same site 
> (although probably not a great idea, but in some cases might be handy, for 
> example whirr uses the confluence wiki, so we can pretty much copy/paste 
> source docs from wiki to our site (svn) if we like)
> Re maven vs our current ant based build. It's probably a good idea for us to 
> move the build to maven at some point. We could initially move just the doc 
> generation, and then incrementally move functionality from build.xml to mvn 
> over a longer time period.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to