Cristiano

I've got the same issue here. Trying to make changes to a Squarespace which had a few requirements: Editing the codebase (can be done with these instructions) Be able to share changes to the client via a link, effectively a staging version. However, so far I've found that making changes locally and push them will always make them live. However, it would be good to have a way of setting up staging version out of the box so that a link could be shared with the relevant stakeholders so that they can approve it or send feedback before all the work is live. Squarespace does not seem to support this at the moment, at least not explicitly so I looked into cloning the site and making the changes there. The issue here is that there's a limit on how many pages can be cloned and this is not an option. It says: Duplication unavailable: Your site is larger than the 100-page limit for duplication. Edit your site to procceed. Another aspect that I've tried was to branch out from the master branch and commit changes to a test branch. in hopes it would create some sort of "preview". but it seems that Squarespace only serves files exclusively from master and does not look into other branches. In a typical all code application I'm most of the time able to setup the application, pull the production or a staging database and effectively have a copy of the site where changes can be made and shared risk free but the current Squarespace workflow seems to be if something is pushed that's automatically deployed. If anyone has any tips on how to get a reliable staging version of a site going it would be amazing. Thank you!