As a long time Wikipedia editor and administrator (might as well get my biases upfront) I am unsure it is a good idea to target Wikipedia. I can understand why, ideologically, this seems like a good idea (and I am sure there’s many a thesis written on its inherent biases) but Wikipedia has the longevity, momentum and sheer weight of users that mean it would be impossible to catch it up and the last point is key because it’s also a vital part of it’s defences against bad actors. That’s not to say it doesn’t have its problems and I haven’t edited in a while (as I was in a place where I didn’t need any extra drama in my life), so it’s good that this tool is out there for people to create an alternative it’s more that I can see better uses for the already impressive wiki software you’ve created. And one key use would be as a plug-in to an existing Fediverse service, rather than a standalone wiki.

A while back I suggested that what Lemmy needed was an integrated wiki - I dubbed it Lemmywiks. I’ve mentioned it a time or two since as it seems the solution to a few issues people have raised. In the meantime I have mulled over the idea (to the point I was rolling my sleeves up to bodge together a proof-of-concept) and it goes a little like this (apologies in advance for the brain-dump):

It piggybacks off the Lemmy authentication (why it’s a plug-in not a standalone) and the bulk of the wiki would be divided up under each community.

Community wiki pages

So:

c/hats

Would get:

w/hats

With all the various pages then being under that:

w/hats/faqs

w/hats/links

And really whatever the community requires - some might not need any pages at all. Well they all get one:

w/hats

Is the main/index page and replaces the text in the community’s sidebar. As they are both markdown it is a straight switch. That sidebar page now becomes the main portal into the community’s pages (if they want any), although you can also add markdown like the wiki links so [[links]] under hats goes to:

w/hats/links

It’s up to each community to decide what pages it wants and the beauty of a wiki is that it is flexible enough to accommodate most things a community requires.

To get around the issue of there not being enough users to monitor edits on pages, I’d suggest they are treated like requests on Github and users can submit edits that Mods would approve or reject. Hopefully, this system would alao encourage communities to recruit more Mods, perhaps even have one or two focused on the wiki.

This system of community wikis would, it is hoped, also encourage more single topic focused instances - we have ones for Star Trek, RPGs, books, etc and there’s no reason there couldn’t be ones for Star Wars, films (there was one that is no more), action figures, etc, etc. A greater diversity of instances has to be a good thing.

In the comments, people have mentioned that this would be ideal for taking on the wikis/fandom wikis and integrating with focused instances would make this possible.

Instance wiki pages

In a similar manner, the main sidebar of the instance is also the front page of the instance wiki pages, structured thusly:

w/lemmy_world/

These pages would only be editable by the Admins and would largely be for all the various bits of documentation the instance needs - legal and policy as well as a potential breakdown of the instance’s communities by category. For example, I help Admin feddit.uk and we have communities focused on football clubs, regions, etc. Being able to have:

w/feddit_uk/football-communities

w/feddit_uk/regional-communities

Would really help with discoverablity and may also help with Lemmy’s SEO.

Not just Lemmy

My original idea was a wiki plug-in for Lemmy because I am on here the most, and Ibis coming from one of the Lemmy devs makes this an even better test case. However, it would work equally well for other services. Obviously the above structure would be what is required for kbin/kbin but it could be of use for Mastodon (especially instances with a specific focus) or pretty much any Fediverse service, if only for being a repository for their documentation. As I’ve said, the flexibility of a wiki means that, once you give people the tools they can take it off in any direction they require.

People have questioned why Ibis needs to be federated at all, but it becomes vital when Ibis is a plug-in to other services rather than standalone. For example, I Mod communities on lemmy.world as well as my home instance and I could edit wikis on all communities from my main account.

I probably forgot some stuff but that should be enough to chew over for now.