As an experiment builder that generally uses the code editors and who uses the cookie and querystring model for qa and works with intricate code that is load dependent and requires more than a few updates to get working properly within the actual site code

I would like to have the ability to publish the variation update on the variation screen (perhaps a 'publish' button)

So I don't have to save the code changes, then go to main experiment screen and publish and then navigate back to the variation and wait for the page (which will fail because it is behind a login or firewalled) and then find the specific page and load again before I can make further updates. It would also save opti servers from all of those loads and network traffic traffic.

Could make it a setting I can choose to enable at project or user level as not everyone is going to need or want it.