In my experience, providing shorter, more focused cross-linked documents in our Jive instance has worked very well, rather than a link to one long instruction manual:
- You can provide help on the features or functions most important to you.
- You can customize each document to your installation.
- Your documents become searchable in your Jive
- You can update the documents based on comments left by readers.
That said, I have stolen much of what is in my help documents verbatim out of the Jive help and primarily removed the details that don't apply to our installation.
Thanks for your feedback. This isn't actually for the Jive help, but for our software which already has Help built in and available within the product.
Same approach, though - breaking into smaller pieces works better so that users can search for and find the bit that is relevant to them at that moment. Otherwise, search is unlikely to bring a relevant results (unless they search for general help instead of a specific topic, the relevance is diluted due to volume of words in one doc).