[
https://issues.apache.org/jira/browse/PARQUET-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963045#comment-16963045
]
Uwe Korn commented on PARQUET-1686:
-----------------------------------
In Arrow we are using Jekyll with Github Actions to automatically deploy our
site:
[https://github.com/apache/arrow-site/blob/master/.github/workflows/deploy.yml]
> Automate site generation
> ------------------------
>
> Key: PARQUET-1686
> URL: https://issues.apache.org/jira/browse/PARQUET-1686
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-site
> Reporter: Gabor Szadovszky
> Priority: Major
> Labels: documentation
>
> We moved our site source to [github|https://github.com/apache/parquet-site].
> It is much better than svn but still not working as it should. Currently, we
> have to generate the site manually before checking in. It would be much
> better if the site generation would be automatic so we can simply accept PRs
> on the source files.
> One option to achieve this is the [Pelican CMS
> System|https://blog.getpelican.com/] as described at [.asf.yaml features for
> git
> repositories|https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-StaticwebsitecontentgenerationviaPelicanCMS].
> Not sure if this is the best solution though. Another solution might be to
> trigger a jenkins build for the changes on master and after generating the
> site with middleman commit the files to the branch asf-site.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
