Great work. Thanks Zoran. On Wed, Oct 31, 2018 at 10:49 AM Nicola Ferraro <[email protected]> wrote:
> That's nice Zoran. I think it's a good first step is to have something that > is displayed on the web, so that we can iterate. > > It would be technically possible to have both websites persisted on master, > so that we just swap them when the new one is ready? > > Nicola > > On Wed, Oct 31, 2018 at 7:15 AM Francois Papon < > [email protected]> > wrote: > > > Hi, > > > > It's great, thanks Zoran! > > > > I can take a look about the breaking CSS and links. > > > > I'm sorry, I was very busy this month and I could not work on the website > > :( > > > > It would be better now! > > > > regards, > > > > François Papon > > [email protected] > > > > Le 30/10/2018 à 17:04, Zoran Regvart a écrit : > > > Hi Tadayoshi & Cameleers, > > > so the staging site now works* it's at: > > > > > > https://camel.apache.org/staging/ > > > > > > *and by that I mean: the content of camel-website's asf-site branch is > > > published there. It is pretty much broken at the moment, CSS and links > > > are generated with absolute values, I need to take a look and make > > > them relative so that the website can be nested in that /staging > > > directory. > > > > > > zoran > > > > > > On Tue, Oct 30, 2018 at 11:40 AM, Zoran Regvart <[email protected]> > > wrote: > > >> Hi Tadayoshi, > > >> I'm really sorry I had little time to look into this, the process > > >> should look like this: > > >> > > >> We make changes on the camel.git gitbox repository (or GitHub mirror) > > >> to the `website` branch (till it's merged over to `master`), Jenkins > > >> builds the website (Jenkinsfile on `website` branch does this[1]) and > > >> pushes to the camel-website.git repository's `asf-site` branch. Then a > > >> script provided by the INFRA[2] should sync with the website's > > >> /staging directory. > > >> > > >> I think we need a `asf-site-staging` and a `asf-site` branches on > > >> `camel-website.git` repository and a way to merge from one repository > > >> to the other (Jenkins job?), but let's make some smaller steps first. > > >> > > >> zoran > > >> > > >> [1] > > > https://gitbox.apache.org/repos/asf?p=camel.git;a=blob;f=Jenkinsfile;h=f094a624332bed955c686ec4a9951aeaa004c258;hb=refs/heads/website#l47 > > >> [2] https://issues.apache.org/jira/browse/INFRA-15969 > > >> > > >> On Tue, Oct 30, 2018 at 9:59 AM, Tadayoshi Sato > > >> <[email protected]> wrote: > > >>> Hi all, > > >>> > > >>> I've been working on migrating docs, and while there are still a > > number of > > >>> pages to be migrated yet it's also becoming in good shape. I think > it's > > >>> good time to host the docs somewhere so that everyone can read and > > further > > >>> contribute to the site. > > >>> > > >>> I'm aware that recently Francois and Zoran worked on doc site > > generation > > >>> and https://github.com/apache/camel-website. Is it currently > > accessible > > >>> online? Can we publish the static site somewhere like GH Pages, > > surge.sh, > > >>> or Netlify? > > >>> > > >>> The docs are already available on GH as asciidoc but the problem is > > that > > >>> links of reference style i.e. <<jms-component,JMS>> do not work on > the > > >>> plain GH. I believe we need some place where those reference style > > links > > >>> are also rendered. > > >>> > > >>> Best regards, > > >>> Tadayoshi > > >> > > >> > > >> -- > > >> Zoran Regvart > > > > > > > > > > >
