I find it too linear.

On Fri, Oct 31, 2008 at 12:21 PM, Symon Rottem <[EMAIL PROTECTED]> wrote:
> Not taking exception, but what's hard to consume or navigate about it?  The
> generated output is in HTML which is fully searchable and can be hyperlinked
> until the cows come home...
>
> Symon.
>
> On Fri, Oct 31, 2008 at 1:00 PM, Colin Ramsay <[EMAIL PROTECTED]> wrote:
>>
>> I don't mean to be negative, but IMO that output format sucks. It's
>> like something which would have been acceptable 15 years ago. There
>> must be something we can do which presents the information in a way
>> which is slightly easier to navigate, the web is not a book. For my
>> part, the current documentation is presented in a format which is much
>> easier to consume. If we could make it easier to update the docs on
>> the Castle site, that would be better.
>>
>> On Fri, Oct 31, 2008 at 11:21 AM, Jonathon Rossi <[EMAIL PROTECTED]>
>> wrote:
>> > While everyone is on the topic of change, do we want to move to the
>> > docbook
>> > documentation that Symon Rottem set up a while back? It should make it
>> > easier to write documentation.
>> >
>> > Do we really need multiple copies of the documentation hosted like we
>> > have
>> > now? Because documentation tends to lag behind and is always being
>> > updated
>> > after a release it might be better to have one copy like jQuery has.
>> >
>> > MonoRail example of the docbook format:
>> > http://www.symbiotic-development.com/monorail/html/index.html
>> >
>> > --
>> > Jonathon Rossi
>> >
>> > >
>> >
>>
>>
>
>
>
> --
> Symon Rottem
> http://blog.symbiotic-development.com
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Castle Project Development List" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to