Skip to main content
Solved

Creating our knowledge base

  • October 28, 2019
  • 3 replies
  • 143 views

PatelN54
  • Contributor ⭐️⭐️
  • 8 replies

Hi All, 

We’re currently in the process of creating our knowledge base, and I was just wondering what you would recommend as best practise for old articles and categories.

We’re looking to completely revamp our community by creating new categories to replace the old ones, and breakdown our current articles in to smaller FAQs for better search results.

We understand that this may lead to duplication in content. So, what would you recommend doing it old ‘redundant’ articles and categories.

Thanks,

Nikhil

iD Mobile

Best answer by Julian

Hi Nikhil,

I’m very happy to hear that you are in the process of reworking your categorization and planning to use our knowledge base as well!

I understand your concern of duplicate content. How I handled it on our community: I keep the knowledge base for official tutorials and FAQs, while the “regular” community categories are there for discussions and Q&A of users.

This way, the FAQs and Tutorials in the knowledge base will offer fundamental support for general questions, while specific problems or questions can be handled in the community.

I have created knowledge base categories which are more specific than the community categories. By doing so, I want to offer an easier navigation across the knowledge base. However it also has to do with general activity across the community categories: If there is not too much activity, you want to have rather general community categories. It would not give a good impression if there are many categories but not much activity in each of them.

 

If I were you, I would map all the content which already exists and is suitable for the knowledge base (from community categories but also outside of the community), and form your knowledge base categories based on that. Then see if there are areas which are not yet covered in the knowledge base (maybe you don’t have content on a subject you do have a community category for) and check if you can create content for it.

Once this is done, you can proceed and create these categories and publish in / move content to these categories.

Let us know if you need further assistance, of if you like us to review your new knowledge base and community categorization!

View original
Did you find this topic helpful?

3 replies

Drew C.
  • Helper ⭐️
  • 36 replies
  • October 29, 2019

Hi Nikhil,

Keep in mind that new categories will require users to re-follow them. Where possible, I’d suggest keeping the categories intact and just renaming them. If the use case will be entirely different after the change, then this is probably unavoidable. Requiring community members to re-follow categories of interest may lead to a decline in participation (hopefully only temporarily).

 

Regarding Knowledge, I’d like to point out the KCS (Knowledge-Centered Service) Methodology.

https://www.serviceinnovation.org/kcs/   There’s a lot to digest, but you’ll likely get some good ideas and best-practices from the content on the site. I’m happy to answer any questions you might have.


PatelN54
  • Author
  • Contributor ⭐️⭐️
  • 8 replies
  • October 30, 2019

Hi @Drew C. , 

Thanks for your feedback, it was really helpful.

I’ll have a read of the KCS link and let you know how I get on.

Thanks again,

Nikhil


Julian
Forum|alt.badge.img+5
  • Gainsight Employee ⭐️⭐️⭐️
  • 908 replies
  • Answer
  • November 13, 2019

Hi Nikhil,

I’m very happy to hear that you are in the process of reworking your categorization and planning to use our knowledge base as well!

I understand your concern of duplicate content. How I handled it on our community: I keep the knowledge base for official tutorials and FAQs, while the “regular” community categories are there for discussions and Q&A of users.

This way, the FAQs and Tutorials in the knowledge base will offer fundamental support for general questions, while specific problems or questions can be handled in the community.

I have created knowledge base categories which are more specific than the community categories. By doing so, I want to offer an easier navigation across the knowledge base. However it also has to do with general activity across the community categories: If there is not too much activity, you want to have rather general community categories. It would not give a good impression if there are many categories but not much activity in each of them.

 

If I were you, I would map all the content which already exists and is suitable for the knowledge base (from community categories but also outside of the community), and form your knowledge base categories based on that. Then see if there are areas which are not yet covered in the knowledge base (maybe you don’t have content on a subject you do have a community category for) and check if you can create content for it.

Once this is done, you can proceed and create these categories and publish in / move content to these categories.

Let us know if you need further assistance, of if you like us to review your new knowledge base and community categorization!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings