Which wiki software to host

https://lemmy.nocturnal.garden/post/552460

Which wiki software to host - Nocturnal Lemmy

cross-posted from: https://lemmy.nocturnal.garden/post/552459 [https://lemmy.nocturnal.garden/post/552459] > For a hobby of mine, there’s an outdated lore wiki on Fandom. I dislike Fandom and would like to host an alternative. It’s supposed to be accessible to all kinds of people. > > I started with mediawiki as that’s what Fandom and Wikipedia are using, so people would be familiar with page structures at least and maybe the editor. > > It turned out to be a bit of a pain though. It only has unofficial container images, the documentation is outdated and (what I consider as) core functionality like WYSIWYG editor or simple infoboxes has to be added by extensions or templates. I’m in the process of setting it all up and wondering if it’s worth it (and if I want to maintain it). There’s so many wiki projects it’s hard to keep track, what are y’all using for stuff that’s used by larger communities and simple to use with close-to-default settings?

MediaWiki’s probably overkill for basic wiki functionality, but I use it for the sake of Semantic MediaWiki and associated extensions. But SMW has more of a learning curve, so it might not be worth it for a casual-use wiki.
semantic-mediawiki.org

semantic-mediawiki.org

Semantic MediaWiki
Yeah it seems like it’s doing too much for me.
Maybe skim this recent post? lemmy.world/post/43616899 Lot of folks chimed in about their opinions on many different wiki approaches, my takeaway was that Bookstack looked like something I’d wanna use in the future, but there’s a lot of stuff covered in there.
My thoughts shopping around for a wiki solution - Lemmy.World

I know wikis have been discussed here before, but I wanted to add my two cents after shopping around for a wiki at work and for personal use. ## Obsidian ### Pros - plain text storage format - great at gathering disorganized thoughts without imposing a rigid structure ## Cons - closed source - many features that arguably define a wiki are either absent or paywalled, like easy sharing, collaboration, and versioning ## Mediawiki ### Pros - it’s the wiki. Everyone’s used and possibly edited a Wikipedia page. - version history - close to Obsidian in terms of “write now, organize later” - Probably the nicest-looking FOSS wiki platform out of the box - a lot of the features that Obsidian paywalls are built in, like multi user support and version history ### Cons - Articles not stored in plain text - Has its own markup. Granted Mediawiki predates Markdown but the table syntax is horrendous. The Mediawiki help page on the matter actually tries to dissuade you from using tables and notes that the markup is ugly. - Extensions are annoying to install - Absolutely zero access control. You can even edit other people’s user pages. There’s no way to hide sections of a wiki from the public or from particular groups of users. - It tries to be all things to everyone. While this makes it versatile, it also means doing a particular thing probably requires knowledge of CSS or Mediawiki’s own templeting syntax. Sometimes I just want to have an info box that doesn’t clutter the source code of a page. ## Dokuwiki ### Pros - Access control finally! - Plain text files - Easy to create namespaces, which Mediawiki also has but doesn’t want you to go crazy making your own. - While it’s not Markdown, the markup is nicer than Mediawiki IMO. The table syntax at least is miles better ### Cons - Uglier than sin. Yes even many of the templates (themes) on offer aren’t much better. The Bootstrap 3 template seems particularly popular, and while it’s a marked improvement in most areas, like a lot of frontends that use those bootswatch pallets there are dusty corners that don’t work, like black text on a black background. - Some stuff like tags and moving pages have to be achieved via plugins. Seriously you can’t even rename a page? - Mutilates article titles. Makes everything lowercase and replaces non alphanumeric chars with underscores (or something else configurable). ## Bookstack ### Pros - It looks good I guess. Haven’t spent much time with it. - Yay markdown! - Also has access control ### Cons - Also not plain text - remember earlier when I talked about “write now, organize later”? Bookstack holds a gun to your head and forces you to use its shelf>book>chapter>page organization system. I know some people thrive under this limitation, but I don’t. Other wikis I’ve tried but not to the same extent ## Wiki.js IDK, I don’t know much about this one, but don’t like the workflow of making new pages. ## Gollum Really simple, which is both good and bad. ## An Otter Wiki (the article seems to be part of the name) A lot like Gollum. Doesn’t indicate when you link to a nonexistent page. No support for article tags. ## Pepperminty wiki Looks cool but it’s abandoned ## Tiddlywiki Steep learning curve but pretty versatile. It’s a single HTML file so you can host it on something like Neocities. Really rudimentary search functions

+1 for Bookstack. Very simple and easy to learn.
I have been rolling bookstack for many years for all things that I keep for myself, it’s great, been pretty much bulletproof also
Only caveat is that bookstack is very opinionated (even said so by its creator) so be sure it’s what you want.
Thanks, I missed that.

There are so, so many options here.

I’ve found alternativeto.net to be a great way to investigate alternative software:

https://alternativeto.net/software/mediawiki/?license=opensource&platform=self-hosted

Someone just posted their own short reviews of a slew of wiki options in this community so maybe go take a peek at that.

Personally I’m finding I like Otterwiki quite a lot though I’ve not yet dug deep into it.

Otter’s almost there. It needs a few things before I’d call it a wiki rather than just a documentation system, namely backlinks and a way to differentiate between links to existing and nonexisting pages, as well as a way to see what nonexisting pages are most wanted.
If you like Lemmy you might like ibis, also by @[email protected]
Main Page — ibis.wiki

I use Dokuwiki for my small fantasy wiki project. I use many plugins to achieve the functionality and style that I want, but it works well for my needs. None of the others I looked at could do quite everything I wanted.
How did you approach finding the proper plugins?
I considered functions that I wanted (for example, tags) and looked to see if there was a plugin that did what I wanted. Dokuwiki’s plugin browser was very useful for this.

I’m currently migrating my worldbuilding and conlanging project to Dokuwiki. Right now I have an Obsidian vault used for brainstorming and drafting and a public Mediawiki for stuff I feel is worth showing off. Like Obsidian, DW stores everything as plaintext (it’s not markdown but it’s readable and the tables are better IMO). Like Mediawiki, DW keeps a version history so I can keep track of how my ideas evolve over time, which is crucial for conlang documentation. I keep tons of example texts that may reflect earlier phases of the grammar and vocab that I may need to reference. Unlike both Obsidian and MW, Dokuwiki has access control, so I can keep a private namespace for drafts and a public namespace for stuff I think is polished enough to show.

I’m not sure DW meet’s OP’s requirements for “out of the box” functionality though. I think it’s intended to be rather bare bones but be very easy to extend with plugins. The plugin browser is built in, so customization is a breeze. Plugins can be individually installed, enabled, disabled, and updated through the admin GUI.

If you wouldn’t mind sharing, I’d love to take a gander at what you’re cooking up!

The DW instance isn’t public (yet) but here’s a link to the currently public mediawiki instance.

constructed.world

I never invested the time to make the content very discoverable, so you’ll have to make copious use of the random page and what links here features if you want to see what I’ve written.

Enjoy my stress-induced maladaptive daydreams.

The Lonely Galaxy Wiki

Thanks for sharing! I don’t have a ton of experience with MediaWiki and cannot figure out how to go to a random page lol
It’s behind the hamburger menu (3 horizontal lines on the top left of the page), at least with the latest default skin.
If I haven’t scared you away with my nonsense, the DW instance is now public. The link I provided earlier should point to the new server. constructed.world
The Lonely Galaxy [The Lonely Galaxy Wiki]

Not at all! I did poke around some random pages after you helped me, sorry I didn’t come back to my. Thanks for sharing the update, I’m keen to see how you’re using DW.

Judging by how productive I’ve been just in the last 8 hours, I’d say going from Mediawiki to Dokuwiki was a good choice. I’m not even sure why. DW still uses markup instead of a WYSIWYG editor, which I’m fine with. I think it’s the namespaces. MW does have them, but you have to set them up with a config file on the server, and adding and removing them cannot be done lightly. With DW it’s as easy as searching for new_namespace:some_new_article, and the namespace is created along with the article. So I have a scratchpad namespace where I can work on drafts, a stories namespace to put my attempts at creative writing, a lore namespace for, well, canonized lore tidbits, and so on. And I don’t need to worry about names colliding like I did with MW where lore articles and story titles often conflicted.

DW lets you use hierarchy when it works, and loose categories (tags) when it doesn’t (with the tags plugin that is). With MW you just have categories but no hierarchy. Bookstack is the opposite. It forces you to use its shelf>book>chapter>page organization system. It does have tags, too, but you can’t have pages outside of books, and the pages have an explicit order. You can fairly easily change that order, but it’s always there.

Back to DokuWiki, the blog plugin has proven invaluable over the last few days. I can jot down ideas as blog entries and push them to the main lore namespace if I think they’re worth keeping.

i like moinmoin and dokuwiki, mediawiki always felt too complex.
As someone from Northern Germany, I’m obliged to check out MoinMoin!

Its name is a play on the North German greeting Moin (from Wikipedia)

TIL!

MoinMoin - Wikipedia

I use mediawiki. It is not as complex as it first might seems
Do you need to host it yourself? miraheze.org may do hosting for you
Miraheze

Seamlessly create and manage a wiki for free, no ads, no strings attached. See why dozens trust our expert hosting. Join Miraheze today!

Miraheze
Need? No
Want? Yes

I settled on mediawiki myself due to basically how trustworthy mediawiki and mediawiki skins look. I use github.com/CanastaWiki/Canasta-DockerCompose myself but the default includes caddy, which I just overrode in the docker compose override. I believe Canasta is mainly driven by someone who works on a wiki farm.

I also know of github.com/nasa/meza.

However, I want to repeat my recommendation of miraheze. When I run into an issue or need an extension, I just look at what miraheze does or what people associated with miraheze do. I also believe that due to the nature of mediawiki it’s a better use of resources to have a wiki farm as opposed to many separate instances. If they will host your wiki, I think they’re the best choice.

GitHub - CanastaWiki/Canasta-DockerCompose: Docker Compose stack template for Canasta

Docker Compose stack template for Canasta. Contribute to CanastaWiki/Canasta-DockerCompose development by creating an account on GitHub.

GitHub
you’re gonna get a LOT of opinions here. Try some out and find what you like the best. Personally, I run Dokuwiki, mostly because i can just zip the whole directory, and move it to another server or back it up a LOT easier than something like MediaWiki.
I love wiki.JS Spun up several sites with it.

Bookstack comes up a lot when “easy to use” is mentioned. It has a WYSYWIG editor by default and has a fairly simple install using a shell script on their docs website. Problems I have with it are it’s not really a wiki. You can’t link to nonexistent pages or see what other pages link to the current page. It’s more of a documentation system.

But I’ve seen it out in the wild being used for your use case (Tunic game wiki)

TUNIC Game Wiki

Thanks for the example! The reasons you mentioned were why I wasn’t looking into it more (using it for my local docs as well).