> I'm convinced that documentation, even for large companies, should just be an Obsidian vault of markdown files maintained via git which is just rendered on th

> I'm convinced that documentation, even for large companies, should just be an Obsidian vault of markdown files maintained via git which is just rendered on the web either using a simple static site generator or using Obsidian Publish This, except for normals, sort of exists: Craft: https://www.craft.do/solutions/businesses https://www.craft.do/solutions/businesses Default is internal only, but you can allow sharing, which creates a web URL that can be privately or publicly shared (and can be on your own custom domain). It has versioning, it has comments, it has real time multi-editor collaboration. An entire conference room, in person and virtual, can co-edit in true real time without anything blowing up, a feat not to be tried in Word, or even Google Docs. Most firms should stop looking and just try Craft. Encourage everyone to do everything there, see what happens. Note bene: it happily imports markdown, also exports Word, PDF, Markdown, and Textbundle, and can feed a static site gen. They also keep busy: https://www.craft.do/whats-new https://www.craft.do/whats-new // I use Obsidian for myself, but Craft to collaborate with non-engineers. I've also been known to recommend FOAM to engineering teams, coupled with mkdocs and a good theme for static site gen, such as material for mkdocs: https://foambubble.github.io/foam/ https://foambubble.github.io/foam/ https://github.com/squidfunk/mkdocs-material https://github.com/squidfunk/mkdocs-material For eng teams already living in VS Code, it's hard to beat PKM where you already are.