Skip to main content

Lock pages

  • March 11, 2021
  • 27 replies
  • 6839 views

Show first post

27 replies

Salvador1
  • New Member
  • May 6, 2025

I love this idea! Currently how I structure some projects I have pages set up for concepts, the stages for each proof (proof 1, proof 2 and so on), and releases. If I ask leadership to review and comment on Proof 2, and I’m starting proof 3 they’ll start noting or making changes on proof 3, why? I don’t know I’m sure curiosity kicks in and they feel it’s best to comment there. I also see the need for this when I have a page for components that I would prefer others to not have access too. 

 

To try and combat this at the moment I have a file I named playground in my drafts and I do everything there and then have to copy and paste it into the project. It would be nice if I didn’t have to do this.


James_Walsh
  • New Participant
  • February 26, 2026

Locking should also keep it from taking component updates. This would allow it to stay in sync on the page that represent the live on site design, while we update component for the new design version page.

Being able to “Publish” a client visible version would be amazing.