I already told everyone what changes are required for the CMS to work properly with the docs tree, starting with utf-8.
Some changes are trivial, others are not. >________________________________ > From: Rich Bowen <rbo...@rcbowen.com> >To: docs@httpd.apache.org >Sent: Wednesday, May 2, 2012 8:46 PM >Subject: Re: Proposal to move docs to Apache CMS > > > >On 2012 5 2 18:52, "Daniel Gruno" <rum...@cord.dk> wrote: >> >> Clean slate here, because this is just some free thoughts: >> >> I am for moving both the site and the documentation to the CMS system if >> it indeed works as Tony explained. I'm also in favor of Noirin's >> suggestion about making how to contribute to documentation clearer >Not that, as mentioned elsewhere, these changes are in the process of being >made and will be made tomorrow. But if the process is too hard, all the >documentation in the world doesn't help. >> >> My train of thoughts as I start from the front page is: >> >> 1) Where can I contribute to documentation? I don't see it >> 2) I'm a newbie, what or who is SVN? >> 3) How do I write a patch or check out a repo? (I see a LOT of bugs on >> the docs bugzilla where people obviously don't know what a patch is) >> 4) Okay, I wrote something - why doesn't it show? I need to rebuild? >> 5) What's XSLT, I just wanted to help with a translation?! >> 6) Will everything blow up when I commit something? >> 7) I can't make Java or Perl or insert-process-here work! >> >Let's talk more tomorrow about writing exactly those docs. >But, yeah, I'd like to see what's involved in getting a demo going in the >cms. Lets do that. > > >
