Paul's Knowledge Base

PKBase2 is like a wiki in web format, except you also have an index on screen for all your files, and you have categories for your various notes, lists, etc.

PKBase2 is a significant upgrade from the original version. Originally, it was designed solely as a web front end for viewing markdown files managed on the back end with Vim and Vimwiki. Version 2 introduces the ability to manage your files completely in PKBase2.

It assumes several things:

Normally, you would administer your knowledge base with Vimwiki, but you can do so with PKBase2 instead, if you like.


Copy this software to some directory served by your web server. Your content will go in the content directory of the site. Create a file in that directory which is an index of the files in your wiki. You may add files and create new directories with files in them. Your which looks like this:

* Foods
	* Fruits
	* Meats

If you make this file the index for your wiki, you can add files on the fly as you normally would in Vimwiki, by creating a Vimwiki link, and hitting Enter on it to go to that file.

This assumes you already have content for your knowledge base. If you don't, PKBase2 will remind you to create some. If you do already have content, once you install PKBase2, hit the "Rebuild Index" button to synchronize PKBase2 with your existing files.


The config/config.ini file allows you to change the name of your wiki, the name of the content directory, etc. You are advised to edit this before installation. You can change the name of the site, the "slogan", and various other aspects.

Use Case

Here's my use case for this software. I dump a lot of random information into my personal wiki, like details on appliances I've bought, cheat sheets for software I use, construction project details, etc. My wife can't access this information normally (it's on my personal machine), and doesn't have the expertise to handle Vim or Vimwiki. Still, she might need access to some of this information. So I run it on a web server on my machine, and she can surf to my webserver from her machine.

Technical Details

This package uses the Parsedown library to parse content from your wiki pages, meaning you'll have to use markdown in your wiki. If you use Vimwiki markup instead, you'll have to substitute some library which understands Vimwiki markup to do your translation. Or, I suppose you could write everything in HTHL. Good luck with that.

Come to think of it, you could use any markup you want. The advantage of using Vimwiki is that I can hit Enter on a link and go to that file, which will be created if it doesn't exist. Hit Backspace in that file to go back to where I came from (the index file).

If you make changes to the contents of your content directory, there is a button named "Rebuild Index" every page of the site. This will generate a new `` (index) page for you.


At Gitlab: Here