[
https://issues.apache.org/jira/browse/TAVERNA-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680285#comment-14680285
]
Stian Soiland-Reyes commented on TAVERNA-870:
---------------------------------------------
Exampes of projects using Jekyll and publishing directly to:
https://github.com/apache/orc/blob/master/site/BUILD.md
https://github.com/apache/drill/tree/gh-pages-master
One downside I found with Jekyll is that you need to install ruby, rvm etc..
and then there's potential versioning issues. I have not got much experience
beyond Github Pages.
Using Jekyll can give compatibility with github pages (e.g. using gh-pages
branch), e.g.with previews like http://apache.github.io/drill/ is good - but
also a bit confusing perhaps?
> Move Taverna website away from SVN and cms.apache.org?
> ------------------------------------------------------
>
> Key: TAVERNA-870
> URL: https://issues.apache.org/jira/browse/TAVERNA-870
> Project: Apache Taverna
> Issue Type: Bug
> Components: Website
> Reporter: Stian Soiland-Reyes
> Assignee: Stian Soiland-Reyes
>
> While having the Github mirroring at
> https://github.com/apache/incubator-taverna-site is great for contributors
> (thanks Gale and Dennis!) - merging those pull requests against the SVN is
> quite a bit of a pain - I've actually had to do it by manual copy and paste.
> The system at https://cms.apache.org/taverna/ is not quite fit for purpose as
> it is very close to SVN, and frequently has issues such as not being updated.
> The build system is tricky to figure out. While we have been able to tweak
> the templates etc - I am now actually not understanding it myself anymore
> when trying to modify the menu bars.
> The SVN-based web publishing and cms.apache.org will at some point be
> deprecated by ASF INFRA (or so is the rumour) - and git-based websites are
> already available:
> https://blogs.apache.org/infra/entry/git_based_websites_available
> The new git-based system is basically "Write HTML files to git, they are
> immediately live" - so no more staging area or "web-based" editing.
> This git-based system seem however seem to require that you do any kind of
> building yourself, e.g. to convert Markdown to HTML and to apply templates
> with common menus.
> Would it be worth re-examining the options here? E.g. Jekyll or Maven Site or
> something else?
> As an example - http://commonsrdf.incubator.apache.org/ is built with Maven
> Site and published through SVN
> from https://github.com/apache/incubator-commonsrdf/tree/master/src/site with
> stuff inherited from Apache Commons poms and styles. There's quite a
> reduction in flexibility - but deploying that website is simply "mvn clean
> site scm-publish:publish-scm" and provide the SVN password. I will imagine
> this would work the same way with a git backend, although that has not been
> tested.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
