• In the past we have always only had one person doing our site updates. They would work in a DEV clone of the production wordpress site and then when their changes were all set to go, we could clone the dev over the top of the production site and all was good.

    Now, we have MULTIPLE people doing editing. And we started down the same path of having a separate dev site for each of them (dev, dev2, dev3, etc)… but then when it came time to publish we encountered the trouble. Dev clones over production… all good. Then Dev2 clones over production… we lose Dev’s changes because what he modified was not in the Dev2 clone. Repeat same situation for when Dev3 clones over production.

    So… I know there are people out there with many people producing content for their sites. Do you just not use DEV sites and people work entirely within production (we use Elementor, so that would get god-awful slow if so… we can barely have 2 people in using the editor within a site before it is taking minutes to load a page). Or… does everyone work on a single DEV site that is published to production at regular intervals?

    Just wondering what best practices are for this so I can get my people setup correctly and be the most productive they can be with as little internal operations knowledge required of them as possible.

    Thanks in advance!

    • This topic was modified 2 years, 10 months ago by hellfyr.
    • This topic was modified 2 years, 10 months ago by hellfyr.
Viewing 1 replies (of 1 total)
  • Create a single dev site, where all users contribute. Push from dev to prod on a schedule (every Sunday at 9am, or whatever).

    Or, create a repository on github where contributors work locally and merge files then push to prod.

    Or, work in production using Roles based permissions to grant access to the public.

Viewing 1 replies (of 1 total)

The topic ‘Managing Multiple “Dev” sites’ is closed to new replies.