> ...the problem that no one has seemed to solve is the local editing for a draft document for someone who understands markdown but not git. .bat or .sh files?

> ...the problem that no one has seemed to solve is the local editing for a draft document for someone who understands markdown but not git. .bat or .sh files? :) A decade ago I was transitioning a small dev shop to Subversion, and daily user #2 was an non-tech accountant who was a few years away from retirement... I didn't teach her branching. I didn't teach her merging. I didn't teach her what a trunk was, or how slicing works. She got two batch files: "Get_Newest" and "Share_Work", and presto-chango she was contributing user documentation and keeping our help-files in order inside our development project. These days, UI competence willing, I'd just install VS Code or Atom with a markdown plugin and point it at the right GitHub repo. With smart branching and repo division I think it's a low-barrier way to get people committing via Git.