DEV Community


Discussion on: A WordPress Development Workflow for Small Teams in 2015

dinhhuyams profile image

How does this change in 2019? Thanks

zackphilipps profile image
Zack Philipps Author • Edited

There are some things about this I would change regardless of the year:

  1. Don’t include the entire WordPress installation to the repo. Instead, only include the theme. Updates to WordPress, plugins, and uploads should be isolated to their environment.
  2. Bite the bullet and buy WP Migrate DB Pro. You will have a better experience.

In 2019, you probably:

  1. Use WordPress as a headless CMS. So, maybe you don’t even need a theme. Instead you use something like Gatsby for the front end. Gatsby would also replace Grunt/Gulp.
  2. Don’t faff around with your own server. If you’re using Gatsby, you probably use something like Netlify to handle builds, deployments, and hosting. DigitalOcean is great, but can be overkill. I suppose you could still use their 1-click WordPress droplet (to host the CMS) but there are probably better WP hosting solutions out there these days.
  3. Use WP CLI for any scaffolding needs instead of saving an SQL dump.
dinhhuyams profile image


I am new to WordPress and I learn WordPress by watching the Udemy course which teaches 'old' stuff. Things have been changed a lot. I use git for my WordPress project and install it on the wp-content (includes plugins, uploads, all themes).

  1. Deployment:
    I use FTP or WP-file-manager plugin to deploy theme and I have to add new pages, plugins, uploads, advanced custom fields manually in staging and production env. How do you do that these days?

  2. Sync between env:
    How can I sync production and local env? WP Migrate DB is great if I fetch DB from production to local but when I make some changes to my local and I want to update it to staging or production, I cannot use that. Should I update staging and production manually?

  3. What WP hosting solutions would you recommend?

Thanks a lot