- cross-posted to:
- selfhosted@lemmy.world
- cross-posted to:
- selfhosted@lemmy.world
cross-posted from: https://lemmy.dbzer0.com/post/5400348
Two days ago, I deployed the official wiki for lemmy.dbzer0.com. It’s using django-wiki as a software, which other than being markdown-based and therefore helping lemmings easily migrate documentation over, provides python hooks for doing some really cool stuff.
For example my current version is tied to my lemmy instance. This means that while everyone can read the wiki, only registered users of my instance can edit articles. This helps prevents the usual problem of open wikis, which is drive-by spam articles, and ensures that only people with interest in the wiki can use it.
I plan to extend this integration in the future. I am thinking things like minimum account age to edit all or some pages, profile pages which enable even tighter integrations, being able to specify “trusted instances” which would allow edits from their users as well, and so on.
But that’s not all, the same approach I used, can also be used to integrate with any fediverse software, like mastodon. This means each instance could theoretically have its own wiki to extend the information adjacent to it.
I’ll soon (I hope) will provide an ansible playbook that anyone can use to deploy it which will also provide my custom code to integrate with lemmy.
You must log in or register to comment.
Very cool!!
Gotta love how /c/ADHD is already on it. Their Wiki will then probably get abandoned for months on end, only to get picked up by the next potential maintainer in a manic “THIS IS NEW AND EXCITING” phase. My people <3
That’s great!
I wish that I could upvote this more than once. Amazing initiative - I always felt like wiki+lemmy could be a great combo, one for discussion and another for long-term storage of info.
Cool. Good that we use standard Markdown instead of
''''whatever'''' ''Wikipedia uses''.To be fair, wikipedia was first, and markdown isn’t a “standard” :D Just one guy’s idea that became popular. But I also prefer the markdown format.
Also, I’d argue the wikilinks (internal links) using
[[any term here]]from Wikipedia, that optionally allow automatically inferring the link, is much more comfortable (and less error-prone) for the usecase of a wiki system, than the[text required](/link_here_also_required_even_when_redundant)from markdown.I was hoping they might have added some markdown extension to do something similar, but it seems not.
I dont see why we cant have both?
Me neither? That’s why I was hoping they might have added some markdown extension.
I have done it in the past with mardown-it-wikilinks npm package, for example.
If u know of any clients written in python i can do it. Or i could do it in js but dont hate myself enough to work on 2js programs simultaneously.
