DokuWiki for simplicity. Everything is a text file that can just be copied to a web server. It doesn’t even require a database. And since all the wiki pages are plaintext markdown files, they can still be easily accessed and read even when the server is down. This is great and why I use DokuWiki for my server documentation as well.

I run a Bookstack instance which works quite well for me.

I really like WikiJS but its development is stuck for a long time now. No v3 in sight… Sadly

I am using latest v2 for now, but I am looking for alternatives. Pro for WikiJS: S3 Backend, easy to use, WYSIWYG-Editor

Outline is a hell to selfhost, even if it starts, login via Email / Password is not enabled by default. You need to login with Github or similar… Never again

This is my experience with wikis so far.

I’m administering a wiki.js instance. Despite it being written in node, it’s a pretty nice wiki with a lot of modern features builtin. The only other wiki I’ve ever setup and used was mediawiki, which is obviously a complete legacy php clusterfuck where you need add-ons (which are terrible to install and configure) for everything.

I just spent a week evaluating all the popular choices to document an overlay network I’m standing up. All I want is a simple markdown interface to write notes in. My goal was something with a very simple UI, markdown, and very light weight.

MediaWiki, Bookstack, and WikiJS (or JSWiki) were good but they were too much for what I needed. I ended up with stumbling on gollum and really like it. It’s very very simple, fast, and clean. I wrote a one line cronjob and now I’m backed up to gitlab.

https://github.com/gollum/gollum

deleted by creator

I like mediawiki

I previously used WikiJS, but since about a year ago I switched to Grav.

The really nice thing is not having an additional database anymore. It’s really just markdown pages, config files and php plugins.

By default it looks like a blogging platform, but with the learn2 theme it also works pretty well as a documentation website. The official docs are written using that theme.

I wasn’t completely happy with the defaults though so I did some modifications for my own wiki. Some limited knowledge in HTML, CSS is required and PHP or Javascript don’t hurt either.

You can find the theme, plugins and pages in my repo as well if you’d want to use any of it.

Bookstack is really nice and user friendly. It’s probably one of my favorites.

Dokuwiki is simple and stores files in plaintext.

I haven’t used wiki.js much but I’ve heard good things about it too.

Another option if you don’t need to share the wiki with anyone would be a note tool like Trilium. It has built in support for stuff like mermaid or excalidraw diagrams.

Don’t forget to setup backups for whatever wiki you do go with, and make sure you can restore them when your wiki is broken ;)

I did a similar inquiry a few months ago. I tried DocuWiki and Wiki.js. Ended up with Wiki.js. It’s very easy to setup with docker-compose. Everything is stored in Postgres but it also exports to the local filesystem in Markdown. Its advanced built-in search is pretty good.

Gollum. Hit integration is required if you value wiki content.

I’ve been using Wiki.js since I asked this question a few months ago. I’ve been pretty happy with it. Stores data in text files using markdown and can synchronize a number of backends. I’ve got mine syncing to a private github repo.