4

In my wiki roundup post I complained about DokuWiki's reliance on plugins, but after scouring the landscape of FOSS wiki offerings nothing else offers exactly what I need. So I settled on DokuWiki with a bunch of plugins. I have plugins for tagging pages, moving pages, blogging (which I use as a place to quickly catch ideas as they come to me before pushing them to the wiki proper), listing orphaned and wanted pages, among others.

The reason I initially disliked the idea of relying on plugins are that they may interfere with one another, interacting with the different plugins is inconsistent, and updating and management become more complex. But like I said, they get me what I need.

On the other hand, I've also been working with BookStack for another project. In many ways it's the opposite of DokuWiki. It looks modern, it has a noob-friendly wysiwyg editor (important when you need people of different technical skill levels to use it), and tries to be "batteries included" in the dev's words. The problem it's missing some features I consider essential for a wiki, chief of which is the ability to link to nonexistent pages. There isn't really a centralized way to manage uploads, either. And since it isn't extensible, you're stuck with those features unless the dev decides to add them later.

So I can see why people may prefer one approach over the other, but how about you?

top 7 comments
sorted by: hot top controversial new old
[-] esc@piefed.social 3 points 1 week ago* (last edited 1 week ago)

I really like software that is built from plugins, but it needs to have some stable 'core' plugins shipped by default, like emacs for example. Nothing by default is pretty useless but it all depends on constraints and requirements.

[-] chonglibloodsport@lemmy.world 2 points 1 week ago

Used to love plug-in-heavy, customizable tools. Then I realized I loved spending time customizing and installing all those plugins, and not a lot of time getting work done.

Now I just prefer good tools that can do everything I need but not necessarily optimally. As long as they feel really efficient for 95% of use cases and the other 5% are possible (but not optimal) I am good with that. I don’t need to reach for “the perfect tool” anymore.

[-] JackbyDev@programming.dev 1 points 1 week ago

I think I like plug-ins so long as there's a good set that's easy to get. Nicely bundled defaults, ya know?

[-] Bullerfar@lemmy.world 1 points 1 week ago

Since I am a fan of blender I most likely have to vote for the first one. However it was kind of a blessing when many of the features that had to be installed as add-ons before now is a part of the plain software. They tend to implement all of the very popular ones, as a part of the standard program. I think people would lie if they didn't love everything working right out of the box, so we don't have to spend time on configuration and more time on actually creating.

[-] hanke@feddit.nu 1 points 1 week ago

This sounds like a very sane bit of both approach.

Support plugins so anyone can extend however they like, but integrate the most popular plugins into the software.

I like it.

[-] undefined@lemmy.hogru.ch 1 points 1 week ago* (last edited 1 week ago)

I do most my work on the terminal so I prefer something in the middle: convention over configuration, most functionality included but rather small by default. More complex needs can be compiled in.

Related: I wish more Linux distributions’ package managers would allow for binary installation alongside source compiled packages. In FreeBSD I’m amazed at how well pkg’ binary packages play with ports-compiled ones.

What about a nice middle ground option? It has all the features that most sane people would want, but not the kitchen sink.

I hate diagnosing 3rd party jank so if I had to pick one or the other then I’d pick all in one. Oh you updated and now your whole ui is broken? Good fucking luck guessing what adon wasn’t updated for this change.

this post was submitted on 28 Mar 2026
4 points (100.0% liked)

Selfhosted

58268 readers
73 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS