Not really, just think about merging two branches. You can't really ask Dropbox to merge two diverging versions of a Word document, preferably automatically, maintaining coherency and correctness of the texts.
In fact, I've been involved in collaborative writing and it was organised so that it didn't require any awkward merging procedure.
'Git skills' take people away from writing. Or, put another way, 'git skills' increase cognitive load on programmers and is just another area where mistakes can be made.
In fact, I've been involved in collaborative writing and it was organised so that it didn't require any such thing.
That just means your group chose to limit the potential quality of the work (by not allowing people to improve on other's parts) or expand the timespan of the project (by disallowing concurrent editing) on behalf of simplifying the process.
They're valid tradeoffs, but too limiting for most software projects, in my opinion.
