Now that our site is live (yay!), I'm trying to figure out the best way to handle staging in the webflow environment. Here's my challenge:
- We have our custom domain attached to our production site.
- I need to make changes for the next version and be able to test them on devices, for things like touchscreen behavior, etc.
- As far as I can tell, the only way to do so is to make a change and publish, which of course I don't want to do because I'm just testing and I know that I'm not ready to go live with them yet.
Currently, my workaround is to duplicate the site and make changes and do testing there, because I can publish it without impacting production. But my only choices from there seem to be:
- Note all changes I've made carefully and reproduce them manually in production, and hope that I got them all right when I push "publish." Not really practical for anything but the tiniest, safest of changes.
- Remove the custom domain setting from our production site and set it, as well as any other site settings that weren't duplicated, in the duplicate site, effectively replacing the production site with my new one. This is like a crude version of pushing staging to production, but I'm concerned about dns lag with the changes. In the very best case it's cumbersome and would need to be done in the middle of the night to avoid the possibility of downtime while making the switch, and worst case, we incur the full ≤48 hr dns propagation period each time we do this.
Any thoughts about providing a real staging workflow? It would be more than a minor convenience. The need for it is sort of brought about by the full cloud nature of using webflow as the dev environment, vs. traditional setups where all the files are local and we can set up staging ourselves.