We are using Elementor to build a website and certain pages have been assigned to each team member.
First, I did a theme and plugin installation and pushed the wp-content to GitHub. The other team members were able to clone it and start from there. The plan was to create a separate branch for each page and when we were done, we'd send a pull request to a default branch. But with page builders, I'm guessing that only tracking the wp-content won't be enough. Are we supposed to import the database and push it as well?
For instance, when it comes to changes made with Elementor, how do we use version control and synchronize changes between team members, since all of the data is stored in the database in the postmeta table?
Let's say I set up some global properties on Elementor and want everyone to have the same. The header and footer needs to be the same as well. Later we'll also need to integrate pages from each team member into a single place. What's the best way to go about this?
Hi,
First, use Git to manage your code. Since you’ve got a GitHub repo, keep your theme and plugin files there. Each person should work on their own branch and push updates regularly. For database changes (where Elementor saves designs), export your database with tools like phpMyAdmin or WP Migrate DB, and share the file with your team. I personally think that it’s easier to use a plugin for handling database migrations.
For consistency, I would suggest you use Elementor’s Global Settings for things like colors and fonts. Save common sections like headers as templates that everyone can use. For team collaboration, try the Multicollab plugin for inline comments and real-time feedback within WordPress.
It’s just my suggestion that you can use communication tools like Slack or Microsoft Teams to keep everyone in the loop. When someone finishes their page, have them create a pull request to merge their work, and test everything on a staging site before going live.
Thanks
You should all be working off the same database. It will be painful doing this if each of you have your own WP instance.
There is no way this gonna work with each one of you doing it locally and using page builder.. If you were to create something like custom theme, coding blocks, styles, then yes… However Elementor save pages to DB and yours DB aren’t in synce nor they will ever be, there is no way to merge like 5 different WP DB into one.
You NEED to use a central dev site, which is online and accessible to all team member, then each guy can work on it own page. Every other solution is just too much trouble…
> I’m guessing that only tracking the wp-content won’t be enough. Are we supposed to import the database and push it as well?
Correct, all of your data (pages, settings, etc.) is stored in the database. There is no simple “partial” database push solution that I’m aware of (I’ve seen custom implementations), so what you’re thinking is not viable.
> For instance, when it comes to changes made with Elementor, how do we use version control and synchronize changes between team members, since all of the data is stored in the database in the postmeta table?
You should all be working on the same site together. Working on separate pages will still work/be fine, you guys will just all be working at, eg. example.com. Common workflow is to have a dev/staging server if you don’t want to work directly on the live site first. Most good/popular hosting will offer this as part of the package.
My recommended course of action would be:
1. Get a site up and running. could be at the live/final domain, could be a dev site, doesn’t matter.
2. Move everyone’s WIP pages to this site. This can be done manually/re-creating each page, or I believe you can use the WordPress Exporter/Importer, although you will probably have to do some clean up.
3. Now everyone can just work on this new site together and you don’t have to worry about it.
I see in the comments that you’re not too keen on doing this right now, but you will have to do it anyways (when you want to make the site live), and you will have less headaches setting it up early before there is too much data to move, etc.