Hey Yoshi,
While that is in the long term goals that we are moving towards, currently it isn't feasible for us to house the documentation in SBS. We're trying to find a way to host content in SBS while continuing to meet the expectations we've already established, and it's keeping our documentation team exceedingly busy. I hope that helps.
Thanks,
Kevin
If it is not possible to host the documentation in SBS, could it then perhaps be hosted in some other format where we can comment on it? For instance, Documentation for contentTypes in searchService is something that really belongs in the documentation and I am sure it would save everybody who works with the webservices time if we could just add those things.
Hey Jochem,
I agree that the documentation could be improved with the addition of some more content. Our documentation team is working hard on documenting current versions as well as keeping up with our development teams. We try to be the stop-gap when we can, like in this instance: Content Types and You. And hopefully, these documents that we sometimes make on the side will be added to the documentation. I hope that helps.
Thanks,
Kevin
kevin.imber wrote:
I agree that the documentation could be improved with the addition of some more content. Our documentation team is working hard on documenting current versions as well as keeping up with our development teams. We try to be the stop-gap when we can, like in this instance: Content Types and You. And hopefully, these documents that we sometimes make on the side will be added to the documentation. I hope that helps.
It helps. But not enough. As should be obvious from the fact that I am basically asking how I can help you write better documentation (or from the list of documentation questions I have asked that remain unanswered).
Hi Jochem,
You can help in the same way that we do in support. If you find that there isn't very good documentation on something, and still want to learn about it, then dive right in. Make a document about it on jivespace when you're finished, so that others can learn from your experience. Then the documentation will improve, from the work of the developers and the community.
Thanks,
Kevin
kevin.imber wrote:
Make a document about it on jivespace when you're finished, so that others can learn from your experience. Then the documentation will improve, from the work of the developers and the community.
I do not consider that a good alternative. A bunch of disconnect documents somewhere else does not equate better documentation. What I am looking for is something like in the MySQL documentation where right at the bottom there is the User Comments link. That way anything added is added right on the page where it is needed so it can be found. In addition redactional control remains with the documentatio group who on each release will either integrate comments into the official documentation or will remove them.
Hey Jochem,
Unfortunately, we don't have that functionality. I've filed an improvement in our system for you on this issue, the improvement ID is CS-17501.
Thanks,
Kevin
Jive combines the most powerful features of collaboration software, community software,
social networking software & social media monitoring into the leading SBS solution.
© Copyright 2000–2010 Jive Software. All rights reserved.
915 SW Stark St., Suite 400, Portland, OR 97205
Sales: 877-495-3700 | General: 503-295-3700
Privacy Policy | Sitemap | Jobs | Contact Us