Teamwork on the site

Not all sites are made by the studio and then given to the customer.

It happens that complex portal-type sites develop in stages,
some are available online, others are under development,
and in fairly large projects several almost independent groups can work on the site.

Here you can see without binoculars that it would be nice to use a repository for storing php and html code.

But how to do it right?
With designers and programmers, everything is quite simple, they develop code on local machines and make changes to the repository. You can even configure cron to periodically post the latest changes from the repository to the online site.

But what about the content?
Content changes only on the online version, so as not to complicate matters by synchronizing data from different databases. But not all content is stored in the database, often CMS content of static pages is stored in .php files, because of which new files and changes appear that you have to periodically transfer from “online” to the repository, and do this manually to avoid version conflicts.

It is interesting who faced and how to solve such problems.