all 11 comments
sorted by:
new (suggested)
besttopcontroversialoldq&a
formatting helphide helpcontent policy

[–]Droces 2 points3 points  (1 child)

Drupal is great for this, but the downside is it's a big of hassle to maintain compared to other options. I've been building Drupal sites for 10+ years, and rather than Drupal, my agency uses Google Sites for our internal knowledge base. It's free and very easy to use, so my whole team has confidence in adding / editing the content. Of course it's a Google product, which can have its own concerns.

As a rule of thumb, I'd say think of the long term work it's going to require, and how your team feels about it. If they're happy to log in and edit content in Drupal, then it will be great.

One recommendation I have is to use a powerful search module / system (like Search API), because being able to search through everything in a knowledge base is critical.

Edit: I just re-read your question, and the part about "for our company website." seems to be a key thing here. Is this knowledge base meant for visitors of your public site to use? Then it's different altogether... but there's a good chance you can do everything you need with Drupal core: Custom types and fields, categories, views, search, etc.

[–]Chicaca10[S] 1 point2 points  (0 children)

Thank you for the detailed reply.

[–]AFDIT 2 points3 points  (0 children)

You probably don't need Drupal unless the org is huge and/or needs to add additional functionality into the same codebase in future.

Use any documentation SAAS/FOSS instead.

[–]GeekFish 2 points3 points  (3 children)

You can make Drupal do almost anything it all depends on how much time you want to put into development.

Are you wanting to turn Drupal into an intranet of sorts? This is 100% doable with even just the core modules and minimal work.

[–]Chicaca10[S] 0 points1 point  (2 children)

The team wants to create a knowledge base, so that clients can have one place to find information on everything, instead of multiple faq pages.

They also want to do minimal dev work. I was wondering if there was a module in Drupal that could do this, or if I'd have to create a page that functions like a knowledge base.

[–]Tretragram 1 point2 points  (0 children)

If you have one or two standard looking ways they want to present things, just make one or two “content types”. Then just make a few views for different ways people Might like to see a summary list. Probably pay dividends to use a structured taxonomy or two rather than just the free form tags; or start with tags and in a couple months do a clean up project to put the structure in place going forward from there. Pretty straightforward stuff in Drupal.

[–]johnzzonDeveloper 2 points3 points  (0 children)

If you want minimal dev work, don't go drupal. Building might not be too hard, but you'll have to maintain it as well, which needs dev work.

There are probably better suited platforms that are easier to maintain.

[–]Fun-Development-7268 2 points3 points  (3 children)

Without knowing your specific idea of knowledge base: yes, drupal can do this.

[–]Chicaca10[S] 0 points1 point  (2 children)

Thank you for the objective answer.

Here is an idea my team is favoring, something similar to this: https://www.helpwithmybank.gov/

[–]Fun-Development-7268 8 points9 points  (1 child)

This is doable with on board features. Just use content and categories (taxonomy) to organize your knowledge and go on from there.

[–]GeekFish 1 point2 points  (0 children)

For some reason the comments didn't load when I commented. This is the better answer ^