I am looking for examples of communities that have integrated a help documentation portal or built one out using Khoros functionality.
Examples of the type of portals:
As seen in the second link, Khoros' own dev docs aren't utilizing the TKB functionality. So I have to think that the best practice is to use another platform to build this type of robust content? It's just unfortunate to have to send users off to a different experience rather than keep them in the community. I'd love to see examples of communities doing this well though.
I don't have a good answer for this personally, as our documentation & community are completely separate. Only unified by Google :-). We looked into using TKB to replace our documentation site before we launched a couple of years ago, but TKB doesn't have some key features our team needed (e.g. internal-only comments).
I also poked around a tiny bit to see if I could find any good examples for you. And, well, I couldn't. Alteryx, who I always admire, does have a lot of knowledge in their community knowledge base (eg https://community.alteryx.com/t5/Alteryx-Connect-Knowledge-Base/tkb-p/connect-kb) but also a separate documentation site (https://help.alteryx.com/current/ToolCategories/Documentation.htm) - which may or may not be integrated in some way.
I also looked @ Atlassian, who also has a number of TKB-based "articles" - e.g. https://community.atlassian.com/t5/Confluence-articles/bg-p/confluence-articles - but separate documentation (which makes sense since Confluence is a documentation product!)
Hopefully this is a tiny bit helpful, and hopefully others will reply with better examples! (Or perhaps the lack of examples is telling...)
So i'm very bias but i have a great example 🙂 About 2 years ago i merged my community and two other seperate websites which provided help/support to our consumer base into a single website hosted on Khoros https://community.talktalk.co.uk/
I'll be honest at the time i couldnt find any other Lithium client who had or was planning on doing this and even now, your first ive seen. Many communities have a TKB i'm not aware of anyone other than myself who use the community as their only support channel for an entire consumer base.
We use TKB but 100% curated by a team who work for me, this allows us to maintain consistency of the content both in terms of design/layout and language, here are some of our TKBs:
All our content is authored using the TKB wysiwyg but we have made some tweaks to add custom widgets/layouts
My advice.... it's no small task and in some parts counter intuitive as you have to re-design key elements to help level the playing field of topics vs tkb but well worth doing...
The workflow for TKB is shocking but we've put a few workarounds in to make it work however there is a new workflow coming for blog and TKB which would make your life so much easier if you did this.
We have a mix of different designs, and sections, which I don't necessarily agree with, but it's a tremendous step above where we were a few years ago.
While our product release notes live in community, our actual product documentation lives outside, and we have training in community and outside of community. In Community, we have Best Practices, Common Support Questions, and Known Issues and Workarounds.
I would actually disagree a best practice is to use an outside platform. When we first launched our Community, we did have our product documentation in Community in a similar style to those you showed but internal politics led to them moving it outside. I'm guessing Khoros has similar problems, there is absolutely no reason they should not be using their own platform for this - It's not a tremendous amount of engineering work, but the problem for our own documentation team is that using the Khoros platform is different than using mad cap, or Kentico, and thus, that alone is reason to not do it.
I'm a huge believer in the best tool you have is the one in front of you, and this is an opportunity for Khoros in onboarding their customers - The platform has the ability to be hugely extendable, but it requires an engineer on staff. No contractors, no third parties (no offense to them), but my entire experience with Khoros flipped when I went from having to manage it as a platform (and thus its huge limits) to when I was able to treat it as a product, bring on an engineering team, and now we can literally do anything, in a few weeks time, without having to use a platform outside Khoros except when there is true benefits (SSO, Unified search). I know this didn't necessarily answer the direct question, but maybe adds some clarity of my POV, lol.
/me steps off soapbox.
Also props to @Fellsteruk , as my boss has used talktalk for years as an example of what good looks like - So completely agree they are a perfect example of things that can be done!
Most of our documentation is on other platforms, but for some communities we migrated, the documentation came with it. I made the pages out of a a category page with one column and one big custom content box in the layout. Here are examples:
Nothing fancy, but it works.