Just wondered about some suggestions for 'best practice' for how to back up an EW site or indeed parts thereof.... Before you ask: I DID check out the EW help and couldn't see anything....... Surely something so important should be 'in your face', as we say in the UK.I found this concept particularly important when doing modifications to e.g. a project being changed on the fly.... I can't tell you how many times things were changed without me having a clear idea why... and potentially messing things up in a big way e.g. master.lwt, or styles etc. So best to back it up before any modifications seems to be a sensible approach....
It might also of great value (a) as a learning tool - watching how the site has evolved ("Heck, did it really look like that !! What was I thinking !!?) and (b) for audit-like recovery of potentially missing files or code that might have been lost in incremental changes.
(Yes, I know that once it is published the ISP/Host has a copy on line, but it seemed to me it made sense to have something off site and safely 'put away'.)
A little bit of research showed the File/Export/Personal Web Package - I wondered if that might be one way of going ahead ?
Up to now, I have used good old winzip which I guess does the trick.
I may be in a minority here, but I'd like to suggest a quick video on why its important and suggestions as to how to carry out a EW site backup.
Again, many thanks in advance,
Tim