Another idea for documentation could be something similar to the Linux Documentation Project. This would allow documents of varying scope. For example a very small how-to could be on transactions.
A much larger how-to could be on intake or extending the turbine schema. On Mon, 2002-11-11 at 18:37, Scott Eade wrote: > Great. For new documents we should aim for at least an outline before we > add them as works in progress. If you intend working on these through to a > level of semi-completion then you should look at the existing xdocs and use > that format (it is really very easy). > > I can't recall where the xdoc documentation resides, bit it is fairly easy > to follow an example - e.g.: > http://cvs.apache.org/viewcvs/jakarta-turbine-2/xdocs/howto/extend-user-howt > o.xml?rev=1.7&content-type=text/vnd.viewcvs-markup > > Cheers, > > Scott >Quinton McCombs< Strategic Planner, NEqualsOne 1800 International Park Drive Suite 205 Birmingham, AL 35243 p: 205.324.8005 x121 800.466.1337 f: 205.324.7008 e: [EMAIL PROTECTED] www.NEqualsOne.com
