this post was submitted on 28 Mar 2026
58 points (95.3% liked)

Selfhosted

60281 readers
664 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
58
Do you prefer bare bones software that you customize with plugins, or an all-in-one solution that does everything you need out of the box? (lemmy.world)
submitted 3 months ago by early_riser@lemmy.world to c/selfhosted@lemmy.world
22 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] tvcvt@lemmy.ml 4 points 3 months ago

I don’t have a real preference, but one more advantage to the plugin route is that if you need something that’s not available, cobbling together a plugin is much simpler than modify most projects directly.

I recently spent a lot of time doing this with Odoo and I was very grateful for the modularity.

By the way, in case you haven’t found it, there is a pretty decent wysiwyg editor plugin for DokuWiki. I use it at work and it’s been pretty simple for my users.