Version Control Workflow

Elements
1

I have been developing a site for a few weeks now, publishing to a password-protected staging site for feedback from friends and stakeholders. This morning I finally published to the public site. Hooray!

Now that the site is live, I am wondering how others manage version control workflow. As I envision it, I will continue to make tweaks and changes, publishing to the the staging server until approved, and then rolling the changes to the public server. So I will have a published version and a work-in-progress version. Should I maintain two Elements project files? Should I check the project file into GitHub and manage versions there? (I am working alone.) How are you all doing it? How do you handle potential rollbacks? Thanks in advance…

2

When I make major changes I’ll call it ‘xyz test’ thus keeping the original and making changes to test…

Inevitably- for me- I’ll delete the original and drop test off the name…

You could also save versions by date…

Whatever works best for you…

3

For changes on only one ot two pages, I duplicate the page within the project first and set this dublicate to not publish, not in the navigation. So I can always refer back to it.

For larger changes on a site (and not only one or two pages) I duplicate the project and add the date to the name, then work on the original for the changes.

1 Like