Hey, I'm not really suggesting one over the other. With the maven-site-approach we could do all together.
Chris ________________________________ Von: Josh Tynjala <joshtynj...@gmail.com> Gesendet: Sonntag, 2. Oktober 2016 22:43:13 An: dev@flex.apache.org Betreff: Re: AW: [DISCUSS] Switch the site repo to GIT? It is also possible to use ``` for a code block in markdown. No indentation required. You can also specify the language. ``` actionscript code ``` - Josh On Oct 2, 2016 2:54 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: > Well they couldn't give me much info on what others are using, but I dug a > little myself. > > So it seems that they use Jekyl to convert Markdown into HTML. There > however is a plugin to use Asciidoctor to do the same. > > > Having used both Asciidoctor and Markdown, I think Asciidoctor is far more > superior when it comes to features. Especially when it comes to the syntax, > I don't quite like how easy it is to mess up a Markdown file. > > > Just as an example: If you want to output some code, in MD you have to > prefix every line of code with four spaces, in adoc you put it in between > two "-----" blocks. > > Lists in MD require you to separate each line with two spaces: > > * first level > > * first level > > * second level > > > In adoc this is: > > * first level > > * first level > > ** second level > > > Markdown does a lot with spaces and Asciidoc does the same with > duplicating the important chars. Duplicating important chars doesn't get > messed up by the line indenting of IDEs. > > > So how about me investigating how to produce gitpages with asciidoc and > having these replace the ApacheCMS pages? > > > Do we have any special stuff in the CMS or is all just static? > > > Chris > > ________________________________ > 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. > >
