You just described SVN. It’s what we used before the invention of git. And is still used today for team projects that use complex file formats, like images, binary blobs, 3d models, that sort of stuff. It will work with any files.
You can literally just upload a library of documents to github or another repo service like codeberg. That’s basically what a code project is, a bunch of files.
The main difference being that code is typically stored in plain text files, where you can more easily compare and merge differences, while some other document types are harder to diff usefully. That doesn’t mean you can’t use git to keep their version history, it just means resolving merge conflicts might be a bitch.
I wish someone make github but for documents. Image your documents can be forked by someone and has many branches and revisions, it must be hilarious.
You just described SVN. It’s what we used before the invention of git. And is still used today for team projects that use complex file formats, like images, binary blobs, 3d models, that sort of stuff. It will work with any files.
You can literally just upload a library of documents to github or another repo service like codeberg. That’s basically what a code project is, a bunch of files.
The main difference being that code is typically stored in plain text files, where you can more easily compare and merge differences, while some other document types are harder to
diffusefully. That doesn’t mean you can’t use git to keep their version history, it just means resolving merge conflicts might be a bitch.