I'm working on this pro-con comparison of having the Product documentation within the Community
- Community: Engagement and relationship building
- Product Docs: Reference and Training
- My usecase is a Collapsable Directory style wiki, like docs.jivesoftware.com
I know Jive has consciously stayed away from offering this capability. I just want to explore why?
From an IT asset management, admin and User Experience standpoint, a single system makes sense.
But does anyone have any best-practices to share on why having the 2 platforms separate is a good idea?
Thoughts shared are greatly appreciated.