Hi,

To answer Bertrand's question first:

I forgot the exact naming for the process but we just mirror one public svn
folder for the website. It might be svnpubsub, IIRC. Multiple Apache
projects use this (see Cordova for example).

There are two alternatives for site committers:

1. We either install Jekyll and Less (if we modify styling) on our machines
and run a few simple commands to generate the synced folder

2. We use a Vagrant template that I built and use the VM that Vagrant
builds to avoid installing the tools we need locally, while running the
same simple commands (this has the advantage that everybody uses the same
configuration, irrespective of the platforms that we use regularly)

Regarding the theming:
I found Apache's CMS lacking flexibility in terms of templating due to the
fact that I don't have Perl knowledge. Changing the CSS for the current
site is not that difficult. However, being able to build the same layout as
my prototype (as this also implies some server-side logic) is a different
beast.

I haven't been able to commit my work yesterday. Hopefully I'll have a few
minutes today.

Cheers,
Radu
On 21 Dec 2014 18:34, "Reza Naghibi" <[email protected]> wrote:

> Is it even possible to host this in apache.org production?
>
> Would it be possible to just take the redesigned theme and apply that to
> the current site?
>
>       From: Bertrand Delacretaz <[email protected]>
>  To: [email protected]
>  Sent: Saturday, December 20, 2014 6:49 AM
>  Subject: How will updates of the new website work? (was: Promoting
> devicemap strengths)
>
> Hi Radu,
>
> On Sat, Dec 20, 2014 at 12:43 AM, Radu Cotescu <[email protected]> wrote:
> > I'm almost ready with the new site...
>
> How do you see the integration of the new site that you're working on
> with the ASF infrastructure - can you briefly describe the scenario
> and tools for updating the website once your new setup is in place?
>
> -Bertrand
>
>
>

Reply via email to