Yes why not. It can be a step two in the documentation project.
From my point of view, the purpose of wiki -> DocBook is to avoid to
rewrite all the content.
After we have two ways:
1/ the wiki is the master and the documentation is generated from there:
the advantage is that it's simple to edit and provide but I'm not sure
that the generated documentation will be very fine
2/ the wiki pages will be deprecated and the sources are "static".
Regards
JB
Charles Moulliard wrote:
That's perfect for me.
Probably that we will need also a command to transform docbook into
HTML page of wiki in order to synchronise docBook with Wiki in a
symetric way.
I don't know if this is interesting but there is a confluence docbook
converter plugin :
http://confluence.atlassian.com/display/CONFEXT/Confdoc+DocBook+Converter
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
On Thu, Nov 19, 2009 at 9:37 AM, Jean-Baptiste Onofré <[email protected]> wrote:
Hi all,
FYI, I have begun to write a maven plugin (in my sandbox repo) to:
- transform a DocBook documentations into HTML, FO, PDF
- be able to get confluence wiki HTML source, apply JTidy on it to transform
into XHTML and apply a XSL to go to DocBook.
This plugin will be used to generate the ServiceMix manual from provided
DocBook document and to init these documents from the wiki.
I would like to resume the work on the manual and, in the same of the first
manual release, promotes http://servicemix.apache.org/home2.html to give
more visibility.
What do you think about this ?
Thanks
Regards
JB
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
[email protected]
PGP : 17D4F086
