Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltaspike-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jeanouii@gmail.com designates
 209.85.161.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <D3D66175-2CFA-4E23-9238-C4031354EC02@gmail.com>
References: <D3D66175-2CFA-4E23-9238-C4031354EC02@gmail.com>
Date: Wed, 25 Jul 2012 09:30:09 +0200
Message-ID: 
 <CAGFtjw3P1aoPSrtCZQ8+XirHqFe4wtzF6ZQW-tg=nYSWTsw+GQ@mail.gmail.com>
Subject: Re: CMS Info
From: Jean-Louis MONTEIRO <jeanouii@gmail.com>
To: deltaspike-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d042f9eb0df792e04c5a272b7

--f46d042f9eb0df792e04c5a272b7
Content-Type: text/plain; charset=ISO-8859-1

+1, as soon as the perl is up, that's pretty cool to get the site updated
and up to date.
That's also easy to get external contributions on the documentation where
usually all projects are interested in.

Jean-Louis

2012/7/25 David Blevins <david.blevins@gmail.com>

> Reposting some info I mentioned on IRC wrt the CMS.
>
> Generally if you're ok with doing things page-at-a-time and keeping the
> markdown, asciidoc or whatever source in svn, all can work fine.
>
> The CMS can keep the site up-to-date immediately after each commit of a
> source file (*.mdtext, *.asciidoc, etc.) with no need to write any of that
> yourself.
>
> So if you can handle this dance:
>
>   CMS: this foo-formatted page changed, turn it into html, please
>   You: ok, one sec, here it is
>
> Then the CMS is golden.  The "ok, one sec, here it is" is done with a perl
> function of your creation.  That perl function can easily call out to
> anything else for the actual generation.  Infra definitely prefers all be
> done in perl, but a hard stance hasn't been made.
>
> Generating an entire site and push all the files, some changed and some
> not, is going against the grain.  It's not in the small tweak category, but
> in the by-passing huge parts of the CMS and doing nearly everything
> yourself.  You don't need to go to this great length just to use an
> alternate input source format than what the CMS currently handles.
>
> This doc recaps the above, gives a little bit of the "how" then goes into
> great detail on the "how".  I recommend reading at least part of it to get
> a better idea.
>
>  - http://www.apache.org/dev/cmsref.html#control-flow
>
> Ushering the content from the markdown or asciidoc source to staging then
> to production is all done with svn hooks, so I don't think git is an option
> -- at least not for all of it.
>
> Not a complete view, but a better idea.  Markdown is what is supported
> "natively", but adding other formats really only takes a few lines of perl
> that calls out to something else.  The restriction being as mentioned:
>
>   - the source doc is svn
>   - the perl function takes one file as input and produces a "string" of
> generated html
>
> If you can do that, you can use whatever format you like and the CMS will
> do all the rest of the work and do it very well.
>
>
> -David
>
>

--f46d042f9eb0df792e04c5a272b7--