Yes, it is, but the issue is ease of use for non-technical users.
I was trying to avoid naming any products on purpose, but, for example, there is a commercial product that is easy enough for most people and affordable that would work for this- and there are a few open source clones that come close.
The open source clones are not quite polished enough for non-technical users, but they are the closest thing I can think of, basically crossing over a wiki + Markdown for knowledgebase creation with Git-like versioning.
There are a million frontends designed to simplify Git for non-programmers. In fact, lots of office software now has version management built-in. Very few people use it. This isn’t a technology problem.
To be fair, version control built into office suits are often hidden away or have other UX patterns that aren’t comfortable for nontechnical folk. So they either still get scared by it, or don’t even know it exists.
Yet there is a demand for version control for nontechnical people. And I know this because I’ve seen enough files called “copy of important thing” or “important thing 2”.
> Yet there is a demand for version control for nontechnical people. And I know this because I’ve seen enough files called “copy of important thing” or “important thing 2”.
This demonstrates LACK OF demand for technical version control, since the system you describe has been used since forever and found to be good enough.
No. It demonstrates nontechnical people adapting the skills they’re familiar with to suit a requirement they have.
It doesn’t prove that they don’t want a better solution should it have the right UX. And, as I said in my original comment, the current UX for version control in documents both sucks and is often hidden away where people might not even be aware it exists.
I do think there are some Markdown-based open source projects that might fit the bill.