Are you transferring a site to a client's workspace so that they can access and maintain it?
Webflow has a steep learning curve, which brings some inherent risk to this. Clients don't always know what they're doing, and bad things can happen.
Webflow doesn't have any kind of GitHub integration for the work you do in the designer, so you're very limited in your ability to selectively revert changes.
Instead, Webflow relies on full-site backups however these can be difficult to work with. On a site restore you lose CMS ID's, break integrations, lose all of the subsequent work...
If you originally built the site, clone it.
When you hand off a site, or make major updates, make a clone and transfer the clone back into your own workspace.
** If you did not build the site, make sure you request permission to do that.
When you have a clone, if they majorly broke a part of the site you can compare and repair directly from two different designer windows - ideally side-by-side on a dual-monitor system.
Note, I use the Agency account for this purpose, so I have unlimited sites, and maintain a BACKUPS folder with dated major revisions.
For JavaScript work, we now do all of our work through GitHub repos, deployed and CDN-linked into the client site. They can make changes, but our tested & working code will never be lost.
