Is it possible to work on a release candidate in a separate editor?

Ask the community
, ,
1

I’m working on a client’s site and I’m trying to figure out how to create, and continuously edit another site version without disrupting the already published site. My client makes updates to their site regularly, and they need to review ALL changes prior to publishing. Is there a way for them to edit and update the published version of the site without changes I make in the editor being persistent? Can I make my changes in a sub version of the site without them being destructive.

NOTE: I’m redesigning their site in stages, because there’s a lot of changes that need to be made and my clients input influences changes I will later propose. I can’t change everything all at once. Also, I thought of working out of a duplicated version of the site, but the problem with that is I would end up having to make the edits twice (once on the duped site, then making the same edit again on the main site after approval).

…sorry for the wordy question, and thanks for your help! :wink:

2

I would first go to the site history and mark the last published version as a " back up" , to switch back to this version if things don’t go well as planned while editing.

Then I would start redesigning. As long as i create a release candidate, instead of publishing, the changes will not be carried over to their live version(last published version), hence they can still update and keep using the live site

Use the R C version to test or share for reviews. Once reviewed, you can publish the RC version. You can only create one candidate at a time; will have to delete old one before creating new. One more thing, even if you don’t publish changes and only create RC, the client will still see the new changes you make when they open editor. If they only need to update stuffs to the live site without opening editor, then this might work for you.

All the best!

3

This is great Webix! Thanks for sharing your ideas with the community :wink: