be630745-f956-4c85-a521-5c8b210f93fe

[giscus[bot]]

be630745-f956-4c85-a521-5c8b210f93fe

Do you have a Knowledge Base (KB)?

https://www.ssw.com.au/rules/knowledge-base-kb/

[adamcogan]

Do you know a good example of a comprehensive KB? eg. Microsoft

[stephanfakossw]

If the knowledge base is or low or even if the problem is new, you can use Scribe to whip up quick documentation 😊

[ricksu978]

https://support.stripe.com/

[thom-wang]

https://ant.design/docs/react/introduce

[suiyangqiu]

I'm personally quite a fan of the design - https://steamdb.info/faq/

[vladislav-kir]

Popular Payment Gateways have good KB, for example https://developer.squareup.com/docs, https://support.stripe.com/

[uly1]

yakshaver.ai has the best docs! 😀

[0xharkirat]

https://support.apple.com/

[Aibono1225]

This is very useful! As a user, when I run into an issue I always check the FAQs/docs first to see if it’s a known issue (most of the time it is), and I’m glad when there’s already a solution documented there.

[isaaclombardssw]

This rules is valuable.

If the public has access to your service, a form of KB is non-negotiable (the alternative is more active support work).
There is a maintenance cost also associated with one - as known-issues, performance tips etc. are all variable and can become stale... so date everything and try and stay across the base content if you can.