I've checked in what Ivan did to https://svn.apache.org/repos/asf/logging/site/branches/cms/trunk as Herve suggested. I found 1 bug in build.php and fixed that and added a requirement to specify the output directory on the command line. I also moved the content and templates to the appropriate directories.RalphOn May 23, 2012, at 9:32 AM, Ralph Goers wrote:Thanks. Please let me know when we are at the point where I can try to add Log4j 2 on to the site.RalphOn May 23, 2012, at 9:30 AM, Ivan Habunek wrote:I have given infra the requirements. We're waiting for them to set it up.Regards,IvanOn 23 May 2012 17:57, Ralph Goers <email@example.com> wrote:
Ivan,Were you able to get a test site to work yet?RalphOn May 22, 2012, at 5:52 AM, Ivan Habunek wrote:Yeah, sorry I haven't been more involved in the discussion. I've been to the phpday conference in Verona, and haven't had time to catch up.I posted a comment to the INFRA ticket with the required information. I'll keep in the loop from now on to answer any other questions.Regards,IvanOn 22 May 2012 13:40, Ralph Goers <firstname.lastname@example.org> wrote:
Ivan,Daniel has updated the Jira and asked "Can you provide a list of dependencies of your site's build process? (as port names -- see www.freshports.org -- for those deps that are in ports)"Since you have actually built the test site could you possibly help with this? The issue is https://issues.apache.org/jira/browse/INFRA-4699.
On May 2, 2012, at 2:11 AM, Ivan Habunek <email@example.com> wrote:
Hi all,I was away for a bit so I didn't comment earlier.My idea is to generate the site using Twig , a nice PHP templating engine, in combination with Textile markup , which is much more versatile than most other common markup languages (such as markdown, apt, ...).I have already converted the logging web site. The code can be found here:And I have deployed the generated web for demo here:This idea is obviously not compatible with the Apache CMS solution. Frankly, I would prefer this solution to the CMS since, from what I have seen, the CMS is quite a pain to use.Regards,IvanOn 2 May 2012 10:44, Christian Grobmeier <firstname.lastname@example.org> wrote:OK I understand svn externals is like "symlinks for svn". Sounds ok.On Mon, Apr 23, 2012 at 4:06 AM, Ralph Goers <email@example.com> wrote:
> On Apr 20, 2012, at 12:14 PM, Christian Grobmeier wrote:
> What i thought was, why not to clean it up? Your proposed solutions
> seem to be the cleanest way and updating everything just when we need
> an update to the main site feels somehow wrong
> Joe has now proposed using the CMS for the main Logging web site along
> with expaths.txt + svnpubsub for each sub-project. Each sub-project would
> then use svn externals so they could be independently managed. This sounds
> perfect to me.
I am a bit concerned on the CMS. Ivan has put much effort in the website design:
I will ask infra (on the ticket) if it is possible to either use that
design for the CMS or if we can bypass the CMS feature for this one