MycorrhizaWiki is a wiki engine written in Go. A wiki running MycorrhizaWiki can be accessed through web only for now, gemini front-end is planned.
It is developed by Timur Ismagilov, that's me
GitHub repo
Features
- Pages are called hyphae. Hyphae can be nested however you like.
Each hypha consists of two parts: textual (mycomarkup) and binary (image, video, audio, arbitrary octet stream). You only need one to create a hypha.
- MycorrhizaWiki implements a special markup called mycomarkup. I used to use gemtext but it ended up being not sufficient. Still, there's a high degree of compatibility. For example, gemtext's => links are supported together wiki [[inline links]].
- Edit history is implemented using git.
I used to use a custom version control system in an earlier version, but I don't think it's a good approach now. Git is so much better. By the way, older edits are not forgotten unlike some other wiki engines.
- There is a tree shown below every hypha that lets you quickly get to a sibling or child hypha.
- Links are colored, like in MediaWiki. Red = hypha doesn't exist.
- You can transclude other hyphae freely with a nice syntax.
- This list is probably incomplete, consult the original repo.
MycorrhizaWiki is close to supporting the common wiki structure.
When you shouldn't use Mycorrhiza
- When you have a really large team of contributors and need an account system.
- When you need a stable tool. Mycorrhiza is developed by one guy (that's me) with some contributions of other people, not an enterprise product.
- When you need something bigger than gemtext.
In all three cases, I'd recommend MediaWiki.
Where Mycorrhiza excels
- Easy to install. One binary to run. Compare to MediaWiki or even MoinMoin.
- Not resource-demanding. I run a MycorrhizaWiki wiki at home on an Orange π lite.
gemini://tanelorn.city/~bouncepaw/gemlog/welcome-orange.gemini
- Sane naming rules: case-insensitive, space=underscore, unicode support. Some characters are forbidden though :-( These are the same links in Mycorrhiza:
mycorrhizawiki
MycorrhizaWiki
mycorrhizaWiki
MYCORRHIZAWIKI
- I use it every day. It means it either gets abandoned (unlikely, I kinda have to support it because of how much data I now have on my home wiki) or gets useful features for everyday usage.
- Works perfectly in mobile browsers and text browsers. Not sure about auditory browsers though. Who can check?
- Has a nice mushroom-inspired terminology.
Gemini integration
Well, there is currently no gemini stuff in the engine beside the gemtext stuff. Gemini front-end is yet to come.
Some integration can be achieved using external tools. I've written a bash script called akavi.sh (akavish means spider in hebrew) that grabs copies of my gemlog pages and adds them to the wiki.
My gemlog
More integration (and not only gemini-related) will be implemented some day. The engine is called Mycorrhiza for a reason.
https://en.wikipedia.org/wiki/Mycorrhiza
I'm thinking about exposing read only pages through gemini and write only pages through titan. It'd make Mycorrhiza quite similar to Phoebe!
Central wiki
There is the central wiki (which is also the test wiki) called Metarrhiza (what a good naming!).
https://github.com/bouncepaw/metarrhiza/
The problem is that it's not hosted anywhere. I'd love someone to host a wiki for me, not gonna lie.
Keyboard wiki
There's a wiki running this engine devoted to ergonomic keyboards and stuff like this. It's in Russian.
http://klavarog.tk