Dev to Live Staging and Approval Process?

[macrobber]

We are investigating how we might implement a staging / approval process for changes made to our live site and I am wondering how others have (or might) handled this.

Let me give you the scenario. We have a dev site and a live site. We have a few users who will likely be making changes (to products, subscriptions, changing images, etc.) throughout the day. We would like to stage those change and have some type of approval process before they get ‘pushed’ to the live system. Has anyone implemented such a work-flow with Miva?

My initial thought was to have changes made to the development site throughout the day, <<insert some approval process for the changes towards the end of the day>>, and possibly push (either through a cron job or a more manual process) those changes to the live system at night.

[Kent Multer]

Some years ago, I had a client with two stores, and he wanted to have the same products in both without entering everything twice. I wrote a module that could transmit the changes from one store to the other. This could be adapted for your purpose: the staff can make changes in the dev store, and the supervisor can push the Transmit button after approving the changes. If you're interested in something like that, you can drop me a line to discuss the details.

Thanks --