taverna-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stian Soiland-Reyes <st...@apache.org>
Subject Re: [jira] [Commented] (TAVERNA-870) Move Taverna website away from SVN and cms.apache.org?
Date Thu, 27 Aug 2015 10:35:35 GMT
No, that has been discussed on the community@ list, but dismissed as ASF do
not want to rely on third-party controlled hosting. Imagine we did this for
hundred projects, and then Github turned evil and wanted lots of moneys
from ASF.

However, we can have a very similar way to edit our web pages, except that
we have to do the build ourselves (e.g. "compile" markdown+template to
HTML).

The advantage of the current cms.Apache.org system is that you do not need
to build anything locally, and so do not need to install anything special
to edit the webpages.

However the web UI of cms, and the alternate direct SVN access, is quite
awkward to use for changes like restructuring or accepting patches via
Github.

So I looked briefly at two potential build system, maven-site-plugin, and
Jekyll. Maven option just needs Maven, which we should all have, while
Jekyll requires Ruby and various libraries, we would probably need to cook
instructions for doing so with rvm/bundle or Docker to get those in
consistent versions.

In both cases you would:

1) check out website source (currently svn, we can move this to a
standalone git repo)
2) edit markdown files and/or templates
3) commit+push to website source (this does not make it live)
4) build with mvn/Jekyll
5) check results locally
6) push built HTML to www repository to make live (currently SVN, this can
also be made a git repo, possible the same as web source, but different
folder or branch)

With the Maven route there are reasonable default templates, but not as
much design flexibility as with Jekyll. However with Jekyll most existing
templates are kind of hip and cool startup-like, and we would probably have
to customise this more, e.g. for the menu.

Jekyll is what Github Pages uses, so the MarkDown dialect would be better
known. I believe variation is not substantial though, it is mainly just a
different way to organise the source and templates.
On 14 Aug 2015 17:40, "Alan Williams" <alaninmcr@googlemail.com> wrote:

> Hello Stian,
>
> I'm confused as to what is being proposed. Will be be like a "normal"
> github repository where the gh-pages branch is editable and sits behind the
> myrepo.github.io site?
>
> Alan
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message