TheBulkyBard

That's rough. Now that I'm used to it, I vastly prefer fluid engine to classic. It's worth taking the time to re-adjust/fix the pages that were adjusted, instead of reverting imo. A fair few of the pages I had worked my hind end off to get working just right are not only now back to the way I like them, but also looking better. The stacking and layer editing is a dream, especially given the mobile/desktop separation now. 

I was totally unaware this change was coming. Clicked on a popup today and, as curiosity got the best of me, I saved the change to Fluid Engine on my pre-existing site. At first I panicked and was quite furious due to how it seemingly destroyed all of my hard work...but then I took a breather, and started messing around with the new engine and IT IS BEAUTIFUL. So many things I used to have to use CSS for are now just built in or otherwise circumvented by how the Fluid Engine operates. Most notably being able to (most things I've tried have worked) FINALLY edit desktop and mobile independently from each other. I'm in love with it. 

That's rough. Now that I'm used to it, I vastly prefer fluid engine to classic. It's worth taking the time to re-adjust/fix the pages that were adjusted, instead of reverting imo. A fair few of the pages I had worked my hind end off to get working just right are not only now back to the way I like them, but also looking better. The stacking and layer editing is a dream, especially given the mobile/desktop separation now. 

You should use data-section-id, instead of using #page .page-section:nth-child(1) 
Use this tool to find data section id. https://chrome.google.com/webstore/detail/squarespace-id-finder/igjamfnifnkmecjidfbdipieoaeghcff?hl=en