Frank Peters a écrit :
Per Eriksson wrote:
But is the wiki the right way to go? How often will different versions
I'm not sure but I would like to evaluate that. For some info types it
will definitely be the right way to go (FAQs, Howtos, Application
Help, all that modular stuff).
I think a wiki is a good tool for *short* articles publication. Such an
article could be: "how to use chapter numbering". While "Using mail merge" or
"Using styles and templates" are not topics for a wiki entry, IMO. These have
to be devoted to a book-like document.
Wikis have been brought to a wide audience mainly because of the spread of
wikipedia. Though, I do know many people -- incl. in the IT field -- who do
not know what they are about and who do prefer a printable document they can
read in situations where they have no access to any computer or web site.
These old-fashioned users are still alive and kicking. We have to accomodate
this population because they see office automation tools like OOo as a means
of producing such printable documentation.
Therefore I would go for two levels of documentation: (1) quickly answered
questions through a wiki and (2) broad information using book-like documents
(pdfs or something). The difficult part of the latter being keeping it
up-to-date with the software evolution.
I agree that topic size may actually be an issue. If you split books by
chapter, the individual chapters may get too big to handle via wiki.
Maybe you need to get more granular.
Yes.
--
Jean-Francois Nifenecker, Bordeaux
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
