You don't need to document the use of github or any source code management system for the end users of your project.

If you have a simpler, more direct way to do what git does the world would be very interested.

Git may be good for the bazaar, and may even find a place somewhere in the cathedral, but it's not a good fit for the "monastery" where an inspired abbot works with a very small team of dedicated and enthusiastic monks to produce reliable code. When we coded our Plain English development system, we put all the source in a folder called CAL-3000. When we got further along, we saved everything in another folder called CAL-3001. Etc. When we found ourselves with a version what was seriously flawed, we simply deleted the current folder and opened up the previous one. And when we got to something we were satisfied with, we released it (in this case, the CAL-3040). Then we saved everything in a folder called the CAL-4000 and went to work on the next version. So, there. In one paragraph we have the monastery equivalent of the bazaar's 231-page GitHub manual.

Then we saved everything in a folder called the CAL-4000 and went to work on the next version. So, there. In one paragraph we have the monastery equivalent of the bazaar's 231-page GitHub manual.

This system has been used in the past by even quite serious large businesses, until the disk were they held they directories failed and they lost of all their source code.

Sorry, 21 years of programming experience doesn't buy the 231 page excuse. I haven't read single page of that manual and I'm capable of using GitHub and git. Utter nonsense, or intended pun.

As far as I can tell a large part of the work of monastic scribes was document reproduction and storage.

I suspect they might be all over git and github. Like they were when the printing press technology came along with Gutenberg.

Can I assume GerryRzeppa has some kind of discomfort at his project being forked and worked on by others?

That folders nomenclature scheme is just exactly what the core functionality of git does under the hood, just only that with a bazillion advanced extra features yo manage them. In fact, Linus Tordvalds created first version of git with a bunch of shell scripts...

Maybe all you need to do is just try and put all the files into a standalone .exe file (if it is possible)