[prev in list] [next in list] [prev in thread] [next in thread] 

List:       groovy-user
Subject:    Re: [groovy-user] Live update of Groovy Documentation
From:       jim northrop <james.b.northrop () googlemail ! com>
Date:       2014-08-29 18:32:58
Message-ID: CAF86WphyriM_dWLyeSROncEpLQP+1yDnXbVVpgzsNPfe56i8Cw () mail ! gmail ! com
[Download RAW message or body]

ah yes ! i did think that was the idea. am quite content that's the
way we do it. less chance for inaccurate docs
thx

On 29/08/2014, C=C3=A9dric Champeau <cedric.champeau@gmail.com> wrote:
> It is intentional, since we want to *avoid* the wiki behavior, which is,
> anybody edits a page, and documentation becomes out of date. With the new
> procedure, documentation is part of the build process and snippets of cod=
e
> are test cases, meaning that all the documentation is tested *before*
> merging.
>
>
> 2014-08-29 15:38 GMT+02:00 jim northrop <james.b.northrop@googlemail.com>=
:
>
>> My understanding at the moment is that groovy documentation is
>> generated as static content with no persistance store behind it. Does
>> anyone know if we have any plans to make our groovy docs more
>> wiki-like in that they can be edited/amended by the reader ?
>>
>> several other sites offer this feature. It just seems a little
>> dangerous to me as some potential changes might not reflect reality or
>> be reviewed by people who know more and might lead future readers
>> astray.
>>
>> what do ya think ?
>>
>> thx
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


[prev in list] [next in list] [prev in thread] [next in thread]