3 ms·
Surprised they didn't recommend Wiki.js under the Wiki section, imo it's the best modern Wiki software right now. Might not be as battle-hardened as Mediawiki b
by haunter 5y ago
Surprised they didn't recommend Wiki.js under the Wiki section, imo it's the best modern Wiki software right now. Might not be as battle-hardened as Mediawiki but my experience it's more pleasant to use https://js.wiki/ https://js.wiki/
- eddieroger 5y agoThere's a lot to be said for Mediawiki's battle-harened-ness. What makes this so much better, particularly when both could be spun up with just docker containers?
- kube-system 5y agoMediaWiki is good if you have a public wiki. If you need to delegate permission or use an identity provider, it’s a pretty bad choice.
- eddieroger 5y agoIf your identity provider supports LDAP, not really. I was partially responsible for an enterprise wide installation of MediaWiki that talked to LDAP just fine, and this was over ten years ago.
- kube-system 5y agoI mean, it has basic support for a private wiki and delegated auth. Just not very robust support. There are a lot of dead ends for common enterprise use cases. It’s just not really designed for this use case, and there other options that do these things better out of the box.
- mhh__ 5y agoI'm not familiar with this tool in particular but I'm fairly convinced now that wikis are often an anti-pattern. If you want a wiki as a loosely federated dump of knowledge then a traditional wiki is ok, but if you want it to be instructional material (e.g. "How to build GCC on the Apollo guidance computer") or a cohesive manual, then it should really be generated by something tracked in a proper git repository.