Re: [Gnumed-devel] small Sphinx demo

[James Busser]

On 11-Sep-08, at 3:38 AM, Gour wrote:
> Sebastian> Point taken. I have to make up my mind where I fit into the
> Sebastian> equation. One issue is the doc team. I consider it
> Sebastian> important.

Me too.

On 11-Sep-08, at 2:34 AM, Karsten Hilbert wrote:

> > Wiki --> edit over months until a release --> transfer manual from  
> > wiki to rst
> > and tidy up --> release manual and software.
>
> I would agree with that workflow.

I understand and agree that there *are* pieces of information that  
best live on the wiki, and whose quick editing is useful. But I also  
agree that

On 11-Sep-08, at 3:15 AM, Gour wrote:
> Well, wiki is, imho, not suited for writing serious & structured
> documentation. It's OK for quick and short notes, but not for  
> technical
> documentation like application's manuals etc. which require very god
> structuring, index, glossaries, figures (screenshots), code snippets
> etc.

although in actuality
> IOW,  I consider that such documentation has to be written offline

the above is presumably only a constraint of the tool(s).

I am not unwilling to learn tools that would make sense to use. I  
only need them to be within my lifetime capacity. Some confidence  
that the choices could be stable and that I won't end up the only one  
using them, since I won't learn too much too quickly, might be nice.  
And yet I recognize, as my mother cautioned, that nothing meaningful  
in life is certain!

For me then, the question is how to separate what *can* usefully  
belong on the wiki and what *isn't* useful to maintain there if it is  
going to be (and better able to be) constructed under a non-wiki  
method. I think for the latter to work, that suitable versions of  
what isn't wiki-generated be conveniently available linked *from* the  
wiki. I will start a new thread "Wiki documentation separation".