Ok so I did a little searching:
It seems that in general if you setup a git repo and define an "asf-site" branch in that (of course have Infra register the repo in their system), stuff pushed to that branch is automatically published as website. I just tested it, the maven site plugin is able to produce html from: - APT (don't know that) - XDoc (don't know that) - Markdown - FML (don't know that) - Asciidoctor (After adding the plugin) So we could write our content in any of these formats. I found this very helpful page of a fellow Apache project [1]. They said, that Markdown had the advantage of allowing inline HTML. So I understand that this could be ideal for the parts of the site where we need detailed control over the HTML. Asciidoctor has the advantage of allowing more features (inline graphs and diagrams just to state one thing I really like). So this could be ideal for the parts where we need features over control of the HTML. So why not simply allow to use both? I have done some searching and I'd like to propose something: 1. We create a new git repo for the site 2. I setup a maven site project inside that 3. I configure the build to allow multiple types of content - Markdown (same as github pages) - Asciidoctor 4. I configure the build to deploy the site to the "asf-site" branch of the same repo 5. We have infra setup the gitpubsub system to stage that somewhere so we can test it 6. We do the Content migration, CSS, HTML fine tuning till we're happy with it 7. We make the new site the official site. Would that be an option? Chris [1] https://cwiki.apache.org/confluence/display/TRAFODION/Modify+Web+Site ________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Sonntag, 2. Oktober 2016 07:14:42 An: dev@flex.apache.org Betreff: Re: [DISCUSS] Switch the site repo to GIT? It is time to consider getting off of Apache CMS. I think some projects have done so already. I'd like to know more about what we lose/gain if we go way from Apache CMS. Some projects are experimenting with GitHub Pages. I think it should be considered as well. -Alex On 10/1/16, 9:11 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote: >Orher projects using git for the cms what are using? >Could we switch, for example, to a wordpress cms if we want? > > > >El sábado, 1 de octubre de 2016, Christofer Dutz ><christofer.d...@c-ware.de> >escribió: > >> Ok so it turns out that as long as we use the Apache CMS we can't change >> to GIT. Guess this was the reason for still being on GIT. >> >> >> I have no idea what we really need the CMS for, but as long as we need >> this, we seem to be stuck there :-( >> >> >> Chris >> >> ________________________________ >> Von: Alex Harui <aha...@adobe.com <javascript:;>> >> Gesendet: Donnerstag, 29. September 2016 18:56:39 >> An: dev@flex.apache.org <javascript:;> >> Betreff: Re: [DISCUSS] Switch the site repo to GIT? >> >> >> >> On 9/29/16, 1:43 AM, "Christofer Dutz" <christofer.d...@c-ware.de >> <javascript:;>> wrote: >> >> >Hi guys, >> > >> > >> >as you might know I have been working hard on the site-generation and >> >this finally seems to be working nicely. The only problem I have is >>that >> >I can't submit to the site repo from the Build agent as SVN isn't setup >> >to allow that. Git however is able to commit without hard-coding >> >credentials. Infra suggested to move our site to GIT to resolve this >> >issue. >> > >> > >> >I was wondering anyway why this is our only SVN repo. Wouldn't it be >>cool >> >to have everything in one type of repo? >> >> The fact our web site is on SVN isn't a big deal to me, but what is a >>big >> deal is 99% of the time I find the two-step staging/publish workflow >> really painful. Related, there is currently no way for the MD5 checker >>on >> the CI server to update the website automatically. If moving to Git >>gets >> us out of that, I'd be for it. Can you provide more info on how folks >>do >> staging when working on big overhauls and why Git doesn't have this >> credential issue? >> >> Thanks, >> -Alex >> >> > >-- > >Carlos Rovira >Director General >M: +34 607 22 60 05 >http://www.codeoscopic.com >http://www.avant2.es > > >Este mensaje se dirige exclusivamente a su destinatario y puede contener >información privilegiada o confidencial. Si ha recibido este mensaje por >error, le rogamos que nos lo comunique inmediatamente por esta misma vía y >proceda a su destrucción. > >De la vigente Ley Orgánica de Protección de Datos (15/1999), le >comunicamos >que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC >S.A. La finalidad de dicho tratamiento es facilitar la prestación del >servicio o información solicitados, teniendo usted derecho de acceso, >rectificación, cancelación y oposición de sus datos dirigiéndose a >nuestras >oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación >necesaria.