I'm not sure who is more confused now - I'm using oyxgen and have (of course, doh) checked the docbook output locally before committing.
But in order to get the stuff through the make and onto the website, there's more beyond that - I've created the docbook for the new how-to and edited the master book to add the entry for the new sub doc. Are we really saying that there should be ?3 manual steps to get the docbook onto our website for every new doc ? Apologies if I'm missing something. Given I'm on windows, I can't really use the readme instructions so perhaps I'm making a mistake about how many steps there are to get docs up on the web ... Regards, Marnie On Wed, Nov 3, 2010 at 9:32 PM, Steve Huston <[email protected]> wrote: > I haven't tried the docbook generation so may be speaking a bit out of > turn, but I agree with Jonathan that automatically pushing new content > to the web without the developer/writer reviewing the result is a bad > idea. > > FWIW, > -Steve > > > -----Original Message----- > > From: Jonathan Robie [mailto:[email protected]] > > Sent: Wednesday, November 03, 2010 4:08 PM > > To: [email protected] > > Subject: Re: Automating docbook generation > > > > > > On 11/03/2010 01:18 PM, Marnie McCormack wrote: > > > All, > > > > > > Would it be possible to agree/setup an automated task on one of the > > > various CI instances around to build/export the master > > docbooks from > > > svn ? > > > > > > I'm working on Windows, and have just completed the 3 > > stages to create > > > a new user doc. Somewhat painful and now I'm stuck (I > > think?) at the > > > make stage, before I could export to the website. > > > > What are you currently using to validate your XML? > > > > You'll probably want to convert locally and look at the output before > > publishing on the web site. > > > > You can get a free copy of the Oxygen XML editor to do this, since > > you're working on the Qpid project: > > > > http://markmail.org/message/jphsxbfg6ilmpj2m > > > > Or if you prefer the command line, you can install Saxon and use the > > docbook stylesheets to convert to PDF and HTML. This is also free. > > > > > > > Seems like an automatic job to pick up any changes and export them > > > nightly onto the website would be a useful util. > > > > > > Thoughts (aside from how much quicker wiki is!!) ? > > > > Possibly - I'd probably set it up so that any XML that does > > not validate > > is rejected, without generating documentation. > > > > And I think the first step is to set things up so you can see > > what you > > are producing locally. Once you can do that, you can check in the > > results without running an automated job. And I'm not sure I > > want people > > checking in documents they haven't looked at on their local machines > > first - what do others think? > > > > Jonathan > > > > --------------------------------------------------------------------- > > Apache Qpid - AMQP Messaging Implementation > > Project: http://qpid.apache.org > > Use/Interact: mailto:[email protected] > > > > > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > >
