On 14 February 2012 17:08, Joe Schaefer <joe_schae...@yahoo.com> wrote: > ----- Original Message ----- > >> From: Joe Schaefer <joe_schae...@yahoo.com> >> To: "general@incubator.apache.org" <general@incubator.apache.org> >> Cc: >> Sent: Tuesday, February 14, 2012 12:04 PM >> Subject: Re: migrating the main site to the CMS- a simple approach >> >>> ________________________________ >>> From: sebb <seb...@gmail.com> >>> To: general@incubator.apache.org >>> Sent: Tuesday, February 14, 2012 11:57 AM >>> Subject: Re: migrating the main site to the CMS- a simple approach >>> >>> On 14 February 2012 16:21, Joe Schaefer <joe_schae...@yahoo.com> >> wrote: >>>> So I realize that I don't have enough time myself >>>> to convert the incubator site's content to markdown >>>> even tho there are scripts to automate that process. >>>> Instead let me offer a different idea- to keep the >>>> existing build system but superimpose the CMS on top >>>> of it. >>> >>>> To facilitate this, all that needs to happen is for >>>> someone to find a generic way of invoking anakia so >>>> it satisfies the command-line interface of >>>> >>>> https://svn.apache.org/repos/infra/websites/cms/build/build_external.pl >>>> >>>> (ie builds sources from ./content/ into a specified target >>>> dir). >>> >>> That's not actually sufficient to build the main Incubator site, >>> because it does not take the Clutch updates into account. >>> >>> However, I guess Clutch could be run separately to update the source >>> files, and then trigger a site rebuild. > > Alternately, if the clutch builds simply modify source content,
Yes, that's all it does. > that aspect can be performed manually and the build system will > generate that content from the changes to the source content. > All someone would have to do in addition to what they already > already do now is publish the changes to the live site. However, the site build does a lot more than just run Anakia. It also runs XSLT and texen; each is run several times with different data. There are some other stages as well. This is all done by Ant, using the build.xml from the top-level directory. I suspect this is also true of a lot of other sites which use Anakia. >> >> >> Ideally the Clutch updates can be considered as "dynamic content" for >> the CMS, so we can simply schedule clutch builds on a periodic basis. >> That is done separately from the generic process of doing anakia builds. >> >> >>> >>>> By generic, I mean a suitable command-line invocation >>>> for the build_external.pl script for the "anakia" type >>>> (basically supplying the right @system_args in the script) >>>> so that pretty much any site currently using anakia will >>>> be able to do the same thing. >>>> >>>> Hopefully the challenge to produce such @system_args is >>>> within the means of this community ;-)- it amounts to >>>> 1 line of perl at this point. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
