Confluence Knowledge Base Article Consolidation

[Mark Tobin]

I recently created a Knowledge Base linked to our incident reporting form. The first stage was to create and publish a load of new articles for user consumption but I'm struggling with the limitation of only three visible articles via the incident reporting form. Some of the KBAs relate to our largest application so there will be potentially be a lot of articles with similar labels, making it difficult for people to find the right article.

What I'd like to do is create a KB/FAQ portal that consolidates all KBAs and has categorisation capabilities to assist with solution identification. Ideally I'd like to utilise existing Confluence functionality if available but I'm open to an app if existing Confluence functionality is not available. I'm currently investigating Content Formatting Macros (Kolekti), KARMA Page Builder for Confluence and Scroll Viewport for Confluence but pricing for some of the apps seems excessive for creation of a KB consolidation page / help centre.

I don't really want to direct people to the Confluence knowledge base space bc I think it will be difficult for some of our users to navigate the space and find what they need so I think a formatted page with good search capabilities that displays all available articles by category would be best.

I'm a newbie with Confluence and have tried to find an article or community page to assist but I'm struggling with finding the right content so if anyone has any recommendations or experience in this area, I'd love some advice :)

Thanks.

[Stavros_Rougas_EasyApps]

@Mark Tobin Scroll Viewport is paid, we use it for our docs. You have to determine if the value for money is good. Without a paid app you will be limited and unable to do more if more is requested by management.

[Kristian Klima]

Hi @Mark Tobin 

You can create multiple subsites in Viewport, so you'd have one landing site and then product specific sites - like here: https://help.k15t.com/?l=en

The advantage is that search on the top site works on all subsites, search on the subsites is confined to the content of the given subsite.

As to how you define content for the subsite... it's up to you. It can be a Confluence space, or it can be a Scroll Document (another app) defined as a portion of that space - think labels but with a different level of organization AND presentation.

You can also integrate the JSM widget and incident reporting into the Viewport site, which, if I understand your usecase correctly, would connect your KB articles from Viewport to your support/incident reporting.

Disclaimer: I don't work for K15t, I just use their apps for our doc center.

[Mark Tobin]

Thanks for the quick response @Kristian Klima

I'll investigate Viewport a bit more. I only found it this morning so still working my way through the product. Lots to learn :)

[Kristian Klima]

@Mark Tobin 

If that's the case, you may find my Community articles useful :) 

• How to build a product documentation solution in 30 minutes
• Conditional content and why you should use it