Git for normal people (or, version control for mortals)
- people who work on non-plaintext files
Git as a database? How? Are there other ways of bringing git-like branching and merging into collaborative software? See Asynchronous collaboration
How can we explain it plainly? How branching and merging works. So many people could understand it. Who could we test this with? Some writers who work editorially? Maybe talk to some publishers
Technology-wise, automerge might be a great solution. Designing workflows and interfaces that explain how this works well is a tough problem! (And one I’m keen to look into).