Comment on My thoughts shopping around for a wiki solution

null@lemmy.org ⁨2⁩ ⁨weeks⁩ ago

• early_riser@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

  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.

  source

  • null@lemmy.org ⁨1⁩ ⁨week⁩ ago

    A little bit of both. I ran a private wiki for writers to collaborate on for a project. I was doing other tech stuff for the team so it was my job to deal with it. Keeping it updated was a chore and actually using it was finicky.

    For example, there was an issue we ran into where we wanted a dynamic table that pulled from other pages. Think of a shopkeeper inventory or something similar where each item was another page. Displaying an item worked fine the first time you pulled it, but if you updated the item’s page it wouldn’t push that to any page it’s displayed on. We ran into issues like this constantly. Some solutions worked, others didn’t.

    After a year or so we migrated to something else. It’s free and it’s great that it exists, but it just has a roughness to it that we didn’t have the resources to deal with.

    source