Defining requirements and choosing a Knowledge Base Platform

Defining requirements is important because it will help you choose the appropriate platform. Here is a list of questions to help you clarify your requirements.

Is the knowledge base for internal use?

If for internal use, the knowledge base will have to be private and protected by a login.

Will you be managing multilingual content?

Make sure to pick a platform that supports managing content in multiple languages if that's a requirement.

Will you be creating guides or manuals as well as regular help articles?

Some platform only support writing classic help articles grouped by topics. If you plan on writing help guides (like this one), consider a solution that will offer layout options optimized for guides.

Do you require a lot of customization?

If your needs are very unique to your organization and know you will require heavy customization, consider choosing a solution giving you control over the template and general behaviour.

Do you prefer a hosted solution or a cloud solution?

Hosted solutions are solutions hosted on your own servers and infrastructure. While you will typically have full control over the platform, you will also have to maintain it. A cloud solution (SaaS) is a service you pay on month-to-month basis.

How many users will need access?

Most solutions will charge on a per-user basis. Note that Timelapse is an exception, all accounts come with unlimited users.

We'd love you to give Timelapse a try.
How did we do with this article?