Hi Rishi,
That's quite a good idea and good news. IIRW, there is already a start for
such things, right?
BTW, I think we should use as much as possible the Confluence history to avoid
to duplicate things and have to maintain them.
My 2cts
Jacques
Le 24/04/2017 à 12:26, Rishi Solanki a écrit :
How about if we start reviewing the documents and update them something
like for which versions those documents applicable. Or may be overall
rearrangement of docs by version.
If we go for overall rearrangement by version then we may have redundant
documentation in most cases. So I would suggest to add supporting version
in the title, or on the top of doc or bottom. May be we can discuss and
come with some best practice to maintain the version.
After that whenever we work on any document we would maintain the practice,
which includes text, image, video, audio all documents. If community agree
then I would like to start on this and start updating few most frequently
used docs.
Thanks!
Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
On Mon, Apr 24, 2017 at 1:49 PM, Jacopo Cappellato <
[email protected]> wrote:
On Sat, Apr 22, 2017 at 7:49 AM, Mike <[email protected]> wrote:
[...] All the previous books, emails, articles, wikis, and blogs that
guided folks on how to deploy a new app, or modify one has been
completely
wiped out [...]
Software documentation is always written for a target version of a software
product and most of the users understand and accept that some of the
information in an older book may not be applicable to newer versions of the
software.
Jacopo
