@mattdev I would take a look at our templating language HubL to see if that can help. That should allow you to template out your divs based on certain logic flows. Here is a link to the documentation.
@mattdev So I think you have nailed one limitation being scope. You would have to everything reside in the scope to be able to access the value. That being said there might be a workaround for it. You could try and use HubDB to store the value and access it it from another part of your website that is outside the scope of that custom module. You will most likely will need to create some sort of session ID to go along with the choice or maybe the contact last name to correctly be able to match up those user choices down the road.
Awesome, i’m glad you found a workaround. thanks to some digging by @zwolfson, he found a page that might be helpful for down the road if this comes up again. There is a way you can export out that value to increase the scope of it.