Was it the backend, maintaining the DB and juggling extensions and such, or was it organizing the wiki itself? I've heard lots of people complain about maintenance. My personal project currently uses Mediawiki with sqlite as the DB. I'm essentially the only editor and almost the only reader, so it's more of a CMS than anything.
Because the wiki is public, I have to maintain a separate KB (currently Obsidian) for drafts and scratch notes and other "thinking out loud" such and such that I'm not ready to present to the public. That's why I'm looking at something with access control. I'd like to consolidate all my work on this project to a single place, with notes and drafts accessible only to me, that I can publish when I'm satisfied. Dokuwiki with a crapload of plugins seems to be the closest.
Lemme tell ya somethin about Tiddlywiki. Actually a lot of knowledge base software has this problem (I've specifically encountered it in Trillium, Obsidian, and TW).
You have your body where you're austencibly storing the meat of your information. But you also have configurable metadata fields. Obsidian has its YAML headers, and TW and Trillium have separate metadata forms. All three of these have scads of methods for sorting and querying and filtering the metadata but next to nothing for the actual note. But the note is already organized data. It has headings and subheadings and text under those headings. Why can't that be queried? I got into this on the TW forums. Everyone was basically telling me to cram all of the actual data into the header, leaving the note itself virtually empty. Obsidian has its bases feature which does the same thing. Then why not just have a bunch of YAML files? A genuine question, I'd actually love a system for sorting and querying a bunch of organized YAML files almost like a noSQL database. But Obsidian doesn't let you do that. It has to be markdown.
I got off track there, but there it is.