Got it. Ok, so this I would propose doing this via conditional rendering. The steps to getting this working can be a little complex, but this is a completely legitimate way to do things and something our Solutions Engineers and internal teams use all the time. It involves a couple things to make it work.
1. A UI-only model to drive the conditional rendering.
2. A conditionally rendered section of the page.
3. Two buttons. One to hide the conditionally rendered section, and one to show it.
You may be familiar with this process, but just in case you aren’t or someone else who stumbles upon this isn’t, I’m going to go ahead and explain it.
You set up a UI-Only model with a checkbox field that is used explicitly to show/hide a single section of your page, with a default value of true. Then, you set up a conditionally rendered section of that page to be only shown when the value of that field is true. Lastly, you set up two buttons, one to set the value of your ui field to true, one to set it to false. You also conditionally render these buttons so that you only are ever showing the one that is relevant. With all of this, you have set up a section of your page that is always shown by default, but can be toggled with the click of a button.
Here is a link to a page that does just that.