Recommended workflow when developing new websites A common workflow for me when building a web page is the following. 


I'm getting a PSD-file (Photoshop) from a external advertising agency
Build the site in Webflow and then export to plain html/css/js
Build the site locally in Craft CMS using Textmate
Deploy to dev.customer.com using DeployBot and Github
Send username and password for Craft to advertising agency, they then start to fill the site with content 


The problem with this workflow is when the agency in step 5 want changes (new fields, sections).  I don't want to add fields on both localhost and dev.customer.com. And I don't want to temporarily shut down dev.customer.com, export database on dev.customer.com to localhost and then import to dev.customer.com when done (there is often a tight schedule).

How would you do? Does Craft 3 solve this?  If not, maybe me and the agency should work on the same codebase and database. One way is to have a small server locally (which i don't have) turned on 24h and open port 80 from outside so the agency could work in Craft. Another way is to use SSHFS to mount file system over SSH on a remote Linux VPS (which i have plenty of), but i'm not sure how stable this is.
Essentially the question is "how can I manage changing database content across environments" which has been covered several times here before.  Some leisure reading:

What&#39;s the best practice for handling data migration and organization across development environments?

Git Workflow and Multi Environment - how to approach

What&#39;s the best practice for upgrading a versioned Craft site?


  Does Craft 3 solve this?


Craft 3.0 will not have a solution for this at launch, but we are planning on something post 3 launch that will help making managing Craft content across environments easier to manage.