Using WordPress as Knowledge Base repository

Well, we all know what a great blogging engine WordPress is. However, I think that WordPress’s CMS abilities can be used for much more than just blogging. Recently, I discussed the possibility of using WordPress for a Knowledge Base repository for where I work. There are many wonderful KB applications out there which could have been used, however given the simplicity of use that WordPress gives; I thought that it should do the job.

Below is how it is specifically helpful as a knowledge base:

  • Easy to setup and get going.
  • Easy to integrate various plug-ins for tagging, navigation, and search.
  • Easy to publish using Word 2007. This is especially important because that is the main mode of publishing that will be used at our place.
  • Free. No licensing costs to run it.
  • Comments system: allows readers to contribute to the content by commenting. (we don’t want a Wiki where people can edit)
  • Fully Customizable: we can make any changes we want to it.

We are thinking of using our WordPress server for:

  • Organizational Policies and Processes.
  • Various FAQs and Tutorials regarding these processes and policies.
  • Hosting technical information for quick access within the organization. For example:
    • Best Practices
    • Tutorials
    • Code Snippets

Let’s see how it goes.

If you found this content helpful, then please help by linking to me. You can also help me by sharing the content using any of these nifty buttons above. Thank you.



You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

7 Responses to “Using WordPress as Knowledge Base repository”

  1.   Lucas Rodriguez Cervera Says:

    extremely interesting. this entry is from 2007, did you finally do it?

    Reply
  2. Great to hear this worked out. I had the idea as well, and I’m glad it’s working.

    I’m trying to decide between tikiwiki, drupal, and wordpress. I like wordpress because of the small footprint, ease of use, and easy tagging system. I do want all users to be able to edit articles (we are using pages for biographical information for individual related to our organization), which makes me think Wiki, but I feel that WP is probably better because people on my staff won’t have to mess with the wiki formatting. What are the problems that you’ve had to face Vaibhav?

    Reply
    • Well, mostly it’s working out okay. However, more as a KB repository for the organizational departments to release information. I was hoping to create a more interactive platform, and the adoption has been low there. Have been busy doing other things, so will be looking to attack this problem again in the future (perhaps a custom platform of some type).

      Reply
  3. very useful. had the same problem and your post really helped me to make my decision. The main feature I see with WordPress instead wikis, is that users can enter free-form content.

    If a user (remember I’m working with administrative users, not IT) know html, put the content in HTML. If any know wiki markup, it uses wiki markup. I take all that and focusing on the primary focus that is “users posting information”.

    Reply




Leave a Reply