I would make the menu a reusable element. That way you can put it on every page and then have the page content to the right. That would be for a multipage app.
@Nocodify
but then on the right main content area - i should just put several different groups and display them based on the state set - correct?
this seems doable - i will give it a try.
Just another question - if i have many - lets say 10 - different content items (subpages) and all are relatively big with many elements - should I just put them one after another on the content area?
this would be hard to read i guess - just wondering what is best practice here
@msamandadianne - oh so this is different idea - right? so I would need to create multiple pages with similar structure and reuse left menu on every one. This would solve “readability” in case of many subpages…
OK i think i just need to experiment with both approaches
Not quite sure what you mean here. I’d put the different groups on top of each other, and then just show them with states. Again, if it makes sense to use groups, go ahead and do that, but sometimes navigating to a new page would make more sense. So then your menu would be a reusable element.
What I meant (with those 10 subpages) was - how would it be readable in editor… but yeah as you said - i can put them on top of each other and switch between…
Thanks again - now i have material to experiment with!
I usually create a state for the whole page called “menu”.
I will then set all groups to not visible on load. Then each group just has a condition “when my page’s menu is ‘settings’ this group is visible (checked)”
Then you just need a final workflow to set initial group state on page load. You can always send a parameter to the page as well to be able to set a different group on load.