Permalink Submitted by Yonas Yanfa ("fizk") (not verified) on Wed, 05/23/2012 - 07:07
I understand why you didn't initially feel the need to use a VCS in this situation, but in the long run, it's definitely worth using.
I like to keep three main branches in my git repository: "development", "staging", and "production".
In terms of working with a theme developer, what works for me is to build out as much functionality as you can first, then ask the theme designer to start building the theme on the dev site.
To help in the effort of duplicating changes made in staging or production, you can export your panels, views, etc, into PHP code and store it in your repository, then push the changes into your other branches as needed.
Version control to the rescue
I understand why you didn't initially feel the need to use a VCS in this situation, but in the long run, it's definitely worth using.
I like to keep three main branches in my git repository: "development", "staging", and "production".
In terms of working with a theme developer, what works for me is to build out as much functionality as you can first, then ask the theme designer to start building the theme on the dev site.
To help in the effort of duplicating changes made in staging or production, you can export your panels, views, etc, into PHP code and store it in your repository, then push the changes into your other branches as needed.
Cheers,
Yonas Yanfa ("fizk")