It would probably be best to do a git repo for the markup components, and have the rest in svn. We currently overload the website with tons of non-markup to take advantage of github pages hosting, we don't need to keep doing that, so some of the site shouldn't be going through jekyll going forward, just the markdown/templates.
It would be best now that we have hosting to properly build/host the javadoc on apache, so navigation is consistently on the same domain. On Tue, May 7, 2013 at 11:29 AM, David Nalley <[email protected]> wrote: > On Tue, May 7, 2013 at 2:15 PM, Andrew Phillips <[email protected]> > wrote: > > Are there any specific requirements with regard to an audit trail for > > changes to the site? > > > > Do we need to be able to show commit logs etc. too, or is it OK to have > > those in GitHub and regard the Apache site as the hosting location for > the > > Jekyll-generated HTML, which would be (over-)written on every merge..? > > > > +1 on the idea of running this via Jekyll. Could/should we be using > Apache > > CI infrastructure to do this, or is CloudBees OK (for now)? > > > > ap > > Website requires svn (long story, but basically, svnpubsub is > required). Jekyll should be fine as a build tool (Olamy or Suresh, > feel free to correct me) - so you could theoretically do a svn->git > replication, but no real way of escaping svn for the website. > > --David >
