@UKRiggers @Antony I have worked in the industry for more than the 20 years and managed large tech teams and once I stopped listening to a developer trying to explain what GIT is it made perfect sense!
A layman's explanation: its just a document manage system (version control) for managing code, that's it! It enables you save files and folders and any changes made to those files are stored as a change including meta data such as who did what, when they did it, what they changes and how they changed it.
It also allows many people to work on the one document (substitute files and code) and files and submit changes (snapshots) and is able to merge all those changes into a one version of the "final document".
The folder it stores it in is called a "repository" (or repo) and has the name .git.
It becomes important once your application gets complex and you have many people working on the same code and you need to make sure no one overwrites that code (including yourself).
But, like most things tech it needs to be as complex and as intimidating as possible 
.
However, I have seen some nightmare scenarios and my strong advice would be at the very least set up your Wappler project to work with GitHub it's really easy to set up and once done you can just save it to both the local and GitHub (remote files storage). Then if something should go astray (which it always does) you have a remote record of every commit (saving of the files) and you can dive into it to find your way back.
Just think about it as a secure remote backup copy of your days work!