Wiki vs Markdown in git

Noticed this recently at

This is very interesting, because for years I’ve been trying to get companies and teams to adopt Wikis for internal documentation with very little success – perhaps because Wikis don’t really offer a collaborative flow that is rewarding to participants.

This also reinforces my growing conviction that a lot more documentation should be done in Git using Markdown. One of new uses for documentation is as a point of collaboration – Git + Markdown provides a mechanism for working through ideas, plus at the end you have documentation – a tangible, useful, and durable product rather than something that vanishes into history (like an email/slack thread, meetings, etc).