How is the work for site layout automated?

Question

Automation

Good afternoon!
Now we are working on one project, in a team of 2 people. I am a programmer and designer/coder.
There are quite a lot of pages in the project, and the question arises of how to store / transfer all this.
And then an unpleasant situation arose, all the laid-out pages are sent to me by mail in archives. Actually, the archive stores 1 html file and all the statics for the project. The size of the archive is 15 MB, the number of pages is more than 50, if an inaccuracy in the layout is found, another archive is sent. And so I receive 2-3 archives per day by mail, it happens that there are a few more pages in the archive, which may differ from those sent earlier. And up to a bunch of css files in the new archive, they are somehow used from the outdated archive (i.e. the layout designer does not think, the main thing is to do it).
I'm already confused in these archives, and when searching for the right page, it starts to make me nervous, plus a huge waste of time.
How can all this be automated so that there are not a huge number of archives?
Thanks in advance for your replies!

Answer 1

In general, I agree about Git, as it was said, but in general it is called Version Control System, VCS . There are others like Mercurial, Subversion, etc.
Since you can work with Git either alone or as a team, and, moreover, each user has a local copy of the repository, a VCS server is needed to link and receive updates between users.
Many VCSs can work both on their own protocol and via HTTP.
This VCS server can be either such hosting sites as BitBucket , GitLab , GitHub
or your own server on which you install your Software (the same GitLab Community Edition). Among the advantages of our own solution is the potentially high speed of data exchange over the Internet and the absence of any visible restrictions other than paying for hosting.
GitHub servers are located in the USA, which means that downloading any relatively "heavy" (more than 7-10 MB) data will result in waiting for the upload to finish. We take into account that the upload speed is always lower than the download speed of Internet providers.
I thought again.
Perhaps a service like Dropbox should be more suitable. You throw files into a folder, and the agent itself is engaged in data synchronization between the user and the remote storage.
That is, no Git.

Answer 2

Discover Git