Good morning,

to publish documentation like the one on
http://directmemory.apache.org/ we used APT and xdoc Maven's format,
not docbook.

best,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Sat, Oct 6, 2012 at 10:40 PM, Christoph Engelbert
<[email protected]> wrote:
> I worked with the docbook standard in a company before. It worked
> very well for documentation of an SOAP webservice and was
> "relatively" easy to customize in terms of layouts.
>
> So +1 from me for using docbook to create pdf and html from the
> docbook standard xml.
>
> I found a really good xml editor with direct docbook support, just
> need to search for it again :-)
>
> Cheers Chris
>
> Am 06.10.2012 22:36, schrieb Raffaele P. Guidi:
>> Yep, it was docbook. I think it brings to extremely well done
>> documentation. Do you guys think that it could be worth giving it a try?
>>
>> Ciao,
>>     R
>>
>> On Sat, Oct 6, 2012 at 10:24 PM, Raffaele P. Guidi <
>> [email protected]> wrote:
>>
>>> You are welcome, thanks for getting involved :) of course adding docs to
>>> the DM maven site is the preferred way even though I wouldn't say that we
>>> are an excellence, when it comes to docs and probably an easier way to
>>> write them would help. Has anyone proposals about it? I really like how the
>>> spring framework is documented (I think it's done with a lucene tool, don't
>>> remember exactly how it is called and my google karma tonight is low).
>>>
>>> Ciao,
>>>     R
>>>
>>>
>>> On Sat, Oct 6, 2012 at 9:47 PM, Christoph Engelbert 
>>> <[email protected]>wrote:
>>>
>>>> Hey guys,
>>>>
>>>> so the account creation was successful :-) Thanks for the given
>>>> trust I'm totally proud.
>>>>
>>>> The first question is how to do documentation for Lightning? Is
>>>> there a preferred way to document subprojects or do they get there
>>>> own part on the main projects page (like it seems to be on the
>>>> commons projects)?
>>>>
>>>> Cheers Chris
>>>>
>>>
>

Reply via email to