Lemmy

2172 readers

9 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to [email protected].

founded 4 years ago

MODERATORS

[email protected]

Are there plans to add support for wiki pages? (self.lemmy)

submitted 1 year ago* (last edited 1 year ago) by capr to c/[email protected]

25 comments fedilink hide all child comments

Title says it all. Unless I'm missing something, I don't see a way to do anything wiki related at the subs I've created.

you are viewing a single comment's thread
view the rest of the comments

[–] capr 2 points 1 year ago (1 children)

For the first option you mentioned, a user already suggested a service called Hubziller. My issue with it is it might be a bit tacky or confusing for readers if they subscribe to a community but have to visit a separate service to access wikis, instead of making them in house. Maybe it's just me being stubborn and not thinking outside the box since I've been a mod on Reddiy for 10 years, but that's my humble opinion.

The second option is a more practical solution for here and now but it doesn't allow for collective editing or reverting changes.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Yeah. I'm definitely for some pretty seamless integration. Probably in the optimal case:

The wikis would be hosted on the same domain as the Lemmy servers.
Any account you had on the associated Lemmy server would automatically exist to the wiki as well.
If you were logged into Lemmy, you'd also be logged into the wiki.
Only mods would be able to enable wikis but the process of doing so would be trivially easy.
I'd personally say that it makes the most sense to just have the mods link the associated wiki from the sidebar rather than creating new special interface features to add a link outside the sidebar or whatever. (Unless some kind of plugin infrastructure that would allow that already exists.)

But all that can be done without putting any wiki-specific code into the Lemmy or Lemmy-UI source repositories, which I think is preferable for the same reason you wouldn't add flight simulator code to a spreadsheet application. (Ok, maybe a bad example, but you get my point.)

Edit: And I'll admit there are both upsides and downsides to my approach here. One downside would be that some Lemmy instances would offer attached wikis and others wouldn't. It's possible it also just wouldn't catch on at all and nobody would enable attached wikis as a feature if it was a whole separate step to setting up "Lemmy".