[
https://issues.apache.org/jira/browse/FLINK-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269188#comment-14269188
]
Max Michels commented on FLINK-1370:
------------------------------------
I agree, an automated build script would be a much more convenient way to
publish the latest website. It could be triggered nightly or even on a commit
basis. If we don't want to use the ASF infrastructure I would recommend Jekyll.
GitHub just published a nice blog post on their set up.
https://github.com/blog/1939-how-github-uses-github-to-document-github
> Build website automatically
> ---------------------------
>
> Key: FLINK-1370
> URL: https://issues.apache.org/jira/browse/FLINK-1370
> Project: Flink
> Issue Type: Task
> Components: Project Website
> Reporter: Robert Metzger
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> We currently use a super slow SVN repository with 17k files to publish our
> website.
> Almost all files in the repository are generated (javadocs, documentation for
> the different releases).
> It would be nice to use the SVN repository to really only host the markdown
> files and let a script generate the rest.
> To figure this out, we either use something within the ASF infra or come up
> with our own solution.
> Something worth looking into might be this:
> http://www.apache.org/dev/cmsref.html#external-build
> What I would personally prefer would be an automated nightly update of the
> website with the latest SNAPSHOT version for the documentation and javadocs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
