How to save previous design elements in Webflow when updating pricing tables and layouts? Answered

I know this is more a Webflow than Memberstack question, but I thought I’d ask it here anyway as I know that most people are building on Webflow.

When you change your designs in Webflow, e.g. create new pricing table/options, how do you “save” the previous elements?

As far as I can see the options are:

  • Use the in-built Webflow backup / version control -> imperfect as you’d have to look back at exactly when you made the change and the site may have changed since then
  • Keep the elements on the page but hide them -> imperfect as users might find them and I guess not good for SEO & general bad practice
  • Keep the elements on a different, unpublished page -> this is what I’ve been doing so far. Is this the best solution?

Wondering what others do for this. thanks!

Comments

4 comments

  • Comment author
    John Matias

    I also use the third option you mentioned. I'll keep elements on a separate unpublished page for a period of time. Then eventually I'll go back on that page once I feel like I won't use those again and clean it up and delete them. Although this does sometimes mean I'll have a number of custom classes that I'm hanging on to that aren't useful. But it gives me peace of mind.

    Alternatively, a fourth option could be to create a separate project and copy those elements to that project. But honestly, I've never had great luck with pasting/copying between projects I always run into issues and I end up wasting more time.

    0
  • Comment author
    Alastair Budge

    Ah cool, thanks for clarifying John. That makes me feel a bit better then!

    I know I need to do more tests on my site, and one of the things that has made me hesitant about this is ease of rolling back & reusing the previous designs/components.

    0
  • Comment author
    John Matias

    Something else to consider - which I think you may also be aware of... is that if you restore a webflow site from a backup all of the CMS ids, ITEM ids, and I think the site ID are changed. So if you refer to these in make or zapier scenarios by ID then those will break. I learned that the hard way and have avoided doing a restore from backup for that specific reason.

    0
  • Comment author
    Alastair Budge

    ah ok, I wasn’t aware of that. very good to know!

    thanks

    0

Please sign in to leave a comment.